ffxiv-reshade-linux-xivlauncher.md

1. Install reshade

Source for the installation script

Download and use the script :

# when asked, install to directory with ffxiv_dx11.exe (Game Path/game in xivlauncher settings)
curl -LO https://github.com/kevinlekiller/reshade-steam-proton/raw/main/reshade-linux.sh && chmod +x reshade-linux.sh && RESHADE_ADDON_SUPPORT=1 ./reshade-linux.sh 

• XIVLauncher automatically detects reshade and will add the correct WINEDLLOVERRIDES to environment. No need to do anything.
• Keep the reshade-linux.sh file somewhere as can use it to uninstall reshade.
• You can remove or ignore the ReShade_shaders the script creates, we will be overriding those in the next step.

2. Install gposingway

Based on manual installation instructions for windows

1. Download latest gposingway.zip file : https://github.com/gposingway/gposingway/releases

2. Extract in game directory, replace the existing Reshade.ini (otherwise gposwingway effects won't load)
3. On first game start after installing the game might crash or freeze after compiling its shaders. I had to wait a good minute until it froze, I killed it and restarted the game and it was good.

3. Enjoy !

Flatpak caveats

Tested with the fedora version of xivlauncher, I need to test if it's the same with the flatpak (steam deck etc.) version. It should be as it allows everything in /home by default.

If it does not work, you can try adding ~/.local/share/reshade/ to the list of allowed paths for xivlauncher in flatseal or flatpak settings.

I'll have to take an exact look but my installation is also pretty odd, having copied a windows installation that already had reshade, which then didnt work, I uninstalled that one to try and get a proper install working on linux.
No clue how, but step one installs reshade allright, but it also causes all of the shaders to fail compiling (I am guessing that thats because I am launching it on linux?).
Step 2 begins compiling (while still saying some failed) and ultimately end up with saying that my system has run out of RAM during compiling and all of steam gets shut down by the linux kernel due to RAM shortage.
I doubt that its really intended to draw that much ram - When I looked it drew a whole lot of 20 gigs until it used up everything and then crashes.

I'll see what I can figure out today with a bit of more tinkering and seeing.

I followed this but I got a lot of shader compilation issues, even on shaders included in the base install. Says, for example, "fastopt" is not implemented. A quick google had me in a reshade forum thread that says the d3d compile 47 dll that was being used was different from the windows one, causing issues. I got the windows version of the dll and overwrote the one in /.xlcore/wineprefix/drive_c/windows/system32/ (you can easily go to it on the launcher settings if using xlcore) and also placed the _64 version that was in the game folder in there for good measure. This seemed to fix the problem.

I followed this but I got a lot of shader compilation issues, even on shaders included in the base install. Says, for example, "fastopt" is not implemented. A quick google had me in a reshade forum thread that says the d3d compile 47 dll that was being used was different from the windows one, causing issues. I got the windows version of the dll and overwrote the one in /.xlcore/wineprefix/drive_c/windows/system32/ (you can easily go to it on the launcher settings if using xlcore) and also placed the _64 version that was in the game folder in there for good measure. This seemed to fix the problem.

Thank you, it actually finally worked for me! My XIVLauncher kept crashing whenever I tried to load gposingway shaders and now it's loaded with no issues

Thanks you all for researching updating this. I swear I'll update this mini guide it whenever I can, my life has been a mess these past months... Sorry I couldn't help more :(

…

On October 11, 2025 9:35:46 PM GMT+02:00, "Kinga Kiełboń" ***@***.***> wrote: @Renikkiner commented on this gist: > I followed this but I got a lot of shader compilation issues, even on shaders included in the base install. Says, for example, "fastopt" is not implemented. A quick google had me in a reshade forum [thread](https://reshade.me/forum/troubleshooting/10027-several-older-games-refuse-to-work-with-update-6-5-1) that says the d3d compile 47 dll that was being used was different from the windows one, causing issues. I got the windows version of the dll and overwrote the one in /.xlcore/wineprefix/drive_c/windows/system32/ (you can easily go to it on the launcher settings if using xlcore) and also placed the _64 version that was in the game folder in there for good measure. This seemed to fix the problem. Thank you, it actually finally worked for me! My XIVLauncher kept crashing whenever I tried to load gposingway shaders and now it's loaded with no issues -- Reply to this email directly or view it on GitHub: https://gist.github.com/xorus/3b9f2d88743d80bae9bc743a72933d10#gistcomment-5798940 Unsubscribe from this thread: https://github.com/notifications/unsubscribe-auth/AAS32YRHELEOV27OQNW7SXT3XFLZHBFHORZGSZ3HMVZKMY3SMVQXIZNMON2WE2TFMN2F65DZOBS2WR3JON2EG33NNVSW45FGORXXA2LDOOIYFJDUPFYGLJDHNFZXJJLWMFWHKZNJGEZTOMRXG4ZDMMVKMF2HI4TJMJ2XIZLTSOBKK5TBNR2WLKBXGI2TCNBYGYZ2I3TBNVS2QYLDORXXEX3JMSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DF You are receiving this because you authored the thread Message ID: ***@***.***>