Jump to content
  • Advertisement
Sign in to follow this  
Crow-knee

XNA 4.0 near broke me spirit!

This topic is 2808 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi All,
Just a quick synopsis of my experience with the 4.0 framework.
I am coming from having a fair amount of code invested in the 3.1 version and so went to do a conversion.
This was, I'm afraid, abandoned.
XNA 4.0 seems to take out far too many helper functions and workflows and gives, well, nothing to the PC programmer. Formats/enums removed, breaking changes to vertex handling, the list is endless...
If there were a list, I suppose that'd be something. A mob of Shawn's posts in relation to this laid out hap-hazardly does not do much good when trying to approach an upgrade.
I also use 3rd party libraries - most notably XNAnimation for skinned mesh animations. The breaking changes ensure that these no longer work either.
I have to admit, I am not an XNA guru - never got too much into the content pipeline processes and importers, which was ok in the previous XNA versions. It seems that 4.0 has raised the bar as far as knowlege requirements in the underlying technology.
What has been your experiences with the new XNA?
Do us Casual programmers just have to harden up?
It seems counter-intuitive that the breaking changes come from feature removal, not extension.
For me at least, I think 3.1 is where I'll be until the libraries catch up.
Steele.

Share this post


Link to post
Share on other sites
Advertisement
I'm currently attempting to write a game for the 360 in 4.0 with VS 2010, however I'd like to remove some of the code/objects into a library for future games(First person camera, a debugging text display, etc...). VS 2010 throws an error regarding the library that requires a .config file to be added to the game application to tell it to use the library.

Share this post


Link to post
Share on other sites
I think PC developers are just expected to abandon XNA 4.0 and stick to 3.1 or go over to SlimDX.

Microsoft has taken the stance from 4.0 onward to remove almost all the PC-only features from the framework to keep the API more cross compatible between environments, despite the fact that they have several things that only work on WP7 and the 360. I kind of feel like the we're basically the odd man out.

Share this post


Link to post
Share on other sites

We had much the same discussion just a few days ago and I'm ok with sticking to XNA 3.1 for my PC projects, more so since much of my codebase is also in 3.1 and it looks like a pain to migrate. However...

It would be nice if a friendly MVP could check with MS how long 3.1 is going to be supported

If the answer is not long or otherwise not comforting, I think investing in the learning curve for SlimDX starts to look more appealing.

Share this post


Link to post
Share on other sites
Quote:
Original post by WWakerFAN
I do quite like the changes where something hasn't been removed.


Which changes would that be for a PC user? To be sure, I'm not challenging you to defend anything, I'm just curious. For me personally moving up to XNA3.1 already meant some loss of control and fighting the API, so I'm growing increasingly hesitant to upgrade to 4.0

Share this post


Link to post
Share on other sites
Quote:
Original post by remigius
It would be nice if a friendly MVP could check with MS how long 3.1 is going to be supported


If one of us did tell you that person wouldn't be an MVP for long. If you have a project that's going to take any length of time to develop you'd be better off not tempting fate and just using 4.0.

Share this post


Link to post
Share on other sites
Quote:
Original post by Crow-knee
I also use 3rd party libraries - most notably XNAnimation for skinned mesh animations. The breaking changes ensure that these no longer work either.
I have to admit, I am not an XNA guru - never got too much into the content pipeline processes and importers, which was ok in the previous XNA versions. It seems that 4.0 has raised the bar as far as knowlege requirements in the underlying technology.

Not really. They've actually made things easier for developing for Windows Phone 7. Development for Xbox and PC really hasn't changed.

Quote:
Original post by Crow-knee
What has been your experiences with the new XNA?

Haven't had any problems with it.

Quote:
Original post by Crow-knee
Do us Casual programmers just have to harden up?

I don't know if you'd consider me a casual programmer since I've been using it from the first beta, but change is part of the game industry. I'm surprised when people have problems with it.

Quote:
Original post by Crow-knee
It seems counter-intuitive that the breaking changes come from feature removal, not extension.

I don't understand this. Almost all of the changes are related to Windows Phone 7, which is new.

Share this post


Link to post
Share on other sites
I don't think SlimDX is a good alternative to XNA. Sure it allows you to use C#, but it provides no framework, content pipeline, etc. It is just a managed wrapper of Direct3D (which has its uses), but is not as friendly as XNA. For example, in SlimDX you would to reimplement the SpriteBatch and all the 2D drawing code that just works out of the box with XNA.

Share this post


Link to post
Share on other sites
Machaira, I am somewhat surprised at your comments. You say that nothin has changed really for windows apps, yet I have experienced so many incompatibilities with my 3.1 code base that the effort to convert amounts to significant redesign and rework. I am not alone in this either, just check the creator club forums for a taste.
I work in web application in my day job, and one of the things we can never do, is remove functionality from the user - even if it is technically difficult when moving to new platforms. It is very poor business. But given the nature of change in programming, you can expect such things from time to time, but on this occasion, with the lack of cohesive documentation on the upgrade process, I find the upgrade a barrier, not an advancement.
Don't get me wrong, the tuts on the new stuff are great. The new bits are nice.
It's the workflow from existing to new which is poor. Where my project was at the stage of dealing in high level objects, now has to have it's basic objects and structures redefined.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!