HGL
adverse-sapphire
32-bit applications using llvmpipe instead of GPU when using DXVK
Tried two 32bit applications through HGL and they both revert to using llvmpipe for graphics instead of detecting the GPU (nvidia in my case). The games I tried were Mount and Blade - Warband and Max Payne. Warband had been working about a week previously. OS is Bunsenlabs Boron, essentially Debian Bookworm (12).
HGL detects the GPU fine and it still works perfectly on newer games. I set up an external, non flatpak version of Wine (10.2) with WineGUI and dropped DXVK into it and those 32bit games work correctly again. It seems to be something to do with the HGL flatpak.
Leaving this here in case someone wants to look into it.
Edited Log:
Launching "Warband" (sideload)
Native? No
Installed in: /home/xxx/Games/Heroic/Prefixes/default/Warband/drive_c/GOG Games/Mount and Blade - Warband
System Info:
CPU: 16x Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
Memory: 33.55 GB (used: 3.94 GB)
GPUs:
GPU 0:
Name: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti]
IDs: D=2486 V=10de SD=87c6 SV=1043
Driver: nvidia
OS: BunsenLabs GNU/Linux 12 (Boron) (linux)
The current system is not a Steam Deck
We are running inside a Flatpak container
...standard log stuff until...
info: Game: mb_warband.exe
info: DXVK: v2.5.3
info: Build: x86 gcc 14.2.0
info: Vulkan: Found vkGetInstanceProcAddr in winevulkan.dll @ 0x6fa838c0
info: Built-in extension providers:
info: Platform WSI
info: OpenVR
info: OpenXR
info: OpenVR: could not open registry key, status 2
info: OpenVR: Failed to locate module
info: Enabled instance extensions:
info: VK_EXT_surface_maintenance1
info: VK_KHR_get_surface_capabilities2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info: llvmpipe (LLVM 17.0.6, 256 bits):
info: Driver : llvmpipe 0.0.1
11 Replies
ratty-blush•3mo ago
perhaps the flatpak driver package and graphics driver are out of sync? (this happens to me sometimes) - try running
flatpak update to see if there are any nvidia driver package updates
though - considering heroic is picking up the gpu correctly it might not be, but its worth a check anywayadverse-sapphireOP•3mo ago
Thanks, already tried that but it didn't help. Driver versions match and running update anyway just says 'nothing to do' . I've also tried used different dxvk versions by turning off the auto update option and using winetricks in case there was a dxvk update that broke it, but no. I've no idea what could have happened. As I said, it was working perfectly a week ago and I didn't change anything that I recall, but I did mess about with the system. But now even a clean install gives me same issue.
I wondered if it was something to do with this:
info: DXVK: v2.5.3
info: Build: x86 gcc 14.2.0
Is that 32-bit dxvk? I manually installed vulkan 32bit icd as well in case that could be something to do with it, but still same issue. shrug
Just tried using old versions of Wine and old versions of dxvk, still the same issue. Bizarre
ratty-blush•3mo ago
considering the game does seem to be using dxvk as the dx9 translation layer, it likely means theres some sort of disconnect between flatpak and your gpu, but I'm not entirely sure what the issue could be as I haven't used debian in a while - apologies!
adverse-sapphireOP•3mo ago
ah no worries. Thanks for your help anyway. It's just so weird that it seemed to just happen. What distro are you using currently? Maybe I'll try with it just to troubleshoot
Decided to try it with another old 32bit game - max payne. Same issue, only llvmpipe is available as a graphic adapter. I'm beginning to suspect this is a debian regression as there was some system updates and I apt upgraded when I installed it. Going to try a different method of installing nvidia drivers
conscious-sapphire•3mo ago
how do you own this game
just curious
because if it is pirated then uh
We cannot help you with pirated/cracked/etc. games, as it is against the Discord ToS and our server rules & personal morals
adverse-sapphireOP•3mo ago
Why would it be pirated? Bought it from GOG many years ago
But anyway, I've installed Wine system-wide, created a prefix and dropped dxvk into it and it works perfectly, so I can only think it must be an issue with Heroic somewhere. If anyone wants me to help troubleshoot, let me know
conscious-sapphire•3mo ago
side load is usually a solid indicator but I do believe you LOL
adverse-sapphireOP•3mo ago
ahhh. lol right. Many years ago a CD I had for interstate 76 stopped working and ever since then I've got into the habit of making isos of all my games to keep. Then I got into the habit of keeping an archive of all my games so now I download all my gog installers as soon as I get them. I've about 2tb of games I've kept, some of which aren't available any more, but I just like having that drive with all my games. Just habit i guess.
Argh! Clean install so no ad-blockers. Been ages since I've seen an ad on youtube. Man, they're unbearable
fascinating-indigo•3mo ago
i dont know your OS, but you may need to enable/install 32bit support and install 32bit versions of your drivers
adverse-sapphireOP•3mo ago
Thanks. I'm using Debian. I've already checked for 32bit drivers. They're installed on my system and the flatpak downloads matching 32bit drivers too. Just for some reason it won't see my GPU. I mentioned above that installing Wine and DXVK deb packages work fine. Is there anything I can provide to help work out if it's a bug or a problem with my system? Or should I report on github?#
Maybe this is of interest to anyone who wants to look into this issue. I've got two versions of the nvidia driver runtimes/driver extensions installed (tried reverting to old ones to see if that was problem). When I run 'flatpak uninstall --unused' to remove the unused ones it removes the x64 runtime version but not the 32bit one. So could this be a problem with the x86 runtimes not being registered properly with the flatpak verison of HGL? I'm not very technical so could be taking rubbish, but it seems like a coincidence.
Figured it out I think. I needed to manually create a 32-bit prefix and install the game into it. Anyone any idea why this would need to be done now when it didn't previously? No doubt I've misunderstood something important, but this game used to work fine before by just installing it the same as any other game (I'd never even realised it was a 32-bit game)
Nope. After a restart it's back to using llvmpipe even though it's still showing as a 32bit wine prefix