Search Issue Tracker
Active
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.}}"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leaks occur when Shader with more than 128 keywords is compiled
- Player built for Windows silently crashes when UI Prefab is instantiated and Render Feature "Render Objects" is active in PC_Renderer Asset
- Crash on CollectUsedSceneObjects when making any modifications and saving in a Scene with a specific GameObject Component enabled
- VFX Graph Properties Transform has a click animation when clicked on the “Transform” text but the drop down does not open
- "Cascade Shadow atlasing has failed" errors are spammed when two Directional Lights with the Shadow Map are enabled and there is a 3D GameObject in the scene
Add comment