Upon further testing, this is caused by the game (and Steam folder) being on an NTFS drive. I won't close this, but the incompatibility is with Proton, not R.E.P.O..
Upon FURTHER testing, this was not the case. I have no idea what caused this bug. I will now close this issue.
Upon FURTHER testing, this was not the case. I have no idea what caused this bug. I will now close this issue.
well uh don't close it if it isn't solved @kisak-valve
Ok, upon further studying of the log it was because of inability to create symlinks which is probably NTFS fault, and OP got it right the first time
@callmeclover
Oh! That's interesting. Should I reopen this?
You can if you want, even though this is a known problem that technically relates to Proton (the Wine component) not being able to symlink to it's installation.
The reason why it does this is to save space.
Technical details:
Since each game creates one Windows install (see /run/media/max/File Sack1/SteamLibrary/steamapps/compatdata/3241660/pfx/, if Proton had to copy all it's installation files (I'm talking DLLs here) to the drive, for each game it would add around half a gigabyte of wasted space total.
And when you own lots of games, that adds up.
Add the following to launch options:
mkdir -p $STEAM_COMPAT_CLIENT_INSTALL_PATH/steamapps/compatdata/$STEAM_COMPAT_APP_ID; STEAM_COMPAT_DATA_PATH=$STEAM_COMPAT_CLIENT_INSTALL_PATH/steamapps/compatdata/$STEAM_COMPAT_APP_ID %command%
proton experimentalx1 2025-03STEAM_COMPAT_APP_IDx1 2025-05STEAM_COMPAT_CLIENT_INSTALL_PATHx1 2025-05STEAM_COMPAT_DATA_PATH=$STEAM_COMPAT_CLIENT_INSTALL_PATH/steamapps/compatdata/$STEAM_COMPAT_APP_IDx1 2025-05
Compatibility Report
System Information
I confirm:
Symptoms
Game almost always refuses to open, and if it does, it repeats the exact same things in the log until closed.
Reproduction
Open game with Proton Experimental.
Proton Log output
steam-3241660.log