Vulkan failing to initialize
Posted: 23 Aug 2023, 03:15
I have Warzone2100 installed from the snap store (https://snapcraft.io/warzone2100) and compiled from master on Github. When I try to launch either, I get an error window with the following message:
with the following text in the console:
(I renamed warzone2100.gdmp-GIHzf5 to warzone2100.gdmp-GIHzf5.txt to make the forum software happy.)
As they're a little long to include here in the text, I've attached the output for both the snap and built versions when run with the --debug=all argument as wz2100_snap_debug.txt and wz2100_build_debug.txt respectively.
To verify that Vulkan sometimes works, I've run vkcube and also started working through the official tutorial. When looking in Warzone2100's source for where it calls createSwapchainKHR(), I found a comment at the top of the respective file (lib/ivis_opengl/gfx_api_vk.cpp) with the flagg to enable validation layers (--gfxdebug). Accordingly, I ran both versions with that flag and saved them as wz2100_snap_gfxdebug.txt and wz2100_build_gfxdebug.txt respectively.
Both gfxdebug outputs pinpoint the error on the compositeAlpha field of the createInfo struct passed to vkCreateSwapchainKHR(). If I'm reading the messages correctly, Warzone2100 tried to create the swap chain with VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR, while the physical device only supports VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR. On its own, that seems almost reasonable. But in the Vulkan tutorial page on setting up the swap chain, they specify and that code (both the version I typed and the copy they link at the bottom of the page) compiles and runs with validation layers enabled without any complaints.
In conclusion, I am thoroughly out of my depth and very confused. I thought I narrowed in on the root problem, but I have other code showing that evidently that is not the case. I am still learning the ins and outs of Vulkan and I haven't read through the Warzone2100 code properly yet. At this point, I am assuming it is more likely that something is wrong with my setup (it certainly won't be the first time) than a bug in Warzone2100 that needs fixing - hence writing this here rather than making an issue on Github. If it would be more helpful, I can rewrite it over there instead/in addition to here.
I'm running Fedora 36 on a desktop with a GTX 1080, running NVidia drivers version 530.41. Warzone2100 does run fine on Windows on the same hardware.
Code: Select all
Failed to draw graphics for backend: Vulkan.
Error Details:
"Failed with error: ErrorInitializationFailed"
Do you want to reset the graphics backend to: OpenGL?Code: Select all
$ warzone2100
info |20:26:48: [rebuildSearchPath:825] Failed to load expected terrain quality overrides: terrain_overrides/high
last message repeated 2 times
info |20:26:48: [wzChangeFullscreenDisplayMode:2061] Changing fullscreen mode to [0] 1920x1200
error |20:26:48: [createSwapchain:4010] vk::Device::createSwapchainKHR: InitializationFailedError: vk::Device::createSwapchainKHR: ErrorInitializationFailed
/usr/bin/gdb: warning: Couldn't determine a path for the index cache directory.
No frame at level 0x7f95d3634d50.
Saved dump file to '/home/penn/.local/share/warzone2100-master//logs/warzone2100.gdmp-GIHzf5'
If you create a bugreport regarding this crash, please include this file.
Aborted (core dumped)As they're a little long to include here in the text, I've attached the output for both the snap and built versions when run with the --debug=all argument as wz2100_snap_debug.txt and wz2100_build_debug.txt respectively.
To verify that Vulkan sometimes works, I've run vkcube and also started working through the official tutorial. When looking in Warzone2100's source for where it calls createSwapchainKHR(), I found a comment at the top of the respective file (lib/ivis_opengl/gfx_api_vk.cpp) with the flagg to enable validation layers (--gfxdebug). Accordingly, I ran both versions with that flag and saved them as wz2100_snap_gfxdebug.txt and wz2100_build_gfxdebug.txt respectively.
Both gfxdebug outputs pinpoint the error on the compositeAlpha field of the createInfo struct passed to vkCreateSwapchainKHR(). If I'm reading the messages correctly, Warzone2100 tried to create the swap chain with VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR, while the physical device only supports VK_COMPOSITE_ALPHA_INHERIT_BIT_KHR. On its own, that seems almost reasonable. But in the Vulkan tutorial page on setting up the swap chain, they specify
Code: Select all
createInfo.compositeAlpha = VK_COMPOSITE_ALPHA_OPAQUE_BIT_KHR;In conclusion, I am thoroughly out of my depth and very confused. I thought I narrowed in on the root problem, but I have other code showing that evidently that is not the case. I am still learning the ins and outs of Vulkan and I haven't read through the Warzone2100 code properly yet. At this point, I am assuming it is more likely that something is wrong with my setup (it certainly won't be the first time) than a bug in Warzone2100 that needs fixing - hence writing this here rather than making an issue on Github. If it would be more helpful, I can rewrite it over there instead/in addition to here.
I'm running Fedora 36 on a desktop with a GTX 1080, running NVidia drivers version 530.41. Warzone2100 does run fine on Windows on the same hardware.