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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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.