Help enable custom mesa in Heroic flatpak/steamdeck and none-flatpak

So first of all, a big Hi to the community from me.
I would like to run Alan Wake 2 in Heroic Game Launcher. I know it needs a development version of mesa to be installed to remove some graphical bugs. I compiled the development version (24.0.0) and it runs great. Tested in Jedi Survivor. But how do I get that driver to run on heroic?
I should also say that this driver version is not installed system wide because I don't want to remove my current stable drivers. Only to be used in some games.
In steam this can be done by adding "sh ~/mesa-run.sh %command% Mesa-run.sh is the executable pointing to all that is needed to run the driver without installing system wide.
Lutris can be done by adding an environment variable like this "VK_ICD_FILENAMES=/home/user/mesa/share/vulkan/icd.d/radeon_icd.x86_64.json"
Only only thing missing now is figuring it out for Heroic. Someone mentioned by adding the driver as a wrapper, but I have no idea what that even means. Do I add the sh file to the wrapper section? I did that but no luck.

Any help would be great, and probably help more in the future.

dry-scarlet•12/30/23, 4:12 AM

latest mesa should work now fwiw, 23.3, which im pretty sure is on flathub

dry-scarlet•12/30/23, 4:13 AM

but if you already set up a mesa repo and built it to use mesa-run script.. you just need to add mesa-run.sh to the "wrappers" section without any arguments

dry-scarlet•12/30/23, 4:15 AM

dry-scarlet•12/30/23, 4:16 AM

this assumes mesa-run.sh is in your path.. if not you probably either want to put it in the path, or do a full path

brilliant-limeOP•12/30/23, 4:48 AM

Hey. Thanks for the replay. Unfortunately the drivers in manjaro are still 23.1.9. The unstable branch has the 23.3 version. That's why i built the driver from source. The mesa-run.sh file is in my home directory. Is that the path you mean? or is it some path I need to add in Heroic somewhere?

dry-scarlet•12/30/23, 4:54 AM

no sorry, the flatpak version is 23.3

dry-scarlet•12/30/23, 4:54 AM

if you are using flatpak heroic.. you should be able to use that

dry-scarlet•12/30/23, 4:54 AM

$PATH is what im referring to

dry-scarlet•12/30/23, 4:54 AM

the directories that get looked into for executables

dry-scarlet•12/30/23, 4:56 AM

if its not in $PATH then use the full path to the mesa-run script

brilliant-limeOP•12/30/23, 4:56 AM

when i do "flatpak list" i see mesa 23.3. How can i see in game if it is used. I have mangohuf flatpak but no idea how to configure it. Any config i make just doesnt pick it up. Probably not placing it in the right place.

brilliant-limeOP•12/30/23, 4:57 AM

I see. it's this $PATH i'm not sure about. how can i check?

dry-scarlet•12/30/23, 4:58 AM

echo $PATH though typically your home directory is not part of path, for good reason heh

dry-scarlet•12/30/23, 4:58 AM

but the script can be put into one of your path directories.. i usually make a /home/username/bin folder

dry-scarlet•12/30/23, 4:59 AM

fwiw this is almost identical to windows' PATH as well.. so if you've ever used it in windows same exact concept

brilliant-limeOP•12/30/23, 5:00 AM

havent used windows in years. lol just never had to bother with custom drivers before.

brilliant-limeOP•12/30/23, 5:01 AM

running echo $PATH gives me.

brilliant-limeOP•12/30/23, 5:01 AM

/home/user/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

brilliant-limeOP•12/30/23, 5:02 AM

can i put he sh file in say .local/bin then?

dry-scarlet•12/30/23, 5:04 AM

yep!

dry-scarlet•12/30/23, 5:05 AM

dont forget to chmod +x

brilliant-limeOP•12/30/23, 5:08 AM

that makes things easier, thanks. But say I want to use another directory that isn't part of path. how do i do a full path, like you mentioned. for educational purposes now.

dry-scarlet•12/30/23, 5:09 AM

/path/to/executable

brilliant-limeOP•12/30/23, 5:12 AM

what i initially did before coming here. in the wrapper section, for name I gave it mesa-dev-24 and path to the sh directory in my users folder. So mesa-dev-24 and the path /home/user/mesa-run.sh. That didnt work. Was it because the name was wrong and it actually had to be just mesa-run.sh as a name?

dry-scarlet•12/30/23, 5:12 AM

the left half of the option is the executable, the right side is the arguments you want to pass to the exectuable

dry-scarlet•12/30/23, 5:13 AM

there is no name here

brilliant-limeOP•12/30/23, 5:14 AM

sorry your right. its 5 in the moring for me haha

brilliant-limeOP•12/30/23, 5:15 AM

"new wapper" section would look like this then? "/home/user/mesa-run.sh"

dry-scarlet•12/30/23, 5:15 AM

yep

brilliant-limeOP•12/30/23, 5:18 AM

oh right! thanks a lot. i'll try that in the morning. Thats what i was mostly confused about. Didn't realise that the path had to be in the new wrapper section. I just thought it was supposed to be a name for the user to identify with.

dry-scarlet•12/30/23, 5:25 AM

ah yeah i can see how that can happen

Help enable custom mesa in Heroic flatpak/steamdeck and none-flatpak

Similar Threads

Similar Threads

Similar Threads