Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.60f1
6000.2.10f1
6000.3.0b7
6000.4.0a3
Issue ID
UUM-125265
Regression
No
[DX12] Crash on with multiple stack traces when rendering large Terrain with specific hardware
How to reproduce:
1. Open the attached “IN-122137.zip” project
2. Observe the crash
Reproducible in: 2023.2.0a1, 6000.0.60f1, 6000.2.10f1, 6000.3.0b7, 6000.4.0a3
Reproducible on: Windows 10 (RTX 2070 Super), Windows 11 (Intel(R) UHD Graphics)
Not reproducible on: Windows 11 (RTX 3080 Ti Laptop)
Notes:
- Could not reproduce in DirectX 11
- Reproduces with DirectX 12 and Vulkan
First few lines of stack trace (6000.3.0b7, DirectX 12):
0x00007FFFACD066BF (Unity) D3D12SwapChain::CreateHWND
0x00007FFFACCA5FCD (Unity) D3D12Window::D3D12Window
0x00007FFFACCE94AE (Unity) GfxDeviceD3D12Base::CreateGfxWindow
0x00007FFFACBBA934 (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
- 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
Add comment