   Game Development Interface....or watever...pls comment on these...
  have a project(RPG game) in which I intend to...Use DirectAudio and DirectInput for the sound and inputs..Use OpenGl for graphicsUse DirectPlay or Winsock for the networking partPersonally, i take this as a learning session and i will prefer to code the RPG using WinSocka question i like to ask is....i heard of people not wanting to use DirectPlay as it will inhabit the game to Windows platform..i was thinking if say i have used DirectAudio and DirectInput already....not matter if i use Winsock or DirectPlay...the game will still be restricted to windows platform rite?Commercial games i know do use winsock..wat do they use for the sound and input/output devices then?  
  Yes, all those libraries are a part of DirectX, which is Windows-specific.http://roninmagus.hopto.org acronymfinder.com - Find any acronym you need!  ;  If you''re interested in cross-platform, then consider SDL for Input/Graphics, and OpenAL for Sound.  You can use Winsock for the networking, as it''s fairly straightforward to port Winsock code over to Unix.SDL will make your life easier if you want cross-platform OpenGL, as it hides all of the platform-dependent initialization code.  It should integrate well with OpenAL for sound as well.Cheers, dorix;  It would be easier to write the network portion targetting towards a berkley socket implementation and use a few defines to include any windows specific code.  Pretty much all that is needed there is a WSAStartup and WSAShutdown (I think?). The rest will work without any changes.  Theres a good tutorial here.The problem with writing the network code is not that the game will be limited to windows, but that your game servers will be limited to windows, unless you write two versions of the network code, but then you might as well use the other implementation.University is a fountain of knowledge, and students go there to drink.  