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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Add comment