XBOX 360 Getting Starting - Revision history

Gunz4Hire: /* Step-by-step guide for installing Unity for Xbox 360: */

2020-07-13T22:30:28Z

Step-by-step guide for installing Unity for Xbox 360:

Gunz4Hire: /* Step-by-step guide for installing Unity for Xbox 360: */

2020-07-13T22:11:38Z

Step-by-step guide for installing Unity for Xbox 360:

Gunz4Hire: /* Avatars */

2020-06-08T02:01:06Z

Avatars

Gunz4Hire: /* Avatars */

2020-06-08T02:00:31Z

Avatars

Gunz4Hire: /* Controller */

2020-06-08T01:53:37Z

Controller

Gunz4Hire at 22:32, 7 June 2020

2020-06-07T22:32:56Z

Gunz4Hire at 22:28, 7 June 2020

2020-06-07T22:28:04Z

Gunz4Hire: /* Debugging */

2020-06-07T22:24:52Z

Debugging

Gunz4Hire at 22:23, 7 June 2020

2020-06-07T22:23:22Z

Gunz4Hire: /* Controller */

2020-06-07T22:20:09Z

Controller

@@ Line 34: / Line 34: @@
 #Install Xbox for Unity.
 #Install Unity 3D Patcher.
 === Build information: ===

@@ Line 32: / Line 32: @@
 #Set up a default devkit or testkit in your Xbox 360 Neighborhood.
 #Install Unity.
 === Build information: ===
 *XDK version: November 2012, #21250.7.

@@ Line 310: / Line 310: @@
 - Make sure a user is signed in: UnityEngine.X360Core.RequestSignIn() when requesting user avatars.
 - Issue an avatar load: UnityEngine.X360Avatars.RequestLocalUserAvatar() or any other Request function.
 - Handle the OnAvatarLoaded(UnityEngine.X360AvatarModel model, IntPtr avatarAssets) callback.
 * X360AvatarModel contains a Mesh with multiple subsets (X360AvatarModel.batchCount). It is a rough wrapper around XAVATAR_ASSETS (see XAvatar Structures in Xbox 360 SDK Documentation). Hold on to it for as long as the Avatar is required.

@@ Line 309: / Line 309: @@
 - Make sure a user is signed in: UnityEngine.X360Core.RequestSignIn() when requesting user avatars.
-- Issue an avatar load: UnityEngine.X360Avatars.RequestLocalUserAvatar() or any other Request* function.
+- Issue an avatar load: UnityEngine.X360Avatars.RequestLocalUserAvatar() or any other Request function.
 - Handle the OnAvatarLoaded(UnityEngine.X360AvatarModel model, IntPtr avatarAssets) callback.
 * X360AvatarModel contains a Mesh with multiple subsets (X360AvatarModel.batchCount). It is a rough wrapper around XAVATAR_ASSETS (see XAvatar Structures in Xbox 360 SDK Documentation). Hold on to it for as long as the Avatar is required.

@@ Line 175: / Line 175: @@
 ! No. !! Button Name !! KeyCode !! Axis# !! Comments
 |-
-| 1 || Guide Button || N/A || N/A || Use the X360Core Class "X360Core.IsSystemUIVisible()"
+| 0 || Guide Button || N/A || N/A || Use the X360Core Class "X360Core.IsSystemUIVisible()"
 |-
-| 2 || A(Green) || JoyStickButton0 || N/A ||
+| 1 || A(Green) || JoyStickButton0 || N/A ||
 |-
-| 3 || B(Red) || JoyStickButton1 || N/A ||
+| 2 || B(Red) || JoyStickButton1 || N/A ||
 |-
-| 4 || X(Blue) || JoyStickButton2 || N/A||
+| 3 || X(Blue) || JoyStickButton2 || N/A||
 |-
-| 5 || Y(Yellow) || JoyStickButton3 || N/A ||
+| 4 || Y(Yellow) || JoyStickButton3 || N/A ||
 |-
-| 6 || Left Stick || JoyStickButton8 || Axis 1 (X) - Horizontal, Axis 2 (Y) - Vertical || Range [–1; 1]
+| 5 || Left Stick || JoyStickButton8 || Axis 1 (X) - Horizontal, Axis 2 (Y) - Vertical || Range [–1; 1]
 |-
-| 7 || Right Stick || JoyStickButton9 || Axis 4 - Horizontal, Axis 5 - Vertical || Range [–1; 1]
+| 6 || Right Stick || JoyStickButton9 || Axis 4 - Horizontal, Axis 5 - Vertical || Range [–1; 1]
 |-
