Steam Linux Runtime Soldier update modified and renamed pressure-vessel-launch

[MokouPlays]

I had the misfortune of breaking a MO2 install through my incompetence, and thus wasting a day clean-installing steam and skyrim. While trying to understand why the autoinstall script started derailing when the previous day it was working fine, I found out that the soldier runtime was missing something expected by the install script. After calling friends to go on a wild goose chase, we found this gitlab post by Valve: https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/merge_requests/428

Here is a sample log. It's complaining about wine not being updated and proton 6.3.8 not being used for skyrim, but those are spurious warnings. They're likely related to me using arch. The warning towards the end and failure is definitely related to the gitlab post though.

ModOrganizerLog.txt

See also: https://gitlab.steamos.cloud/steamrt/steamrt/-/wikis/Soldier-release-notes

[kdormer]

Having this same issue. Did you find a workaround?

[MokouPlays]

Sadly no. I've no clue how the executable was supposed to be used by the install script or even where it specifically calls pressure-vessel-launch. I suspect it's being called indirectly via protontricks. A project maintainer could probably fix this after like 10 minutes of documentation reading (assuming the new pressure vessel executable doesn't make it too hard to access old functionality), so I'm hopeful for a fix on this soon.

[Compizfox]

Same issue.

For clarity (and searchability), the relevant error is:

warning: ~/.cache/protontricks/proton/Proton 6.3/bin/wine cmd.exe /c echo '%AppData%' returned empty string, error message "~/.cache/protontricks/proton/Proton 6.3/bin/wine: line 155: /mnt/games/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pressure-vessel-launch: No such file or directory" 

[ISAndreiva]

This is caused by protontricks 1.8.1 and was already fixed in 1.8.2. You mentioned you are on Arch and are probably using protontricks from the AUR which is out of date. Either use another way to install protontricks or use the protontricks-git package from the AUR instead of protontricks

[MokouPlays]

I had some other issues with the git version a few weeks ago which forced me to move to the other version, but I can confirm the git version works for Mod Organizer 2. AUR package maintainers: can't live with them, can't live without them. I'll leave this issue open for a week in case one of the other rolling release distros has the same problem and needs to report their workaround.

[kdormer]

It will now install properly but trying to launch MO2 immediately crashes. Not sure if this is related to using protontricks-git or not.

[MokouPlays]

When you say MO2 immediately crashes, do you mean MO2 itself, or Skyrim crashing on the main menu after being launched from MO2 (even with no mods enabled)? MO2 itself seems to install and run after switching to protontricks-git, but I'm dealing with the latter problem which I think is a separate issue relating to SKSE. SKSE seems to be working fine when installed alone; I'm still investigating what's crashing skyrim at the main menu all is well on latest proton version instead of 6.3.

[voidedlegacy]

@kyle-dormer are you running standard arch linux or a distribution. My problem was solved via moving to manajro or fedora.

[kdormer]

@MokouPlays I get a black window that flashes quickly before crashing. Managed to read:

INFO: read executable location 'Z'
ERROR: cannot execute 'Z' - no such file or directory

Seems to be related to having Fallout installed on my media drive but will test this.

[kdormer]

@firaenv I'm running standard Arch, but have used MO2 fine before. Thank you for your suggestion.

[voidedlegacy]

ah. Well I moved to a base arch installation and it worked perfectly. What I did was follow this video: https://www.youtube.com/watch?v=rH-IiKxoozw&t=206s and it worked like a charm!

[voidedlegacy]

@MokouPlays from what I've tested, Your game needs to be installed on your home filesystem. That should fix the issue of it not starting

[soulflyman]

Same issue.

For clarity (and searchability), the relevant error is:

warning: ~/.cache/protontricks/proton/Proton 6.3/bin/wine cmd.exe /c echo '%AppData%' returned empty string, error message "~/.cache/protontricks/proton/Proton 6.3/bin/wine: line 155: /mnt/games/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pressure-vessel-launch: No such file or directory" 

Got the same error on this specific line on my arch based endeavourOS. Protontricks version is used is 1.10.1.

So the error states that the environment variable PROTONTRICKS_STEAM_RUNTIME is not set.

Launching the install.sh and setting the variable manually fixed the error for me:

PROTONTRICKS_STEAM_RUNTIME=legacy ./install.sh

[rockerbacon]

Same issue.

For clarity (and searchability), the relevant error is:

warning: ~/.cache/protontricks/proton/Proton 6.3/bin/wine cmd.exe /c echo '%AppData%' returned empty string, error message "~/.cache/protontricks/proton/Proton 6.3/bin/wine: line 155: /mnt/games/SteamLibrary/steamapps/common/SteamLinuxRuntime_soldier/pressure-vessel/bin/pressure-vessel-launch: No such file or directory" 

This is not a new error and is usually caused by switching between Proton versions (usually a version downgrade, can't confirm this is the exact cause in this particular instance without testing). Steam makes no attempt at cleaning the first bottle it creates and not all Wine versions work with all bottles.

The solution here would be deleting the existing bottle and creating a new one, this is covered in the post-install instructions, section "Using alternative proton versions".