I uploaded it for you but the latest mesa 20.3.3 in slackware works OK for me. https://drive.google.com/file/d/1kbf...ew?usp=sharing

If anyone still has this problem (it returned for me), exporting VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json fixes it.

Or, just remove lvp_icd.x86_64.json and lvp_icd.i686.json from /usr/share/vulkan/icd.d. That's what I do with unwanted vulkan icd loader files... move them out of there. The vulkan loader may not choose the one you want, if other valid ones are in there. For example I've had it load AMDVLK when unwanted, and then later the behaviour of the vulkan loader changed. Make up your damned mind... I'm not second guessing that.

The problem with setting VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json is that it will be wrong for 32 bit games. OK, so set it to the 32 bit one for those games, right? Not so fast... some (windows) games have 32 bit launchers/clients that will fail when loading directx and 64 bit binaries with the wrong back end. I think it's possible to specify both with a colon between, but I've just come to rely on having both the 64 bit and lib32 vulkan icd loader and not have any unwanted .json files.

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json

2 members found this post helpful.

I joined this Forum just to say a massive thankyou to TheRealGrogan for this solution. I've been tearing my hair out and getting extremely angry trying to get Fallout4 working on my Optimus graphics laptop under WINE.

It was actually working extremely well, I managed to get F4SE (a sort of master mod loader), all my mods (98 of them), and sound working perfectly on Fedora34 with WINE v6.11 (staging) - but only at a lousy 5fps using the Intel "GPU".

WINE simply refused to use my Nvidia card and I couldn't figure out why. Steam for Linux was using Nvidia, but it simply refused to load my mods (it couldn't find the Windows "AppData" folder for some unknown reason) which made it useless for me.

With some amazing luck, I tumbled on this page and followed TheRealGrogan's advice and removed everything except nvidia_icd.json from /usr/share/vulkan/icd.d/ (...moved them to a backup folder) - and it worked .

So many many thanks for your input.

Regards, Me .

I'm glad to hear it helped you. I play Fallout 4 through SteamPlay, but I don't have your mods so I don't have a problem. Probably in the Wine registry files, %LOCALAPPDATA% is set to "drive_c\users\steamuser\local settings\application data". On a normal modern windows system, that would be a hard link (to AppData\Local), but Proton uses that old Windows XP path for AppData. Possibly that is what confused your mod loader that wasn't correctly using the environment variable in their paths. (you're never supposed to hard code paths to userdirs like that)

You may have been able to work around that by making a symlink in the Wine Prefix (in steamapps/compatdata/377160/pfx/drive_c/users/steamuser/AppData) named Local and pointing to ../local settings/application data but it's better that you have it working in your own native wine anyway.

3 members found this post helpful.

I am aware this is an older post. On Tinycore the Mesa package is Xorg-7.7-3d and @TheRealGrogan

works a treat.


was giving me an error for lavapipe