Batman: Arkham City GOTY can't find 32-bit driver, falls back to llvmpipe

[b2jammer]

DXVK is unable to find a 32-bit NVIDIA driver and falls back to using llvmpipe:

Running VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.i686.json vulkaninfo --summary prints the following, which seems to imply there's no 32-bit driver available?

ERROR: [Loader Message] Code 0 : vkCreateInstance: Found no drivers!
Cannot create Vulkan instance.
This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan.
ERROR at /builddir/build/BUILD/vulkan-tools-1.4.341.0-build/Vulkan-Tools-vulkan-sdk-1.4.341.0/vulkaninfo/./vulkaninfo.h:611:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVER

Software information

Batman: Arkham City GOTY
Steam Release

System information

• GPU: NVIDIA RTX 4070 Ti
• Driver: NVIDIA Proprietary 595.80
• Wine version: Proton 8.0-5 (Also occurs on 9.0-4 and 10.0-4)
• DXVK version: v2.3-21-g1b31aa5dbca0749
• OS: Fedora Kinoite 44
• Layered Packages:

akmod-nvidia-open akmod-v4l2loopback cockpit cockpit-machines containerd.io distrobox fastfetch ffmpeg fluid-soundfont-gs git libva-nvidia-driver libva-utils libvirt-daemon libvirt-daemon-qemu podman-compose rpmfusion-free-release rpmfusion-nonfree-release steam steam-devices syncthing tailscale tmux vdpauinfo virt-manager xorg-x11-drv-nvidia-cuda

Apitrace file(s)

• BatmanAC.trace.tar.gz

Log files

steam-200260.log

[doitsujin]

vulkaninfo is a 64-bit app so it won't work with 32-bit drivers, but yes, Lavapipe is the only 32-bit driver reported to us in the log so we can obviously only use that.

[b2jammer]

Turns out it was a packaging issue after all. I also had to layer vulkan-loader.i686 to get the driver to appear:

[b2jammer]

Might have spoken too soon. The driver only seems to load if /usr is unlocked by running either rpm-ostree apply-live --reset or rpm-ostree usroverlay. Seems to be a weird quirk in either ostree or the RPMFusion packages.

I'll open a report at the RPMFusion Bugzilla as well.

[K0bin]

Either way, this clearly isn't a DXVK bug.