Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.2.X
Votes
1
Found in
2017.2.0a3
2017.2.0f3
Issue ID
964073
Regression
Yes
[Regression] Standalone built game crashes when Direct3D12 is the first Graphics API while PC supports only Direct3D11
How to reproduce:
1. Download attached project file and open "Test" Scene
2. Build game on Standalone
3. Launch game on Windows 7/10 with PC which does not support DirectX12
Expected: Standalone player should automatically detect that DX12 isn't available and switch to DX11 without issue
Actual Result: Standalone Player will Select DX12 (as reported in logs) but then still crash after showing white screen due to similar access violation issue.
Reproduced with: 2017.2.0p1, 2017.3.0b8, 2018.1.0a3
Not reproduced with: 5.6.4p2, 2017.1.2p2
Regression since: 2017.2.0a3
Tested on win7
Note: Only launches successfully if forcing D3D11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Add comment