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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment