Search Issue Tracker
Fixed
Fixed in 2022.3.34f1, 6000.0.3f1
Votes
0
Found in
2022.3.26f1
2023.2.19f1
6000.0.0b16
Issue ID
UUM-70289
Regression
No
Crash on D3D12GetInterface when enabling a GameObject using a Sample Skinned Mesh node
How to reproduce:
1. Open the “IN-73903_repro“ project
2. Open the “Main“ scene
3. Enable the “Particlepeople01“ GameObject
Expected result: The GameObject is enabled and the Editor is running
Actual result: The Editor crashes
Reproducible with: 2022.3.26f1, 2023.2.19f1, 6000.0.0b16
Could not test with: 2021.3.37f1 (errors)
Reproducible on: Windows 10, Windows 11 (user’s device)
Not reproducible on: No other environment tested
First few lines of Stack Trace:
0x00007FF88E159CF9 (D3D12Core) D3D12GetInterface
0x00007FF7227A4D87 (Unity) FillTableUNIAndBarrier
0x00007FF7227A191A (Unity) CmdListFillTableUNI
0x00007FF7227AC0AD (Unity) D3D12ComputeState::Transition
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
- Multiple exceptions are thrown after exiting Play mode when Layout Group component is displayed in Debug Inspector and Padding section is expanded
- ScrollView elements are not restored to their original positions after removing a Layout Group with Undo action
- "Assembly with name already exists" errors are thrown when two packages with different technical names resolve to the same namespace
- A Select Scene Entry is added to Undo History when Deleting while a Scene is selected in the Hierarchy
- The Add Component Menu's back arrow accumulates phantom levels when the Menu is repeatedly opened into a Category and closed without selecting
Resolution Note:
Resolved a crash issue arising from the use of a Skinned Mesh Renderer with the DX12 rendering API.
Resolution Note (fix version 6000.0.3f1):
Resolved a crash issue arising from the use of a Skinned Mesh Renderer with the DX12 rendering API.