You are not logged in.
I have Doom 2016 installed through Steam. It suddenly stopped working, crashing when I attempted to start the game. I noticed the vulkan packages were just updated with a version bump, and I know I have Doom setup to use vulkan. As I expected, downgrading vulkan (I did both the "vulkan-radeon" and "lib32-vulkan-radeon" packages) from 19.2.0-2 to 19.1.7-1 allowed the game to run properly again.
I guess my question is, where does the fix / bug report go? Does an Arch Linux package need to be updated / recompiled? Or Steam? Or Doom? Or Proton (used to run Windows games on Linux)?
I'm not even sure which forums to search on for this issue...
Last edited by drcouzelis (2019-10-08 14:33:09)
Offline
Those packages are part of the mesa/lib32-mesa pkgbase.
Did you also downgrade (if present on your system)
mesa, libva-mesa-driver, mesa-vdpau, opencl-mesa, vulkan-intel, vulkan-mesa-layer
and lib32-mesa, lib32-libva-mesa-driver, lib32-mesa-vdpau, lib32-vulkan-intel ?
No idea where the fix should come from, but i'd start searching for issues between steam and mesa 19.2 .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Hi
I've reported this bug here: https://gitlab.freedesktop.org/mesa/mesa/issues/1902
A fix is already developed, and it's easy to apply by adding the application override to /usr/share/drirc.d/00-mesa-defaults.conf (.drirc could also work, but I didn't try).
Add to <device> section
<application name="DOOM" executable="DOOMx64vk.exe">
<option name="vk_x11_strict_image_count" value="true" />
</application>
Offline
Thank you!!!
I'll mark this as "solved" for now, even though I can't test it out until tonight.
Offline