Search Unity

Xbox One -Platform windows 10 64bit with device Direct3d11 is not supported with High Definition Ren

Discussion in 'Windows' started by LoopIssuer, May 11, 2021.

  1. LoopIssuer

    LoopIssuer

    Joined:
    Jan 27, 2020
    Posts:
    109
    Hi,
    I am trying to build and deploy game to Xbox One and get this error:

    Platform windows 10 64bit with device Direct3d11 is not supported with High Definition Rendering Pipeline, no rendering will occur

    Tried on different versions of Unity:
    2019.2.5f1 + HDRP 6.9.1
    2019.4.17f1 + HDRP 7.3.1

    I'm building UWP application and deploying with Rmote Machine (game starts with error, rendering fails).
    When building UWP, deploying and launching directly from Xbox - game runs with black screen.

    Please help.
     
    LoopIssuer, May 11, 2021
    #1

  2. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Xbox one doesn't support Compute shaders via UWP on D3D11. And HDRP requires that. You need to switch to D3D12 if you want to use HDRP on Xbox One on UWP.
     
    Tautvydas-Zilys, May 12, 2021
    #2
    cjjeffery likes this.

  3. LoopIssuer

    LoopIssuer

    Joined:
    Jan 27, 2020
    Posts:
    109
    Thanks for the answer, but how to do that? I mean - how to switch to direct12 on Xbox?

    Is it the option when Auto graphics API is disabled?
     
    LoopIssuer, May 12, 2021
    #3

  4. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Yeah, disable Auto graphics API and make sure only D3D12 is in the list. Also, make sure the game runs in "Game mode", not "App Mode" (otherwise it will fail to initialize D3D12).
     
    Tautvydas-Zilys, May 12, 2021
    #4

  5. LoopIssuer

    LoopIssuer

    Joined:
    Jan 27, 2020
    Posts:
    109
    Thanks!

    It works!

    But...
    Now I have error - d3d12 generating mipmaps is not yet supported.
     
    Last edited: May 12, 2021
    LoopIssuer, May 12, 2021
    #5

  6. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Do you know where that is coming from?
     
    Tautvydas-Zilys, May 12, 2021
    #6

  7. LoopIssuer

    LoopIssuer

    Joined:
    Jan 27, 2020
    Posts:
    109
    LoopIssuer, May 12, 2021
    #7

  8. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    What are your PC specs? What resolution are you running at? Which player config (debug/release/master) are you using?
     
    Tautvydas-Zilys, May 12, 2021
    #8

  9. LoopIssuer

    LoopIssuer

    Joined:
    Jan 27, 2020
    Posts:
    109
    Pc specs:
    Processor Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz 2.30 GHz
    Installed RAM 16.0 GB (15.9 GB usable)
    System type 64-bit operating system, x64-based processor

    Resolution 1920x1080

    Player config - I think I tried Debug and Release.


    I built a sample project for Xbox - sample scene from HDRP template (the one with workshop).
    There was only 15 FPS on Xbox.

    I tried to make some modifications to the HDRP config:
    -sample project - 30 FPS
    -my game - 5 FPS

    Please help. Maybe there is some "HDRP config for Xbox one" or for low end PC and it would help?
     
    Last edited: May 12, 2021
    LoopIssuer, May 12, 2021
    #9

  10. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Make sure to not run in debug. Other than that, I suggest using the profiler.
     
    Tautvydas-Zilys, May 13, 2021
    #10

  11. deadlycrow

    deadlycrow

    Joined:
    Feb 10, 2014
    Posts:
    166
    Hi, i have this same problem, and i did switched to D3D12 but the problem is still happening... what else can i try?
     
    deadlycrow, Oct 17, 2021
    #11

  12. Tautvydas-Zilys

    Tautvydas-Zilys

    Unity Technologies

    Joined:
    Jul 25, 2013
    Posts:
    10,680
    Two things:

    1. Make sure the game is configured to run as a "Game" rather than "App". This is a setting on the xbox itself.
    2. Make sure it's actually using D3D12 (perhaps the switch didn't take effect). You can do that by either looking at the player log or printing out SystemInfo.graphicsDeviceType.

    BTW I saw your other post. I am sorry it is frustrating to work with it. Those bad links in documentation are bugs - please report them if you find any. We don't try to obfuscate information about Xbox development via UWP at all. And feel free to ask any questions on this forum.

    Regarding ID@XBOX program, we are bound by NDAs from Microsoft and cannot legally disclose things publicly.
     
    Tautvydas-Zilys, Oct 18, 2021
    #12
    samarthmp8 likes this.