-| 8 || Dpad || Example || Axis 6 - Horizontal, Axis 7 - Vertical || Set {–1; 0; 1}
+| 7 || Dpad || Example || Axis 6 - Horizontal, Axis 7 - Vertical || Set {–1; 0; 1}
 |-
-| 9 || Back || JoyStickButton6|| N/A ||
+| 8 || Back || JoyStickButton6|| N/A ||
 |-
-| 10 || Start || JoyStickButton7 || N/A ||
+| 9 || Start || JoyStickButton7 || N/A ||
 |-
-| 11 || Left Trigger || N/A || Axis 9 || Range [0; 1]
+| 10 || Left Trigger || N/A || Axis 9 || Range [0; 1]
 |-
-| 12 || Right Trigger || N/A || Axis 10 || Range [0; 1]
+| 11 || Right Trigger || N/A || Axis 10 || Range [0; 1]
 |-
-| 13 || Left Bumper || JoyStickButton4 || N/A ||
+| 12 || Left Bumper || JoyStickButton4 || N/A ||
 |-
-| 14 || Right Bumper || JoyStickButton5 || N/A ||
+| 13 || Right Bumper || JoyStickButton5 || N/A ||
 |}
 ==Debugging==

← Older revision		Revision as of 22:32, 7 June 2020
Line 275:		Line 275:
	* MyScript_Update is the Update function of MyScript.		* MyScript_Update is the Update function of MyScript.
	* plt_UnityEngine_Rect__ctor_single_single_single_single is the constructor of UnityEngine.Rect with 4 arguments.		* plt_UnityEngine_Rect__ctor_single_single_single_single is the constructor of UnityEngine.Rect with 4 arguments.
		+
		+
		+	==Title Updates==
		+	===How to build a title update===
		+	To create a title update follow the “Title Updates on Xbox 360” page in the Xbox 360 SDK Documentation.
		+
		+	- Store the output of your original game build after release.
		+	- Use the same Unity version for the update (or an updated one that has been approved).
		+	- If updating scripts:
		+	* Include the updated .def and .mono files.
		+	* If using the same Unity version for the update, only the Assembly-* files need to be updated.
		+	* If code stripping was enabled in the original game build, all assemblies will most likely need to be updated (with the exception of tiny bigfixes).
		+	* If title update contains a lot of new code and forces the in-memory size of any assembly to decrease/increase below/above the next multiple of 64KB, the relocation address of multiple assemblies will change and all assemblies will need to be updated.
		+	- If updating assets:
		+	* Build them with UncompressedAssetBundle flag.
		+	* Add custom code to call AssetBundle.CreateFromFile.
		+	* Load asset bundles from the UPDATE: mount that will become available when the title update is applied.
		+
		+
		+	==Kinect==
		+	===Kinect Editor Window===
		+
		+	In Unity you can test your Kinect based projects from within the Unity editor. Firstly you need to create Kinect recording(s) from Microsoft’s Xstudio tool. This is located: WindowsOS Start->All Programs->Microsoft Xbox 360 SDK->Natural Input->Xbox Studio or via C:\Program Files (x86)\Microsoft Xbox 360 SDK\bin\win32\Xstudio.exe
		+
		+	* Place the Microsoft XStudio recordings (.xed files) into your Unity project
		+	* In Unity open the kinect window - located at the menu bar Window->Xbox 360->Kinect
		+	* Start your project in the editor (main play button)
		+	* In the kinect window Select the recording from the dropdown and press play
		+
		+
		+	==Avatars==
		+	===Avatars===
		+	Unity provides a simple way to load Avatar resources - see Scripting API reference for UnityEngine.X360Avatars Displaying an avatar step by step:
		+
		+	- Make sure a user is signed in: UnityEngine.X360Core.RequestSignIn() when requesting user avatars.
		+	- Issue an avatar load: UnityEngine.X360Avatars.RequestLocalUserAvatar() or any other Request* function.
		+	- Handle the OnAvatarLoaded(UnityEngine.X360AvatarModel model, IntPtr avatarAssets) callback.
		+	* X360AvatarModel contains a Mesh with multiple subsets (X360AvatarModel.batchCount). It is a rough wrapper around XAVATAR_ASSETS (see XAvatar Structures in Xbox 360 SDK Documentation). Hold on to it for as long as the Avatar is required.
		+	* avatarAssets is a pointer to XAVATAR_ASSETS valid during the callback. It may be passed to a plugin.
		+	- X360AvatarModel.Mesh can be used in Unity as a normal Mesh.
		+	- Avatar vertex buffers contain extra UV channels (half2) in certain cases:
		+	*Head: TEXCOORD2 through TEXCOORD5 for:
		+	*Eyebrow texture.
		+	*Eye texture.
		+	*Mouth texture.
		+	*Eye shadow texture.
		+	*Non-shiny body parts: TEXCOORD2 for the decal texture.
		+	*Data from these extra channels can not be accessed from scripts.
		+
		+	===Shaderlab extensions===
		+	In order to support Avatar rendering, shaderlab was extended to allow for more UV sets on Xbox 360. In case of surface shaders, those UV sets are only accessible when #pragma only_renderers xbox360 is set.
		+
		+	===Example project:===
		+	See “Xbox 360 - Avatar Rendering Example” package.
		+
		+	==Known Issues==
		+	===Known Issues===
		+	* Mono threads will currently only run on thread 4.
		+	* Image effects from the Standard Assets package are not modified to benefit from RenderTexture.DiscardContents.
		+	===Known Crashes===
		+	* Certain crashes are developer’s responsibility to fix and are not handled by Unity:
		+	* It is mandatory to have at least one Rich Presence string in the Xbox Live game configuration. Failing to do so will cause a crash in SendToLive@PresenceCollection (see callstack).

