Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.2.1f1
Issue ID
UUM-115028
Regression
No
Crash on D3D12GetInterface when creating a project from template on specific Windows ARM devices
How to reproduce:
1. Create and open a project using the 3D Game Kit template (https://assetstore.unity.com/packages/templates/tutorials/unity-learn-3d-game-kit-115747 )
2. Observe the crash
Reproducible in: 6000.1.15f1, 6000.2.1f1 (inconclusive)
Reproducible on: Microsoft Surface Pro 11 (Snapdragon X) - User’s device
Not reproducible on: Microsoft Surface Pro 9 (Microsoft SQ3), Dell XPS 13 (Snapdragon X Elite)
First few lines of stacktrace:
{noformat}0x00007FF833D9D0DC (qcdx12arm64xum) OpenAdapter12
0x00007FF840B871C4 (D3D12Core) D3D12GetInterface
...
(ScriptedImporter)0x00007FF81746BFB8 (Unity) D3D12CopyCommandList::GetFreshCommandList
0x00007FF817460900 (Unity) D3D12UploadOperation::CopyTextureRegion
(ScriptedImporter)0x00007FF8174B2C90 (Unity) TexturesD3D12::UploadTextureDataInternal{noformat}
Note:
- Same behavior was also reported when creating project with Universal 3D template
- Not reproduced by CQA due to lack of hardware
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Resolution Note:
We have tried to keep an eye on this crash for a while. Unfortunately, this is a hardware configuration/driver problem because crash callstacks point to vendor-specific driver functions, like OpenAdapter12() in libraries, such as amdxc64.dll (AMD), nvwgf2umx.dll (NVIDIA), qcdx12arm64xum.dll (Qualcomm), etc. Since, as a result, our code in the engine can not even start any crash-analysis on DirectX 12, we can not debug or fix such problems on our side. The only recommendation we can give is to update the drivers and/or to perform full uninstallation (i.e., using "Display Driver Uninstaller" tool) followed by a clean installation of the driver.