Change:
<ins> diff --git a/src/r2mm/launching/runners/linux/SteamGameRunner_Linux.ts b/src/r2mm/launching/runners/linux/SteamGameRunner_Linux.ts index ddee0e9..fc9ffca 100644 --- a/src/r2mm/launching/runners/linux/SteamGameRunner_Linux.ts +++ b/src/r2mm/launching/runners/linux/SteamGameRunner_Linux.ts @@ -61,15 +61,9 @@ export default class SteamGameRunner_Linux extends GameRunnerProvider { async start(game: Game, args: string): Promise<void | R2Error> { const settings = await ManagerSettings.getSingleton(game); -        const steamDir = await GameDirectoryResolverProvider.instance.getSteamDirectory(); -        if(steamDir instanceof R2Error) { -            return steamDir; -        } - -        LoggerProvider.instance.Log(LogSeverity.INFO, `Steam directory is: ${steamDir}`); try { -            const cmd = `"${steamDir}/steam.sh" -applaunch ${game.activePlatform.storeIdentifier} ${args} ${settings.getContext().gameSpecific.launchParameters}`; +            const cmd = `steam -applaunch ${game.activePlatform.storeIdentifier} ${args} ${settings.getContext().gameSpecific.launchParameters}`; LoggerProvider.instance.Log(LogSeverity.INFO, `Running command: ${cmd}`); await exec(cmd); } catch(err) { </ins>

Discussion:
When you try to start any game from r2modman both modded and vanilla you get a terminal like window saying that "You are missing the following 32-bit libraries, and steam may not run: Press enter to continue: " After pressing enter the terminal like window closes Steps to reproduce the behavior: r2modman any game using r2modman The game should launch ! Steam is installed using nixos options (I might be stupid or something but i cant find where meta.maintainers list is) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
This is a known issue, and I am still unsure of the best way to solve it. On NixOS, if you want to launch a Steam game from outside the Steam launcher, you would have to run it via . I chose not to wrap r2modman in the Steam FHS environment, because it can be used with non-Steam games, but doing so may be the most reliable way to let it run non-Steam games as well. The way I have been using r2modman is only to install mods, then modify the launch command for the game in Steam to run the game through the r2modman profile for said game. Do you think we should wrap r2modman in an FHS environment like we do for Lutris and Heroic?
Honestly I'm not too sure either. One downside of using as part of r2modman is that it makes the package depend on a non-free derivation, but that's not too big of a deal. Is there a way to have the steam runner in use the steam fhs env? That seems like what r2modman is trying to run. However, this doesn't solve the issue of non-steam games. What exactly is the best user experience for those running non-steam games? I think using a FHS env is the only way to get those games to run. Ideally I wouldn't like to maintain a FHS environment specifically for r2modman as well, could we borrow the steam FHS env? I think if we're able to, simply using the steam FHS is the best solution.
So what should i do for now?

Can you please share the command to launch modded version of the game?
If you want to find the additional launch arguments to give to steam to launch the modded version, r2modman displays it in the help section: !
Thanks!
Reopening, as I do want to address this issue in the package somehow.
hi there. (I just realised ?) Regardless, it seems to still not work for me, though I think it's because it's a proton game? I can open a new issue if you'd like, but here's the error I get when trying to launch both modded and vanilla:
Yes, please open a separate ticket.

When opening r2modman, you get a white screen (due to same issue that heroic fixed i believe, caused by electron update) Steps to reproduce the behavior: r2modman a few seconds Usable, no white screen If applicable, add screenshots to help explain your problem. Add any other context about the problem here. you should know what to do <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.