You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Steam pushed out an update which added screen recording for all platforms. This update also included an update to the runtime environment for native games. By default steam now uses something called scout 1.0. Here are the relevant patch notes: https://store.steampowered.com/news/app/593110/view/4472730495692571024
"Native titles will execute in 'Steam for Linux runtime 1.0 (scout)' by default, instead of the legacy runtime environment."
This seems to have broken r2modman's ability to launch valheim in modded mod. The game can still be launched in vanilla mode.
To Reproduce
Steps to reproduce the behavior:
Create a valheim modded profile on r2modman
Try to launch valheim
Steam will open and valheim will briefly show it is running and then immediately crash
You should be able to launch valheim in vanilla mode via steam directly or via r2modman
A handful of people have verified that this work around works.
Confirmed an issue on Arch, Kubuntu, and Pop!
This launch parameter forces steam to use the legacy runtime environment from before the update.
Other have stated that they manually installed the mods and launched valheim via Steam in the new runtime environment and it works without issue.
This was an issue in r2modman 51 and 52.
I have also tried creating a fresh profile and updating mods to the latest which did not fix the issue. I also tried making a barebones profile with just a couple simple mods and this also did not launch.
When you launch Valheim in vanilla mode valheim also talks about not being about to load PlayFab and requiring some MS runtime files. Unsure if this is related.
The text was updated successfully, but these errors were encountered:
I can confirm. I manually load BepInEx. Since the latest Steam update, Valheim no longer loads. When i Start team using "-compat-force-slr off", Valheim, with BepInEx loads fine. I'm also able to just start Valheim, with BepInEx, outside of Steam just using the sh script.
Describe the bug
Steam pushed out an update which added screen recording for all platforms. This update also included an update to the runtime environment for native games. By default steam now uses something called scout 1.0. Here are the relevant patch notes: https://store.steampowered.com/news/app/593110/view/4472730495692571024
"Native titles will execute in 'Steam for Linux runtime 1.0 (scout)' by default, instead of the legacy runtime environment."
This seems to have broken r2modman's ability to launch valheim in modded mod. The game can still be launched in vanilla mode.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Valheim should launch with mods
Screenshots
NA
Additional context
I have a work around for this issue. You can add the launch parameter "-compat-force-slr off" to the r2modman steam launch parameters. I documented this solution in the discord (https://discord.com/channels/727304496522461185/1303809239898259476/1303909649153527870) and here: https://www.reddit.com/r/valheim/comments/1glggwy/workaround_modded_valheim_on_linux_with_r2modman/
A handful of people have verified that this work around works.
Confirmed an issue on Arch, Kubuntu, and Pop!
This launch parameter forces steam to use the legacy runtime environment from before the update.
Other have stated that they manually installed the mods and launched valheim via Steam in the new runtime environment and it works without issue.
This was an issue in r2modman 51 and 52.
I have also tried creating a fresh profile and updating mods to the latest which did not fix the issue. I also tried making a barebones profile with just a couple simple mods and this also did not launch.
When you launch Valheim in vanilla mode valheim also talks about not being about to load PlayFab and requiring some MS runtime files. Unsure if this is related.
The text was updated successfully, but these errors were encountered: