UWP Enhanced Access

I’ve been having trouble with getting a decent framerate on my UWP Unity game after deploying to Xbox one, so i was excited to hear much more system resources are available with the new Fall Creators update. However, I don’t understand if these new resources are used automatically, or how to access them. Xbox dev portal does not show i’m hitting performance limits. I haven’t noticed an improvement in performance although a DirectX12 build now does seem to work. Any advice? Thanks

Make sure that you are pushing a Release or Master build to the Xbox. I have noticed significant performance decrease with Debug builds.

I am also interested in the answer to your question regarding access to the extra resources on Xbox One, though.

Okay I think I found an answer here

https://social.msdn.microsoft.com/Forums/en-US/41791573-e078-4840-8d69-11b5581a341e/uwpxboxdxc-xbox-one-expanded-resources-in-fall-creators-update?forum=wpdevelop

following the instructions causes my game to crash on launch though

What kind of a crash is it? Do you have a stacktrace?

It gives this error. If i restart the console then it doesn’t give an error it just goes to black screen then back to dev home.

I ran into the same problem a while ago and it turns out there exist at least two issues:

  • GPU Instancing is broken

  • Dynamic batching doesn’t work in a build

(Case 946966) GPU Instancing significantly slower than no batching at all (UWP/Xbox One)
https://discussions.unity.com/t/675736

(Case 946946) Dynamic Batching not working in a Player
https://discussions.unity.com/t/675719

Perhaps @PJayB has any news regarding the GPU Instancing issue?

I solved the crashing on startup issue by selecting auto graphics API in the editor. The trouble is that full access to the xbox GPU is only available with DX12. If i force DX12 the game runs in App mode but will not launch in Game mode it just restarts dev home

@Mullan7 did you try attaching native mode debugger to the app to see where it’s crashing?

@Peter77 the instancing issue was identified to be a bug in Xbox One DirectX driver stack. We forwarded to Microsoft and they will be fixing it.

1 Like

I’ve actually managed to reproduce this issue. Looks like something is wrong with the developer mode while running in d3d12 mode:

We’ll investigate.

1 Like

I eventually got it to work. The trick was just to restart the xbox after changing application type