Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.20f1
Issue ID
UUM-64619
Regression
No
Crash on GfxDeviceD3D12Base::DrawBuffersCommon while using Direct3D12 as the graphics API and trying to read from _CameraDepthTexture
Reproduction steps:
1. Open the attached "crash_IN-66281" project
2. Observe the crash
Reproduced with: 2022.3.20f1
Not reproduced with: 2023.2.11f1
Couldn’t test with: 2021.3.35f1, 2023.3.0b8 (couldn’t open the project due to compilation errors caused by some Scripts located in the “\Assets\EDRP\Runtime” folder)
Reproduced on: Windows 10 (22H2)
Not reproduced on: No other environments tested
Notes:
- Couldn’t find the “Fixed in“ version. Earliest not reproducible version after 2022.3.20f1 is 2023.1.0a24. For 2023.1.0a1-2023.1.0a23 it was not possible to resolve the compilation errors appearing while launching the project
- If the crash doesn’t appear while opening, make sure that the “Graphics API” in the “Project Settings…“ is set to “Direct3D12“ and “Direct3D11“ is removed
First few lines of the stack trace:
0x00007FF7E8B5192B (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FF7E8B50BCE (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FF7E8B50E50 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FF7EA18A752 (Unity) GfxDeviceWorker::RunCommand
0x00007FF7EA18D4DB (Unity) GfxDeviceWorker::RunExt
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.