Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0b11
Issue ID
892610
Regression
No
AMD GPU installations are missing vulkan-1.dll
===
In many cases the end users seem to be missing vulkan-1.dll from their systems, causing the vulkan renderer to fail (and crash if no other renderers are available). Try to figure out some kind of a remedy for this.
====
To reproduce:
1. Go to Player Settings / Other Settings
2. Disable "Auto Graphics API for Windows"
3. Set API to Vulkan
4. Build & run to Windows Standalone with "-force-vulkan" flag
Expected: the same game view as in editor
Actual: opened window becomes pink: https://gyazo.com/27bf8edda6495fd5cd26f45cc5859f4d
Workaround:
1. Add Direct3D9 to the list of API
2. Build & run to Windows Standalone with "-force-vulkan" flag
3. Everything works as expected
Reproduced on: 5.6.0b11, f2
Not reproducible on 5.5 because 'Platform WindowsStandaloneSupport does not support graphics device type Vulkan'
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
vulkan-1.dll is from the Vulkan driver. User can try to update their Vulkan Driver to see if this solves their problem.