Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.1.0b5
Issue ID
912955
Regression
No
DX12 doesn't fall back to DX11 on hardware that does not support DX12
To reproduce:
1. Open a new project in a computer with a GPU that doesn't support DX12
2. Set the Graphics API to Direct3D12 (Experimental)
3. Set the Graphics API to Driect3D9
4. Repeat step 2
5. Observe the title bar of the Editor window
Expected: setting Graphics API to DX12 on hardware that doesn't support DX12 should fallback to DX11 (if the hardware supports it)
Actual: Graphics API doesn't change if it was changed from DX9 to DX12
Reproduced in 5.4.5p2, 5.5.3p2, 5.6.1p1, 2017.1.0b6, 2017.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment