Copyright © 2026 Unity Technologies
Thank you for reporting a bug to Unity. We have investigated the issue but were unable to reproduce it with the information provided. This can happen due to differences in environment, project setup, or steps taken. We will close this case for now. If you're able to share additional details such as different projects, steps, hardware/software configuration, or logs - please let us know, and we'll be happy to re-evaluate.
Unity 6000.2 has reached its end of life and will not receive further updates. If you need additional fixes, please upgrade to a newer Unity version.
Cancelling: the 6000.1 version has reached its end of life. If you need additional fixes, please upgrade to a newer Unity version.
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:
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
Issues you vote on will appear here