← Older revision		Revision as of 22:28, 7 June 2020
Line 250:		Line 250:
	# Known issues:		# Known issues:
	* Floating point registers may be trampled in the current version. Take care when debugging around plugin invocation code that uses floating point values.		* Floating point registers may be trampled in the current version. Take care when debugging around plugin invocation code that uses floating point values.
		+
		+
		+	==Profiling==
		+	===Unity Profiler===
		+	Unity editor can attach to a development player running on any Xbox on the network.
		+
		+	# Run your build.
		+	# Activate Windows->Profiler.
		+	# Select XenonPlayer(YOUR_XBOX_NAME) as the active profiler.
		+	# Use the profiler as usual.
		+
		+	===PIX Timing Capture===
		+	Timing capture can be used like for any normal Xbox application.
		+
		+	===PIX GPU Trace===
		+	GPU trace can be used like for any normal Xbox application.
		+
		+	===PIX CPU Trace===
		+	CPU trace can be used like for any normal Xbox application. Navigate to “Functions->Module” tab and load any missing symbol files from BUILD_TARGET\Media\Managed.
		+
		+	* Assembly* files are generated from your Unity scripts.
		+	* Other libraries with AOTCompileStep in their paths are also Unity related. Symbol names do not match those in your scripts exactly, but they can be easily interpreted. Examples:
		+	* plt_UnityEngine_Screen_get_width is the getter of UnityEngine.Screen.width.
		+	* MyScript_Update is the Update function of MyScript.
		+	* plt_UnityEngine_Rect__ctor_single_single_single_single is the constructor of UnityEngine.Rect with 4 arguments.

@@ Line 226: / Line 226: @@
 # Note: Make sure to save ‘MiniDump with heap’ otherwise symbols will not load.
-Explicit Null Checks
+===Explicit Null Checks===
 In case you’re only interested in hunting down your null ref bugs, this is your best bet. Enabling the feature will:
@@ Line 232: / Line 232: @@
 # Output the managed callstack, i.e.: [F9000000:] EXCEPTION handling: NullReferenceException NullReferenceException: A null value was found where an object instance was required. at MyScript.BadFunction () [0x00023] in C:\MyExample\Assets\MyScript.cs:19 at MyScript.Start () [0x00000] in C:\MyExample\Assets\MyScript.cs:23 Note that NullReferenceException will NOT work in non-development(Release) builds.
-Debugging shaders via PIX (Automatic UPDB generation)
+===Debugging shaders via PIX (Automatic UPDB generation)===
 To enable PIX debugging of shaders.
-In the Windows system registry (regedit), create a DumpShaderPdbDir string registry entry in the HKEY_CURRENT_USER\Software\Microsoft\XenonSDK\ subkey. Within the registry entry, specify a directory on your PC where UPDB files will be automatically generated.
+# In the Windows system registry (regedit), create a DumpShaderPdbDir string registry entry in the HKEY_CURRENT_USER\Software\Microsoft\XenonSDK\ subkey. Within the registry entry, specify a directory on your PC where UPDB files will be automatically generated.
-In Unity re-import the .shaders files (Shader opcode generation occurs during import time not at build time).
+# In Unity re-import the .shaders files (Shader opcode generation occurs during import time not at build time).
-Build and run your Unity project.
+# Build and run your Unity project.
-Launch PIX and perform a “Record GPU” [ctrl+G]
+# Launch PIX and perform a “Record GPU” [ctrl+G]
-Launch the PIX analysis app [F5]
+# Launch the PIX analysis app [F5]
-Select the DrawIndexPrimitive of interest and select Shaders tab. Periodic clearing of the UPDB folder might be required.
+# Select the DrawIndexPrimitive of interest and select Shaders tab. Periodic clearing of the UPDB folder might be required.
 Script Debugging with MonoDevelop
