Unknown
PROTON_USE_WINED3D=1 %command%
using wine3d is a necessary step! the game does not launch otherwise - it may also be necessary to do combat too, as i tried other versions of proton, all of which crashed upon entering combat.
Low sanity, a region in the upper right, the endings all need some extra dependencies for shaders.
Similar to https://www.protondb.com/app/437250#3TTY3P4Buw I used
WINEPREFIX=~/.steam/steam/steamapps/compatdata/437250/pfx winetricks d3dcompiler_43
Occasional Crashes during combat, usually a restart would fix it.
I played with Altotas's patch 1.4, I would consider the game unplayable without it. Unfortunately even after installing this patch there are some shader issues, but installing the d3dcompiler_43 dependency seemed to fix them.
For more information, please see: https://steamcommunity.com/sharedfiles/filedetails/?id=3003963756&tscn=1692901776 and https://steamcommunity.com/sharedfiles/filedetails/?id=2708670345
And a huge thanks to Altotas for making this game playable!
Works fine with Proton Experimental, even combat. Controls are a bit awkward.
Also tried ge-proton
Many users report bugs on Windows native, but I didn't encounter any in my initial 30 minutes. Did exploration, visiting cities, and combat. No issues encountered, runs perfectly out of the box so far.
Crashes during combat. Most combats can be avoided during the game, except the final boss, so I rate it borked.
Runs about as well as on Windows judging by the other people's bug reports, certain crashes occur on shader compilation errors, they're fixable by installing native d3dcompiler_43 and setting the override with winetricks (e.g. by running WINEPREFIX=$HOME/.steam/steam/SteamApps/compatdata/437250/pfx/ WINE="$HOME/.steam/steam/SteamApps/common/Proton 4.2/dist/bin/wine" winetricks -q d3dcompiler_43 but replacing "Proton 4.2" with the actual version used). With that workaround the game is very playable and completable.
Unknown(an hour with Proton)Crashes during combat
Unknown(an hour with Proton)
