Microsoft burned down my home, where now?

Started by
41 comments, last by 3Ddreamer 10 years, 11 months ago

zounds...i'm really glad I wasn't the only one not picking my nose and not communicating with anyone about this issue.

On the other hand, shame on you people! I've been learning C# for awhile now, and from a developer standpoint, this is an investment. I don't have time or resources to doubt myself and reverse all the time I've spent on it now in favor of C++.

It's not about the language, it's about what you say, right?

On the other hand, XNA is/was THE ONLY WAY to port a game over to 360. Smoke that chiba for a minute. I really could care less about XNA framework for PC, but again, there is/was no other way to get your game on 360. Furthermore, I work on a graphics chip that isn't supported by XNA 4.0, therefor not supported by Monogame.

So yeah, MS did sort of burn the house down on that. Considering the overwhelming popularity of 360 in the North American market, the door is closing on Indie Devs for a console market. You could make the argument that MS is edging us out in favor of the large studios like Bethesda and Gearbox, because they HAVE NO CREATIVITY LEFT. They need the pull of Microsoft and Sony to dick us out of their field. You really think they want creative, amped-up competition from about 10,000 indie devs that have poured more heart and soul into this than a 2-year program at the Art Institute could ever buy?

yeah, sorry...I'm a novice, amateur. again, it's not about the language, it's about what you say. there's a lot of untapped potential left in the 360, but you can only sell the console to so many people before everyone's got one.

anyway, thanks for clarifying a few things I've been wondering about, also. cool community, glad it's here, just not sure where to go for Console development from here on out.

Advertisement

XNA isn't working anymore on the 360? When did that happen?

rolleyes.gif

Stefano Casillo
TWITTER: [twitter]KunosStefano[/twitter]
AssettoCorsa - netKar PRO - Kunos Simulazioni

On the other hand, XNA is/was THE ONLY WAY to port a game over to 360. Smoke that chiba for a minute. I really could care less about XNA framework for PC, but again, there is/was no other way to get your game on 360. Furthermore, I work on a graphics chip that isn't supported by XNA 4.0, therefor not supported by Monogame.

So yeah, MS did sort of burn the house down on that. Considering the overwhelming popularity of 360 in the North American market, the door is closing on Indie Devs for a console market.

Does XNA still work on the 360? Because if so whats the problem?

All this means is that MS are no longer going to develop XNA going forward which makes sense as it is a poor fit, API wise, for newer hardware which exists.

Chances are that next XBox will have an 'indie' section like the 360 and because it is expected to be built on the same foudations as Windows Phone 8 and Windows Store apps development will be along the same lines; pick your language (C++ being an option, so already indies can get ahead of the game) and go.

At least this is what I expect anyway...

...I've been learning C# for awhile now, and from a developer standpoint, this is an investment. I don't have time or resources to doubt myself and reverse all the time I've spent on it now in favor of C++...

Luckily programming skill isn't language specific. There is no reason to "reverse all the time" to switch over from C#/XNA to C++/DX/OGL since most of the actual knowledge transfers over (protip: syntax and api aren't the hard part about programming :p).

On the other hand, XNA is/was THE ONLY WAY to port a game over to 360. Smoke that chiba for a minute. I really could care less about XNA framework for PC, but again, there is/was no other way to get your game on 360. Furthermore, I work on a graphics chip that isn't supported by XNA 4.0, therefor not supported by Monogame.

If you're working on something now there's no reason why you can't continue. Microsoft didn't pull a magic switch that instantly made XNA stop working. XNA still works, they're just not updating it going forward.

Seriously, what is wrong with you people? Major platform reaches end of life and no longer gets updates does not mean that it's now impossible to use that platform. Shake off the negativity - you can still use XNA.

Direct3D has need of instancing, but we do not. We have plenty of glVertexAttrib calls.

Those "Mummy, XNA is dead" threads have occured quite often lately. I suspect this was a flame bait post, the OP was a new poster and his pseudonym is very suspicious.

And despite that you can still create a new Windows Forms app in Visual Studio today, go to References, Add Reference, pick ".NET" and all of the "Microsoft.DirectX" stuff is still available for use.

