Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.3.X, 2022.1.X
Votes
2
Found in
2021.2
2021.2.0f1
2022.1
Issue ID
1381731
Regression
Yes
Painting Terrain details result in a crash when using DirectX12
Reproduction steps:
1. Open the attached project
2. Open "Assets/Scenes/SampleScene" scene
3. Select GameObject "Terrain" from the Hierarchy
4. Select "Paint Details" from the Terrain Component in the Inspector
5. Select "Cube" from the Details list
6. Try painting on the Terrain GameObject
Expected result: Terrain details are painted on the terrain
Actual result: Editor crashes
Reproducible with: 2021.2.4f1, 2022.1.0a16
Not reproducible with: 2019.4.33f1, 2020.3.23f1, 2021.1.28f1
Stacktrace:
0x00007FF669606F8C (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FF66960634E (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FF6696065D0 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FF66AB882BB (Unity) GfxDeviceWorker::RunCommand
0x00007FF66AB8A9DD (Unity) GfxDeviceWorker::RunExt
0x00007FF66AB8AAF8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF6692C2AC7 (Unity) Thread::RunThreadWrapper
0x00007FFC4A957034 (KERNEL32) BaseThreadInitThunk
0x00007FFC4BA82651 (ntdll) RtlUserThreadStart
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
- Crash on RaiseException when terrain detail instancing is excessive
- Prefab variant reference is lost when assigned by click-and-drag in Prefab Editor mode
- Opening any dropdown in Shader Graph stops the Nodes preview but it still plays in the background
- GPU utilization increases when a GameObject is selected
- Motion Blur has sharp edges when object is moving in the foreground of another object
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a12
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in: 2021.3.2f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.34f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.40f1