Death Stranding Director's Cut patcher not working under wine

[jibsaramnim]

Hello! First off, thank you so much for everything that you've done to make these games more accessible for those of us who have ultrawide displays. I truly appreciate it! Onto my question;

---

With the original version of Death Stranding I was able to use your patcher even though I play the game under Linux. I would launch the game through Steam, then separately launch the patcher within the same wine prefix, and it would work as expected.

However, with the Director's Cut edition I'm somehow not able to get it to work. Do you happen to know if something changed in the way you have implemented the hook/listener for the function keys?

It would be really nice if there was a way to get it to work again. I purchased the Director's Cut version mostly to support the developer and I was hopeful it would just come with 32:9 support out of the box, but that ended up not being the case, and unfortunately I have thus far not been able to get your patcher to work again too, so I've not been able to play again.

Anyway, I know you officially support only Windows, but for those of us who do not use this and do have an ultrawide, it would be really nice if whatever changed between the original and DC versions could be adjusted so that us Linux folk could play the game in all its ultrawide goodness again. Either way, thanks so much!

[RoseTheFlower]

Hi. Could you confirm that the original trainer still works as of today and the version of Wine or Proton that you're using?

Is this suggestion of any use?

[jibsaramnim]

Sorry for the slightly delayed response, I had to reinstall the non-DC version. I just tried again and, somehow, I can't get the patcher to work for the non-DC version either.

I am indeed launching the patcher in the same way as the link you have provided, and checking with taskmgr both the patcher and game are seen in the processes list, so I'm not sure what might be going on. I used to play this way, though admittedly it has been a while (>6 months at least).

Edit: forgot to add: I'm currently using GloriousEggroll's proton flavor, version 7-31.

Edit 2: I tried a few different versions of Proton, and am not able to get the Aspect Ratio correction patch to actually work. I did however notice that F3 and F4 do make their respective texts highlight in green in the patcher -- even though I do not see the FOV change, which is probably expected as F7 does not seem to respond (just like F5 and F6, of course).

[RoseTheFlower]

The F3 and F4 functions aren't conditional, so they will get highlighted even if you run the trainer by itself.

I sent a message to the person who made the linked comment to inquire if they've run any of my more recent trainers.

[jibsaramnim]

Thank you kindly! I'm not sure what may have changed -- it did work in the past for me (for the non-DC version), even though that too seems to not work anymore now. Thank you so much for looking into it, I really appreciate it!

[RoseTheFlower]

Could you try following this guide? If not on the Deck, perhaps there is something similar for the other distros.

[rialpa84]

I just thought I'd let you know that this does work on Linux, under Wine, as long as it and the game are ran from the same prefix. I used the "Run EXE inside of Wine prefix" feature included in Lutris. The guide you posed should work, too, in a more automated manner.

[RoseTheFlower]

Thanks for the report! The job of digging into so many games and maintaining over 100 mods is quite tough. If I were to also test them on Mac and Linux, or on each specific Linux distro, it would literally multiply the amount of work I have to do and distract from getting on new titles. I'm glad there are users that share their knowledge to make up this.

[rialpa84]

And thank you for the tool. This is one of those little annoyances that tends trip up people the first time they come across it and why things like Lutris and SteamTinkerLauncher make lives easier. The alternative is launching the tool with something like this:
WINEPREFIX="/external_disk/wine/egs" "/home/$USERNAME/.local/share/Steam/compatibilitytools.d/GE-Proton8-9/files/bin/wine" "/external_disk/games/pc/windows/Epic Games/DeathStrandingDC/Death Stranding Director's Cut - Display Mods v1.0 - Epic.exe"

That command specifically sets the WINEPREFIX variable to use my generic Epic Games prefix and uses the same Wine binaries (GE-Proton8-9 in this instance) that the game will be using.

If you just use wine /path/to/Death Stranding Director's Cut - Display Mods v1.0 - Epic.exe you'll use the system installed Wine and default, or currently set, prefix (usually $HOME/.wine) which probably isn't the one with DXVK, vkd3d-proton, and all the other goodies that make games run well on Linux.

[Calinou]

I've tried to run the Jedi Fallen Order ultrawide EXE in the same Proton Experimental prefix as the game itself (running via Heroic), but since the "Run EXE inside prefix" option does nothing for me¹, I tried to resort to the command line:

STEAM_COMPAT_DATA_PATH="/home/hugo/.local/share/heroic/prefixes/Jedi Fallen Order" STEAM_COMPAT_CLIENT_INSTALL_PATH="/home/hugo/.local/share/Steam" "/home/hugo/.local/share/Steam/steamapps/common/Proton - Experimental/proton" run Fallen\ Order\ Ultrawide\ 2.1.exe

Unfortunately, the trainer still can't "see" the running game when I do this (I launched the game first).

Footnotes

1. Literally nothing happens, even though I'm using the AppImage and not the Flatpak which has known issues with this. ↩