Works awesome! Thanks for introducing me to xdotool, what a helpful utility. Question: what does the --file flag in your command do? I can't find it in the manpage
Jozzo
I had a similar problem, it was caused by undervoltage. Are you using the official power supply?
Reporting back!
Reformatted with btrfs, steam now does this when I open the game (didn't before):
anddd it works! Can't believe this whole headache was just exfat all along lol!
Thank you for your help :D
Reporting back!
Reformatted with btrfs, steam now does this when I open the game (didn't before):
anddd it works! Can't believe this whole headache was just exfat all along lol!
Thank you for your help :D
I think you've just pointed me in the direction of a solution...
The comment you're referring to seems to be this one:
mv Launcher Launcherbak
ln -s bin Launcher
ln -s ./bin/bg3_dx11.exe ./bin/LariLauncher.exe
cp ./Launcherbak/*.dll ./bin
creating a symlink to trick steam into thinking it's running the launcher when it actually runs the game. BUT ... my SSD is formatted as exFAT, which doesn't support symlinks, so I can't do this.
So I'm guessing proton is trying to create a symlink at pfx/dosdevices/c when it installs .NET, but fails, which is also probably why everyone else seems to have a breezy time with it. Not sure why my other games haven't run into this though... maybe they haven't needed to install anything there?
I will report back after reformatting my entire SSD lol
I think you've just pointed me in the direction of a solution...
I tried to create a symlink "c:" pointing to ../drive_c, but I couldn't. "Operation not permitted" I then got ptsd flashbacks to the last time this happened - turns out it was because my SSD is formatted as exFAT, which doesn't support symlinks.
I'm guessing proton is trying to create this symlink when it installs .NET, but fails, which is probably why everyone else seems to have a breezy time with it. Not sure why my other games haven't run into this though... maybe they haven't needed to install anything there?
I will report back after reformatting my entire SSD lol
Ohh, is the "c" just a symlink to the drive_c folder?
I need STEAM_COMPAT_DATA_PATH because my proton is installed in a different steam library than the game, all of my proton games use this. I tried to remove it anyway and try just '--skip-launcher', but now the game doesn't launch lol
The command likely won't work for you because you don't have proton installed at that location
Still the same error unfortunately.
Interestingly though, when I try to install .NET manually via protontricks-launch -v --appid 1086940 /home/user/Downloads/windowsdesktop-runtime-6.0.35-win-x64.exe
I get the following error:
/media/user/T7/Main/Games/SteamInstalled/steamapps/compatdata/1086940/pfx/dosdevices/c:/windows: No such file or directory
Going down that tree I see the entire path is there except for "/c" at the end. I manually added a "c" folder, but then I get stuck at this error:
protontricks (ERROR): Active compatibility tool was found, but it's not a Proton installation supported by Protontricks.
Proton installation could not be found!
I know my proton installation works because all my other games use it fine. Proton is on a different drive than BG3, could that cause issues?
No, installed from debian repository
I already skip the launcher but this error still happens. My launch args are
STEAM_COMPAT_DATA_PATH=/home/user/.local/share/Steam/steamapps/compatdata %command% --skip-launcher
Good solution, cheers! I also followed the other commenter's idea to add it as a KDE shortcut so I can use it on demand.
I guess I'll just need to be careful not to paste a bazillion lines of text lol