Search Issue Tracker
Duplicate
Votes
1
Found in
2019.3.0b10
Issue ID
1197012
Regression
Yes
Switching to Vulkan crashes editor
RPs tested: URP, HDRP, Standard (Occurs in all three)
Version tested: 2020.1.0a12, 2019.3.0b10, 2019.2.8f1
Does not occur on 2019.2.8f1!
My theory: it's gpu related, as I have AMD Radeon VII and it does not happen on any Nvidia GTX machines.
PC:
Windows 10
Intel Xeon W-2145
AMD Radeon VII
Steps to reproduce:
1) Open any project
2) Switch to Vulkan in Player settings
3) Observe that it tries to reload the editor but crashes
4) Try opening the project again. No luck
Bonus issue:
If you build the project with Vulkan and force it via command line it will crash
1) Add Vulkan to graphics API but don't switch to it
2) Build the project
3) Run it with -force-vulkan flat
4) Observe the crash
(attaching player.log)
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
This is a duplicate of issue #1197292