-Detach Xbox Watson! Script debugging does not work if a debugger is attached.
+===Script Debugging with MonoDevelop===
-Enable script debugging in the build settings window.
+# Detach Xbox Watson! Script debugging does not work if a debugger is attached.
-Build and run your project.
+# Enable script debugging in the build settings window.
-Attach MonoDevelop to an instance of “XenonPlayer”.
+# Build and run your project.
-Use as normal.
+# Attach MonoDevelop to an instance of “XenonPlayer”.
-Known issues:
+# Use as normal.
-Floating point registers may be trampled in the current version. Take care when debugging around plugin invocation code that uses floating point values.
+# Known issues:

← Older revision		Revision as of 22:23, 7 June 2020
Line 203:		Line 203:
	\| 14 \|\| Right Bumper \|\| JoyStickButton5 \|\| N/A \|\|		\| 14 \|\| Right Bumper \|\| JoyStickButton5 \|\| N/A \|\|
	\|}		\|}
		+
		+
		+	==Debugging==
		+	===Xbox Watson===
		+	Keeping Xbox Watson attached to the kit you’re testing on is always a good idea for the visibility of debug output. If your project crashes, you will get output similar to this: Exception : 4177526784 3221225477 2281767608 FirstChance. Here’s how to interpret it:
		+
		+	# Convert it to hex to get Exception : 0xF9000000 0xC0000005 0x880102B8 FirstChance.
		+	# The second value is the exception type (i.e. 0xC0000005 is EXCEPTION_ACCESS_VIOLATION).
		+	# The third value is the instruction address (i.e. 0x880102B8).
		+	# Look for previous output mentioning loaded DLLs, i.e.: Loaded DLL Assembly-CSharp.dll.xex (\Device\Harddisk0\Partition1\DEVKIT\Unity\Media\Managed\Assembly-CSharp.dll.xex); Mapped 0x88000000 thru 0x88030000
		+	# If the instruction address is in the mapped range of a DLL, it’s the culprit.
		+	# This method is not very informative.
		+
		+	===Crash Dumps===
		+	Crash dumps are saved on your devkit (DEVKIT\dumps) if Watson is not attached, otherwise dumps can be saved directly to your pc. Once a crash dump is on your development machine it can be examined like this:
		+
		+	# Open the dump in Visual Studio.
		+	# Start debugging.
		+	# Load symbols for your managed code from BUILD_TARGET\Media\Managed.
		+	# Examine the callstack, etc.
		+	# Known issue: Visual Studio currently displays only the top function when in compiled script code.
		+	# Note: Make sure to save ‘MiniDump with heap’ otherwise symbols will not load.
		+
		+	Explicit Null Checks
		+	In case you’re only interested in hunting down your null ref bugs, this is your best bet. Enabling the feature will:
		+
		+	# Throw a NullReferenceException.
		+	# Output the managed callstack, i.e.: [F9000000:] EXCEPTION handling: NullReferenceException NullReferenceException: A null value was found where an object instance was required. at MyScript.BadFunction () [0x00023] in C:\MyExample\Assets\MyScript.cs:19 at MyScript.Start () [0x00000] in C:\MyExample\Assets\MyScript.cs:23 Note that NullReferenceException will NOT work in non-development(Release) builds.
		+
		+	Debugging shaders via PIX (Automatic UPDB generation)
		+	To enable PIX debugging of shaders.
		+
		+	In the Windows system registry (regedit), create a DumpShaderPdbDir string registry entry in the HKEY_CURRENT_USER\Software\Microsoft\XenonSDK\ subkey. Within the registry entry, specify a directory on your PC where UPDB files will be automatically generated.
		+	In Unity re-import the .shaders files (Shader opcode generation occurs during import time not at build time).
		+	Build and run your Unity project.
		+	Launch PIX and perform a “Record GPU” [ctrl+G]
		+	Launch the PIX analysis app [F5]
		+	Select the DrawIndexPrimitive of interest and select Shaders tab. Periodic clearing of the UPDB folder might be required.
		+	Script Debugging with MonoDevelop
		+	Detach Xbox Watson! Script debugging does not work if a debugger is attached.
		+	Enable script debugging in the build settings window.
		+	Build and run your project.
		+	Attach MonoDevelop to an instance of “XenonPlayer”.
		+	Use as normal.
		+	Known issues:
		+	Floating point registers may be trampled in the current version. Take care when debugging around plugin invocation code that uses floating point values.