Posted 12 May 2003 - 01:21 PM
Posted 12 May 2003 - 03:14 PM
Posted 12 May 2003 - 03:18 PM
You're going to need to find (who knows where) the MS "XDK" or "Xbox Dev. Kit" why it isn't the XSDK I don't know, but consistency of product isn't MS' biggest issue. It's what you'll need to compile your sources (C, VB, basically any direct languagebase that Visual Studio does) into executables that run in the xbox's execution environment.
Apparently it's predominantly DirectX-controlled, which isn't surprising, but that also means you're gonna have to draw all of your own RECTs for any kind of window class you'll want, rather than having a prebuilt set to reference from. Not all that bad, really; a lot less to worry about than normal PC programming, but the lack of readily available information and reliable sources for support can hinder your progress greatly.
Check for help int eh development forums and on IRC. Also talk to some of the people who currently develop for the box, there are many projects you can possibly help out with to start into X development, or at least make enough connections so that you know where to go for support, etc.
Good luck in your development efforts.
Posted 12 May 2003 - 03:22 PM
You'll find a way around hurdles without talking to MS. I mean really, do you want 5 copies of MSDNnow! delivered to you monthly?
Posted 13 May 2003 - 03:29 PM
Now believe it or not the truth behind this reality is actually even worse than it sounds. Because almost every third party publisher will want at least some kind of working code before they touch you. For MS to back you it gets even worse.
The XDK itself is not hard to find, and once you modchip an xbox you basically have a debug xbox.(since all they are is an xbox with much larger hdd and the ability to play unsigned code.)
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users