That's a cautionary lesson in the whole "WAAAHH!!! MICROSOFT KILLED XNA AND NOW I CAN DO NOTHING!!!!" drama. Despite the fact that Managed DirectX was killed years ago, it is still available for use. What is it that is causing people to think that the situation would be otherwise with XNA?

I guess I should weigh in. This is, after all, my drama in more ways than one.

Microsoft has a long tradition of deprecating but preserving technology. That's an important part of how they run their business and their commitment to it is a large part of what has made an investment in the various Windows technologies safe. Things that worked on Windows X are nearly guaranteed to be fine on Windows X+1, X+2, X+3, even more sometimes. MDX, XNA, SL are all in this category. The trouble is that most of us live in a world where technology moves on and so "will work" is a necessary but not sufficient guarantee for us to run our affairs in a productive way. That's where the split in this thread comes in.

Yes, XNA will continue to work and do what it does. That doesn't make it a good idea.

D3D 10 arrived, along with the new driver model, in Windows Vista. That was in 2007, six years ago. It's true that D3D 9 has enjoyed a particular level of stability (for various reasons), but it's time to face the music. To commit any serious resources to 9 now are strictly a function of legacy support. XNA cuts it even finer, especially with the introduction of the quirky profiles in 4 which were very, extremely poorly thought out and implemented. (Sorry Shawn.) It's an open question about where you go from there, but it's only a question of where, not if. And frankly it's well past due by now. C#/SlimDX, C#/SharpDX, C#/MonoGame, C++/D3D11, even C++/GL are all productive angles with their own pros and cons.

Obviously for indie Xbox there's only two choices: XNA or don't play. I'll leave it at that.

More generally speaking, a lot of us are growing irritated with the sheer rate that MS is deprecating, transitioning, or just plain forgetting about some of their newer technologies. That's a much different and longer conversation, but I'll say the same thing I've said before: it's no longer a Microsoft-only world of consumer computing. There's an awful lot of consumer-facing devices that aren't Windows, and that's got serious implications for how developers choose their tech. Somehow I'm not in a hurry to jump on the Metro train.

SlimDX | Ventspace Blog | Twitter | Diverse teams make better games. I am currently hiring capable C++ engine developers in Baltimore, MD.

More generally speaking, a lot of us are growing irritated with the sheer rate that MS is deprecating, transitioning, or just plain forgetting about some of their newer technologies. That's a much different and longer conversation, but I'll say the same thing I've said before: it's no longer a Microsoft-only world of consumer computing. There's an awful lot of consumer-facing devices that aren't Windows, and that's got serious implications for how developers choose their tech.

Yeah I guess we have to remember that Microsoft is a company, backed by large investors, and they need to answer to these investors. Investors only care about one thing. Making money. I remember back when Bill Gates was CEO, one investor on a conference call asked him to give less to charity, and try and generate more for the investors (or something like that). Microsoft needs to keep us buying products and spending money. So when they "deprecate" products, yeah it sucks, but I kind of understand that is just how it works. They don't just make tech to please us developers... It's a business, they need to be where the money is.

I'm totally with you (Promit) about Metro. I'm disinterested.

Somehow I'm not in a hurry to jump on the Metro train

Heh, I'm glad I'm not the only paranoid one who thinks twice before jumping on yet-another-soon-to-be-killed bandwaggon...

Unfortunately, I gotta totally agree also with the rest your Inconvenient Truth (TM).

VladR My 3rd person action RPG on GreenLight: http://steamcommunity.com/sharedfiles/filedetails/?id=92951596

XNA is mature and not dead, which actually makes developing with it easier than if it were still growing. Just like in human relationships, mature is better !

Monogame is really the way to go, but either way, games made with XNA or Monogame will run for years in people's devices.

Enjoy the development environment for years to come, stop complaining, and start making money with games soon! Construction on the doorway has practically stopped, but the Door is still open!

Clinton

Personal life and your private thoughts always effect your career. Research is the intellectual backbone of game development and the first order. Version Control is crucial for full management of applications and software. The better the workflow pipeline, then the greater the potential output for a quality game. Completing projects is the last but finest order.

by Clinton, 3Ddreamer

This topic is closed to new replies.

Advertisement