Share via

Why does everyone seem to think the XNA Framework is only XBox?

  • Article

In the comments section of my last post (not including the april fools joke) many people are talking about how MDX2 is 'dead' and they can't afford an XBox dev kit, etc..

I'm not entirely sure where the confusion of ideas has come from.  The XNA Framework is going to be cross platform.  This means that it will run on Windows.  XBox 360 (and thus development kits) is not a requirement for using the framework at all.  You will be able to use the framework and write games for Windows even if you've never seen an Xbox 360 before.

While MDX2 as a name may be "dead", many of the API's in the framework will look quite familiar to developers who have used MDX2.  I also enjoy reading everyone discussing how much things are going to cost ignoring the facts that:

  • We haven't said anything about availability or pricing
  • The DirectX SDK is already free

Everyone seems to be getting all up in arms by jumping to conclusions, and making a lot of bold assumptions.  At least let us announce our plans,etc before you go off predicting such doomsday scenarios..

Before you ask, no, I'm not aware of when we'll be announcing more of the plans.  So I guess everyone will continue to assume the worst until we either verify their fears or disprove them. :p

(Edit: I can't spell obviously)

Comments

  • Anonymous
    April 11, 2006
    I think, with J. Allard initially being the "front man" for the XNA framework, kinda made it look like Xbox (and Xbox360).

    I think as time goes on, people will realize it.

  • Anonymous
    April 11, 2006
    I've always considered XNA to be an Xbox thing, integrating MDX into to just sounds like an easy way for people to write xbox games, the cross-platform part seems to have gotten lost in the excitement of the thought of non-expert programmers developing an application which could work on an xbox!

    Also, the April 06 SDK disappointed cos even though MDX2 is 'dead' as you said, there was no documentation for the 'dead' libraries which supposedly you were working on. Even half-finished docs would be good, something to make all the changes clearer so we can get ready for XNA properly

  • Anonymous
    April 11, 2006
    "development kids" - thankfully we won't be needing those ;)

    I've seen and tried to answer a few questions on this already and without more info about XNA's availability, featureset and pricing, sticking with MDX1.1 for the time being seems to be the smartest choice for most people out there.

    Could we get an official comment on that? :)

  • Anonymous
    April 11, 2006
    "XBox 360 (and thus development kids)"

    I am guesssing that is a typo. Or does one get them free with the dev kit? :)

    yes, XNA sounded more inclined, infact totally for XBOX, however logically didnt make any sense considering the 2 main gaming platforms.

    Anyways, the new Mnaged Directx book was to be released today. Delayed ? Canceled ? being updated ?

    Thanks

  • Anonymous
    April 11, 2006
    "(Edit: I can't spell obviously)"

    obviously

  • Anonymous
    April 11, 2006
    The comment has been removed

  • Anonymous
    April 11, 2006
    People are talking about the latest release of the DirectX SDK (April 2006) on <a href="http://www.gamedev.net/community/forums/topic.asp?topic_id=386587">gamedev.net</a> , and some are saying it's better to stick with 1.1.  What do you think?

  • Anonymous
    April 12, 2006
    All kidding aside (pun intended ;), could you please give the official word on my previous question? Is MDX1.1 currently indeed the officially recommended platform for developing MDX apps in both .NET1.1 and .NET2.0?

    I'll be writing an article about MDX soon and I'd like to get this straight.

  • Anonymous
    April 13, 2006
    One question. Beacause some of the functionally in Diret3D is not avalable for the XBox that this mean that the MDX2 -Direct3D- XNA will be less powerfull that DIRECT3D 10?

  • Anonymous
    April 17, 2006
    snip ...XNA's availability, featureset and pricing... end snip

    The word PRICING makes me a bit wonky here. Hopefully we don't have to pay for the libraries to develop on Windows?

    The whole XNA marketing is a mess. Would be nice to announce what will happen in the future, and maybe a timeline when it will happen. This XNA-stuff gets some Duke Nukem Forever touch... it's done when it's done. Welcome to Vaporware awards.

    The DirectX SDK indeed is free. Nice. And completely pointless for .NET programmers, as the featureset is frozen now on 1.1.

    Just my 2 cents of bold assumptions.

  • Anonymous
    May 29, 2009
    PingBack from http://paidsurveyshub.info/story.php?title=tom-miller-s-blog-why-does-everyone-seem-to-think-the-xna-framework

  • Anonymous
    June 15, 2009
    PingBack from http://debtsolutionsnow.info/story.php?id=11448