Search Issue Tracker
Active
Under Consideration for 6000.1.X
Votes
0
Found in
6000.1.2f1
Issue ID
UUM-105801
Regression
No
Crash on D3D12DeviceState::ApplyRenderTargets when creating a new "Get Started With Unity" project
Reproduction steps:
1. In Unity Hub, create and open a new project with the “Get Started With Unity” (com.unity.template.get-started-1.0.1.tgz) template
2. Observe the crash
Reproducible with: 6000.1.0f1, 6000.1.1f1, 6000.1.2f1
Reproducible on: Windows 11 (24H2) (reporter), Windows 10 (22H2) (another reporter)
Not reproducible on: No other environments tested
Notes:
* Not reproduced by CQA
* Some users can reproduce the same crash when opening their existing projects
* All known crashes with this stack trace are on Windows 10 and Windows 11
* Known duplicates consist of Intel integrated GPUs and an AMD Radeon RX 5700 XT
First few lines of the stack trace:
0x00007FFAA53C1BE2 (Unity) D3D12DeviceState::ApplyRenderTargets
0x00007FFAA53CFA57 (Unity) D3D12DeviceState::Transition
0x00007FFAA538F2BB (Unity) D3D12CommandListWithState::ApplyStateClear
0x00007FFAA5392AFF (Unity) GfxDeviceD3D12Base::Clear
0x00007FFAA6B23EE6 (Unity) GfxDeviceWorker::RunCommand
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
- [Android] Light2D visuals stacking over frames when using RenderGraph
Add comment