Jump to content
Posted 13 February 2012 - 04:59 PM
Posted 13 February 2012 - 05:52 PM
Posted 13 February 2012 - 09:43 PM
As stated by Shawn Hargreaves here, It is clearly stated that XNA is not an option for Windows 8 Metro. He doesn't say "XNA is not yet an option, but wait, you will see an amazing XNA 5.0 coming soon". So you should better focus on learning Direct3D11, as there is more chance that you will leverage on this knowledge to jump into the bandwagon next-gen API. If you care about making games for Windows 8 Metro, Direct3D11 is the only way. If you don't, you can still use XNA on the desktop, but you should not expect XNA API to be part of any next-gen plans.
So I guess my question is, is there enough 'evidence' to claim XNA is likely to die? I dont mean an official blog or anything but business patterns, cancelled funding, fired members etc. While the learning curve would be good and learning something is always nice, DirectX is only on my list of things to learn at the moment because of XNA's presumed fate, I am just concerned that a few months down the line a "XNA 5.0 to be released soon" announcement will appear which would mean I spent all that time learning when I could have been improving / adding content to my current game.
Is the ship really sinking?
Posted 13 February 2012 - 11:08 PM
Posted 13 February 2012 - 11:14 PM
.NET peeps who miss MDX should move on to SlimDX, no need to resort to C++
I remember being on these forums years ago when Microsoft dumped managed DX for XNA and pissed off all the VB programmers that were using it.
Is Windows 8 really that much of a resource hog that they have resort to native C++ for games?
Posted 13 February 2012 - 11:20 PM
Posted 13 February 2012 - 11:45 PM
Posted 14 February 2012 - 10:00 AM