Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.24f1
2023.2.18f1
6000.0.0b14
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-68643
Regression
No
Crash on GfxDeviceD3D12Base::SetRayTracingShaderResources when changing Game view resolution
How to reproduce:
1. Open the “IN-72369_repro“ project
2. Open the “NewTest“ scene
3. Select Game view and change to a different Looking Glass resolution
Expected result: Resolution changes
Actual result: Editor crashes
Reproducible with: 2021.3.37f1, 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of Stack Trace:
0x00007FF6DC49A710 (Unity) GfxDeviceD3D12Base::SetRayTracingShaderResources
0x00007FF6DDA1D90C (Unity) GfxDeviceWorker::RunCommand
0x00007FF6DDA212BD (Unity) GfxDeviceWorker::RunExt
0x00007FF6DDA213D8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
Note:
- To reproduce the issue delete the Library folder before opening the project
- If the issue does not reproduce try to change the resolution up to 7 times continuously
- If a package error is thrown it can be ignored
- Sometimes a different Stack trace is seen
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
The instabilities and d3d12 device lost issue were caused by the project using all GPU memory because of the 8k resolution which made the system unresponsive.