Search Issue Tracker

By Design

Under Consideration for 6000.0.X

Votes

0

Found in

6000.0.58f1

Issue ID

UUM-119665

Regression

No

Scene is not rendered in Player when ran with -force-d3d12 argument and GPU Resident Drawer enabled

-

Reproduction steps:
1. Open the attached “IN-116749.zip” project
2. Build the project (File > Build Profiles > Build)
3. Run the .exe Player
4. Observe the scene is rendered
5. Run the Player with “-force-d3d12” argument
6. Observe the Player

Expected result: The scene is rendered
Actual result: The scene is not rendered, the Player is gray

Reproducible with: 6000.0.58f1, 6000.1.0a1
Fixed in: 6000.1.0a2
Not reproducible with: 6000.2.6f1, 6000.3.0b3, 6000.4.0a1
Couldn’t test with: 2023.3.0a1 (GPU Resident Drawer not available)

Reproducible on: Windows 11
Not reproducible on: no other environments tested

Note:
- Such errors are also present in the Player.log: “{{Kernel 'MainUploadScatterInstances' not found ArgumentException: Kernel 'MainUploadScatterInstances' not found.}}"

  1. Resolution Note:

    You can't run a standalone player forcing a specific gfx api if project wasn't build with this gfx API.
    Repro project is set to "auto graphics API", so it only contains directx11 API by default till Unity 6.0.
    If you try to run player with -force-d3d12 it can't render properly because of missing compute shader.

    Up to Unity 6.1 the build settings automatically include both dx11 and dx12 gfx API when building. So running standalone with "-force-d3d12" would work.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.