Jump to content

  • Log In with Google      Sign In   
  • Create Account


DirectX and Win32...worth bothering with?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 mark ds   Members   -  Reputation: 1190

Like
0Likes
Like

Posted 05 July 2012 - 02:03 PM

Like everyone else, I'm making a game (or trying to!). I'm a fairly strong Win32 programmer, but new to games - although I do have experience with OpenGL 2.1, this is very much a learning curve, and done purely for my own entertainment. Part of the reason I'm doing this is to familiarise myself with modern OpenGL. But, I fully intend to make a Direct3D port too.

Then it dawned on me - is it really worth bothering with D3D on Win32 for a non-commercial endeavour?

With WinRT coming out with Windows 8, which can be used to create both Metro and desktop apps, wouldn't it make more sense to wait and create a WinRT port, rather than Win32?

Also, what's the betting the 'XBox 720', or whatever it will be called, will use WinRT natively - enabling a single development approach to ALL Microsoft platforms?

Any thoughts?

Sponsor:

#2 MJP   Moderators   -  Reputation: 10929

Like
0Likes
Like

Posted 05 July 2012 - 02:36 PM

For a typical full-screen game I don't think you'll have very much interaction with either Win32 or WinRT. It's mostly going to be relegated to a few system API's like CreateFile or CreateThread, which you can easily hide inside wrapper functions that are implemented differently for each platform. So i wouldn't worry about it, as long as you stick with D3D11 as your graphics API.

#3 Hornsj3   Members   -  Reputation: 191

Like
0Likes
Like

Posted 05 July 2012 - 03:49 PM

And, WIN32 is fully supported for Windows8 desktop apps.

If you are targeting Metro Apps you have to target WinRT, as well as a subset of DirectX (due to the Metro sandbox).

Go to MSDN and look at the target environment of some of the functions (desktop apps / metro apps). Like all mobile environments, MetroUI restricts access to system resources.

#4 mhagain   Crossbones+   -  Reputation: 7824

Like
0Likes
Like

Posted 05 July 2012 - 04:47 PM

Definitely worth bothering - native D3D is going to be around for a long time and the potential audience for WinRT/Metro will be quite small to begin with. Unless of course you want to learn the Metro stuff.

It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.





Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS