Archived

This topic is now archived and is closed to further replies.

Ratman

what to do, what to do.....

Recommended Posts

Ok Im confused, I just finished writing my own DirecDraw engine (or rather, the DirectDraw part of my engine) and now I was planning to write the network part. Now having a pretty good grasp on DirectDraw (and DirectSound) Im thinking DirectPlay should be the next natural step (as opposed to writing my own own network stuff in winsock). But as I look around, Im finding pretty much 0 on the latest version of DirectPlay (or even 6.1). And the helpfile seems to broad and general (I want real examples). And now Im also hearing DirectPlay is being rewritten in DX8. So maybe its not worth my time to learn it now. Maybe I should wait for 8. What should I do? learn it now? wait? do winsock (dont really want to)? find a network library (also dont want to, would rather write at least some of my own code)? any input would be appreciated. ratman

Share this post


Link to post
Share on other sites
well... I''ve here that there planning on rwwritting dplay sence DX 3.0... so they never realy documented it well... I haven''t looked in to dx8 so I don''t know for shure... I say learn it now... there is always backward compatablity... Inside DX is a good book.. it shows you everything but d3d.... have fun...

Great Milenko

Words Of Wisdom:
"Never Stick A Pretzel In Your Butt It Might Break Off In There."


http://www.crosswinds.net/~milenko
http://www.crosswinds.net/~pirotech

Share this post


Link to post
Share on other sites
I''d recommend staying away from DirectPlay and go get yourself a book on Winsock. Directplay is difficult to use, no longer supported, ineffiecient, and just a big general hassle. Winsock is a far superior choice, and is actually quite easy to get going in a simple manner.

Share this post


Link to post
Share on other sites
quote:
Original post by daveb

I''d recommend staying away from DirectPlay and go get yourself a book on Winsock. Directplay is difficult to use, no longer supported, ineffiecient, and just a big general hassle. Winsock is a far superior choice, and is actually quite easy to get going in a simple manner.


Don''t believe the above.

DirectPlay is difficult to LEARN, not use.

DPlay is supported currently, will be supported in dx8, and will continue to be used because of the x-box and the new versions of windows (including win2k).

DPlay tries to be effecient, after all it incorperates many features and tries to give all options available to the user through the various protocal enumerations.

I can''t tell you to use winsock or not, that''s up to you.

however, some day you want to learn it. It''s really really really confusing at times, but if you can learn just the basic initialization procedures, you can pick up sending your own messages rather easily. The help docs provided with dx7 sdk were the most helpful as was the sample chat program with the dx7 sdk.

Share this post


Link to post
Share on other sites
quote:
Original post by daveb
Directplay is difficult to use, no longer supported, ineffiecient, and just a big general hassle. Winsock is a


ahhhh what ah?

No longer supported in DX? what drugs are you doing, send some this way.

I admit it is difficult to understand, but so was D3D when it started out. They are revamping it in 8, but I have had no really bad experiences using it since dx6.1, and, I find it easier than creating a seperate library of functions for winsock.

int main() {
   if(reply.IsSpam()) {
      while(true) {
         int*ptr=new int[1000000];
         reply.RandomInsult(); } }
   else std::cout<< "mailto:amorano@bworks.com"
}

Share this post


Link to post
Share on other sites