Search Issue Tracker
Active
Under Consideration for 6000.2.X
Votes
2
Found in
6000.1.14f1
6000.2.2f1
Issue ID
UUM-114301
Regression
No
Crash on D3D12GetInterface when creating a new project
How to reproduce:
1. Create a new project
Expected result: The project opens
Actual result: The project fails to open
Reproducible with: 6000.1.12f1, 6000.1.14f1
Reproducible on: Windows 10 (reporter)
Notes:
- Not reproduced by CQA
- Issue reproduced when creating a project different templates
- Reportedly the crash occurs when the loading screen reaches “Initializing Graphics” step
- The project disappears from Unity Hub after the crash
First few lines of stack trace:
{noformat}0x00007FFD2CE713A9 (D3D12Core) D3D12GetInterface
0x00007FFD2CE0036E (D3D12Core) D3D12GetInterface
0x00007FFD940D5406 (d3d12) GetBehaviorValue
0x00007FFD2CF372FB (D3D12Core) D3D12GetInterface
0x00007FFD2CE5B57C (D3D12Core) D3D12GetInterface{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment