Search Issue Tracker
Duplicate
Votes
0
Found in
6000.0.60f1
6000.2.10f1
6000.3.0b7
6000.4.0a3
Issue ID
UUM-128983
Regression
No
[Vulkan] 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
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Need testing before create separate ticket
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-125265