ebkr
[BUG] - (Linux) Risk of Rain Returns launch parameter is incorrect
Describe the bug The launch parameter listed under the "Set Custom launch parameters" is incorrect if the user is running Linux (potentially only Flatpak/manual launch argument). The launch parameter given does not list a drive letter (default seems to be Z under proton) similar to the launch parameter given by Risk of Rain 2 for example. Adding the Z: at the start fixes the issue.
RORR launch parameter:
--rom_modding_root_folder "/(Path to profile)
ROR2 launch parameter:
--doorstop-enabled true --doorstop-target-assembly "Z:/(Path to profile)
This causes the game to refuse to launch when the launch parameter is given manually. I am unable to confirm if this effects the "Start modded" button as that convenience is currently unsupported on Flatpak steam.
To Reproduce Steps to reproduce the behavior:
- Make a RORR profile.
- Set launch arguments manually
- Game refuses to launch
Expected behavior launch argument copied into Steam should launch the game with mods active and not cause it to stop launching.
Additional context Version of Steam Installed - Flatpak. This means that I need to manually add the launch parameter to steam. Unknown if this changes anything.
Game and Profile are installed on external drive. Unknown if this changes anything.
ROR2 is installed the same as above however and produces the correct path.
Assuming you are on the latest (3.2.3), Go to Settings -> Change launch behaviour. Make sure you have Proton selected.
I changed that before and it has no effect on the launch parameter. If I go onto a windows computer the launch parameter has a drive letter assigned to it (in my case its C since the profile is not on an external drive under windows). Strange that under linux it does not.
I just did some troubleshooting using ChatGPT (I know probably not the best way to troubleshoot), and found out that Proton ignores the winhttp.dll that is installed with either the game or BepInEx. It instructed me to use protontricks and run protontricks 632360 winhttp=native in the terminal. This immediately forced it to work.
