Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
Issue ID
1014404
Regression
No
[UWP] User can set Graphic APIs to DX12 only.
For UWP settings, the user can choose DX12 as the only Graphic API.
However, the DX12 is experimental and should always paired with DX11 in the setting.
Besides, on the Windows standalone side, if user chooses DX12 as the only option, the Editor generates a warning and automatically add DX11. The behavior should be consistent for both standalone and UWP.
Repro Step:
1. Go to Player Settings -> Other Settings -> Graphics API, make sure it is for UWP
2. Uncheck the "Auto Graphics API"
3. Add "Direct3D12 (Experimental)" and delete "Direct3D11"
4. Observe the Editor does not complain or correct it.
(Optional) 5. Repeat step 2-4 for the Standalone Graphics APIs for Windows and observe the warning message in Editor Console
Expected: The experimental DX12 should not be the only Graphics API chosen.
Comments (2)
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
- Rigged GameObject doesn’t return to its idle state when disabling "Preview" and the GameObject has nested rigged GameObjects
- Error "ArgumentException: Trying to use an invalid resource" when creating custom post-processing effect in URP
- [DX12] GameObjects using CommandBuffer DrawProcedural and DispatchCompute calls have color flicker when changing color and moving mouse cursor
- The Player becomes unresponsive after resolution switch in Exclusive Fullscreen mode when using DX12 Graphics API
- (Apple Silicon) Floating point inconsistencies between mono and il2cpp
shubhamswaraj2021
Aug 19, 2020 13:32
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
maxgray1
Oct 01, 2019 12:13
Hi! This article could not be composed much better.
https://hillclimbcoins.club
https://bstarscash.club
https://kimstarscash.club
https://homescapescoins.club
https://thetappedoutdonuts.club