XBOX 360 Getting Starting
Xbox 360: Getting Started
Developing for Xbox 360
To develop for the Xbox 360 you must be a Microsoft Certified Xbox 360 Developer and own the appropriate hardware. See the Xbox 360 Setup page for a seat setup checklist.
Access Xbox 360 unique functionality Unity Xbox provides a number of new scripting APIs to access Xbox Live services, storage devices, Avatars and much more. See the UnityEngine.X360 namespace in the scripting API.
How Unity Xbox differs from Desktop Unity Strongly Typed JavaScript Dynamic typing in JavaScript is always turned off in Unity on Xbox. This is the same as adding #pragma strict to your scripts, but it is done by default instead, in order to improve performance. When you launch an existing Unity Project, with dynamic typing, you will see compiler errors. You can easily fix them by either using static typing for the variables that are causing errors or taking advantage of type interface. Ahead-Of-Time (AOT) compilation Scripts are AOT compiled and loaded in as normal Xbox 360 dynamic libraries. JITing is not supported. Exotic class libraries (reflection, LINQ etc) not fully supported. Limited memory Expect about 440MB free system memory with an empty project loaded. Fixed resolution 720p (1280x720) is the only resolution you’ll have to deal with. No hardware MSAA Unity for Xbox does not do hardware MSAA. Use “AntialiasingAsPostEffect” technique “FXAA3” from the “Image Effects” standard package for best results. XMA audio compression Unity will compress audio to XMA when targeting Xbox 360. Unity will use OGG in the editor (XMA can not be played on the PC). Expect audio quality to differ and check the output Xbox produces. Only two channels are supported when load type is “Compressed in memory”. Build information: XDK version: November 2012, #21250.7.
