Opting into the beta fixes the mouse not appearing in the overlay. The alt-tabbing issue is still present, other than that the game runs flawlessly.

• System information
• i7-4770k, GTX 1060 6gb
• i3-wm, compton, 5.0.4-arch1-1-ARCH
• Driver Version: 4.6.0 NVIDIA 418.56
• Proton version: 4.2-1

Works almost perfectly out of the box, only issue being that that the refresh rate is stuck at 60hz. It might be related to Proton fullscreen patch mentioned here, since higher refresh rates are available when using a custom proton-tkg build with the patch disabled.

Invisible character models on Intel graphics.

System Information

Works great here, only that the quit button sometimes just makes the game freeze.
i5-4460
rx 580
proton 4.2-2
system information: https://gist.github.com/thunder1410/76897c9bd211c74b30968baa4037ce96

I'm on Fedora 28 64 bit, with an nvidia gtx 960, with the proprietary drivers.

The only issue I'm having with it is that sometimes the process seems to freeze on exit. Other than that it works flawlessly.

It also hung on me once with proton 4.2-3 on the 3 times I played the game.

Mine appears to still be working fine. Attach a proton log to your post ( right click the game, select properties, set launch options and add this: PROTON_LOG=1 %command% ) so Valve et al can dig through it and see what's going on under the hood.

After installing Lutris requirements, the game seems to boot fine on my computer without any issues.
Hope it'll help getting things right

Drivers
Wine

• Proton: 4.2-3
• Kernel version: x86_64 Linux 5.0.9-arch1-1-ARCH
• GPU: RX580 (4gb)
• Driver/LLVM version: Radeon RX 580 Series (POLARIS10, DRM 3.27.0, 5.0.9-arch1-1-ARCH, LLVM 8.0.0)

Confirming that the beta does work correctly to solve the issue @kisak-valve

Connecting in multiplayer works, but has constant lag and is not caused by graphics options. Using proton 4.2-9.

Cannot confirm. Have had no issues with multiplayer specifically when it comes to FPS.

RoR2 does have an issue with starting and full video memory, is your video memory full when launching? (can check with nvidia-smi if using an NV GPU)

Possibly that. Maybe I just get too unlucky with starts with friends as I had good fps in multiplayer with quick match just now.

Just an update to my earlier comment, @kisak-valve was correct. Mesa 19.1 hit Flatpak beta and the invisible character models are now gone and the game seems to work perfectly (outside of the unplayable framerate on Intel gfx.)

Proton 4.11-1 reports the correct refresh rate (144 Hz) to the game, as 144 Hz appears in the video settings. However, the game is still capped at 60 FPS for some reason. Again, this is not the case on Windows.

Using Manjaro Budgie.

As of 4.11-10, the mouse controls in this game have started exhibiting strange behavior. Here's a short clip: https://streamable.com/mpxo7

It started happening around the 35-minute mark of this run, and has never happened to me before. This is the first run I've done on 4.11-10, which led me to believe it was related.

I've been experiencing the same mouse issue with 4.11-10. Reverting to 4.2-9 seems to have fixed it.

Launching Risk of Rain 2 through any version of proton results in a black screen that must be force quit.

Specs:
4.16.18-MANJARO
RX 580
Intel i5-6500

Fossilize INFO: Overriding serialization path: "/home/paul/.local/share/Steam/shader_cache_temp_dir_vk_64/fozpipelinesv4/steamapprun_pipeline_cache".
Installing breakpad exception handler for appid(steam)/version(1576550254)
Opted-in Controller Mask for AppId 0: 0

(steam:48386): Gtk-WARNING **: 17:56:43.465: gtk_disable_setlocale() must be called before gtk_init()
Installing breakpad exception handler for appid(steam)/version(1576550254)
roaming config store loaded successfully - 2978 bytes.
migrating temporary roaming config store
BRefreshApplicationsInLibrary 1: 25ms
[1230/175645.629852:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1230/175645.659397:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1230/175645.685731:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
Installing breakpad exception handler for appid(steam)/version(1576550254)
Installing breakpad exception handler for appid(steam)/version(1576550254)
Failed to init SteamVR because it isn't installed
ExecCommandLine: "'/home/paul/.local/share/Steam/ubuntu12_32/steam'"
System startup time: 13.33 seconds
[1230/175646.083892:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1230/175646.108190:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
BuildCompleteAppOverviewChange: 108
RegisterForAppOverview 1: 5ms
RegisterForAppOverview 2: 5ms
[1230/175647.269026:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[1230/175647.340854:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
[632360]Non-Steam Controller Configs Enabled: 1
Installing breakpad exception handler for appid(steam)/version(1576550254)
Opted-in Controller Mask for AppId 632360: 0
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to ProcessingInstallScript with ""
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to RunningInstallScript with ""
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to SynchronizingCloud with ""
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 632360, ActionID 1] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 632360, ActionID 1] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 632360 "", ProcID 51081, IP 0.0.0.0:0
Starting app 632360
>>> Adding process 51081 for game ID 632360
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/paul/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 632360, ActionID 1] : LaunchApp changed task to Completed with ""
ERROR: ld.so: object '/home/paul/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/paul/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/paul/.config/openvr/openvrpaths.vrpath'
>>> Adding process 51082 for game ID 632360
>>> Adding process 51083 for game ID 632360
>>> Adding process 51087 for game ID 632360
>>> Adding process 51089 for game ID 632360
>>> Adding process 51092 for game ID 632360
>>> Adding process 51094 for game ID 632360
>>> Adding process 51097 for game ID 632360
Installing breakpad exception handler for appid(steam)/version(1576550254)
>>> Adding process 51106 for game ID 632360
>>> Adding process 51111 for game ID 632360
>>> Adding process 52559 for game ID 632360
>>> Adding process 52681 for game ID 632360
Mono path[0] = 'Z:/home/paul/.local/share/Steam/steamapps/common/Risk of Rain 2/Risk of Rain 2_Data/Managed'
Mono config path = 'Z:/home/paul/.local/share/Steam/steamapps/common/Risk of Rain 2/MonoBleedingEdge/etc'
Installing breakpad exception handler for appid(gameoverlayui)/version(20191216164847)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
[1230/175658.332768:INFO:crash_reporting.cc(270)] Crash reporting enabled for process: renderer
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Game update: AppID 632360 "", ProcID 51087, IP 0.0.0.0:0
RecordSteamInterfaceCreation (PID 51087): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 51087): SteamUser019 / User
RecordSteamInterfaceCreation (PID 51087): SteamUser019 / User
RecordSteamInterfaceCreation (PID 51087): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 51087): SteamNetworking005 / Networking
RecordSteamInterfaceCreation (PID 51087): SteamGameServerStats001 / GameServerStats
RecordSteamInterfaceCreation (PID 51087): STEAMHTTP_INTERFACE_VERSION002 / HTTP
RecordSteamInterfaceCreation (PID 51087): STEAMINVENTORY_INTERFACE_V002 / Inventory
RecordSteamInterfaceCreation (PID 51087): STEAMUGC_INTERFACE_VERSION010 / UGC
RecordSteamInterfaceCreation (PID 51087): STEAMAPPS_INTERFACE_VERSION008 / Apps
RecordSteamInterfaceCreation (PID 51087): SteamGameServer012 / GameServer
RecordSteamInterfaceCreation (PID 51087): SteamFriends015 / Friends
RecordSteamInterfaceCreation (PID 51087): SteamMatchMakingServers002 / MatchmakingServers
RecordSteamInterfaceCreation (PID 51087): STEAMUSERSTATS_INTERFACE_VERSION011 / UserStats
RecordSteamInterfaceCreation (PID 51087): STEAMSCREENSHOTS_INTERFACE_VERSION003 / Screenshots
RecordSteamInterfaceCreation (PID 51087): STEAMREMOTESTORAGE_INTERFACE_VERSION014 / RemoteStorage
RecordSteamInterfaceCreation (PID 51087): SteamMatchMaking009 / Matchmaking
RecordSteamInterfaceCreation (PID 51087): STEAMAPPLIST_INTERFACE_VERSION001 / AppList
RecordSteamInterfaceCreation (PID 51087): SteamUtils009 / Utils
RecordSteamInterfaceCreation (PID 51087): SteamController006 / Controller

Let me know what other information would be helpful.

Here's the gist: https://gist.github.com/pasimko/4dd96b15fb2e9b35295fc342c3475576

I just launched the game and it worked. Nothing changed, as far as I can tell. It just worked this time.

It's been quite a while and I'd like to report that the "freeze on exit" I was getting months ago hasn't been happening anymore. However I've noticed now that performance seems to be... worse, especially during extended play.

With the latest proton version: 4.11-12 the game crashes if a PS3 controller is plugged in. This doesn't happen with 4.2-9 or 4.21-GE-2.
Also I'm still experiencing issues with it freezing on exit.

steam-632360.log
Here is the log.

Here's the problem:

wine: Call from 0x7b45318c to unimplemented function hid.dll.HidP_GetUsageValueArray, aborting

@TheGreatestJannet You should be able to work around this by enabling game controller mapping in the Steam client. This will make the controller appear as an Xbox controller to the game, which I think will avoid this crash.

@TheGreatestJannet I could not replicate the crash you are getting with a ps3 controller plugged in via usb. I have built a version of Proton that contains a potential fix - could you test it and see if it gets rid of the crash for you?

The build is uploaded here with the lock code "ps3": https://www.codeweavers.com/xfer/alasky/risk-of-rain-ps3/

To test, you can put the tar into ~/.steam/steam/compatibilitytools.d/. and then untar the bundle. You might have to create the compatibilitytools.d folder in that location, since it is not created automatically. After dropping the build in the folder, when you restart Steam, the build should show up in the dropdown list of Proton builds to choose from.

If you have enabled controller mapping to get around the crash, please turn it off before testing :)

Hi @alasky17 your fix does solve the issue however it makes the mouse act very weirdly and with very low sensitivity. Seeing as I haven't played the game with a PS3 controller I'm not sure if this happened on older builds but I'm pretty sure it didn't. Furthermore when going ingame it shows unknown on the abilities instead of the actual buttons to press and my character runs around in a circle as if the analog stick was pushed down when it isn't. Finally some buttons seem to work but not others.
However the game doesn't crash at all anymore. Thanks for your hard work!

@TheGreatestJannet Thank you for testing that! Could you get a log of the bad mouse behavior and the incorrect cursor controls with +x11drv,+x11settings,+event,+cursor,+win,+message,+hid,+hidp,+hid_report,+plugplay,+rawinput,+dinput,+xinput,+joystick,+setupapi

In order to add extra logging channels, go into the Proton folder in compatbilitytools.d and create a copy of user_settings.sample.py that is renamed "user_settings.py". You can then edit user_settings.py to add the channels to the end of the "WINEDEBUG" line inside the quotes.

Just messing around a bit to recreate the problems with logging turned on should do the trick :)

@alasky17 Hi unfortunately the log file is too big to upload to github even though I ran it for less than 30 seconds. Do you have anywhere I could upload it?

Here is the archive I didn't expect it to compress so well!
steam-632360.zip

@TheGreatestJannet Thank you!

@TheGreatestJannet I uploaded a new version of Proton build to the same location with more traces added to gather extra logging information. Could you try this new build, verify that the behavior is the same, and take a new log with the same logging channels added? Thank you so much!

Hi @alasky17 sorry for the delay here is the log using the new build.
steam-632360.zip

Launching Risk of Rain 2 results in no visible window. Nothing happens. Status in Steam changes to "Running" for a while and then disappears again.

System Info : sysinfo
Proton Log : steam-632360.log
Proton version: 4.11-12 (4.2-9 has the same result)

If it helps:
The device is optimus-enabled. The dedicated card is Nvidia 1050 Ti.
Running Steam using optirun steam doesn't display current gfx driver in SysInfo. (Intended behavior of bumblebee I believe). Bumblebee seems to be working perfectly. Changing RoR2's startup command to optirun %command% also doesn't help.

Thank you so much. @kisak-valve

Unable to confirm, just tested. RX 570, mesa 19.2.8, kernel 5.5.4. So perhaps a mesa weirdness?

Had to update mesa, weird but it's fixed now.

Unable to confirm, though I do have a mesa update that I have yet to apply

New update has 'just worked' for me, hopefully someone knowledgeable can chime in. Last time I had to reinstall mesa and vulkan-radeon mentioned above.
steam-632360.tar.gz

Since the artifact update from today, the game launches, but does not show anything for a few minutes before closing itself.
The log : steam-632360.log

Well, I just now could launch the game and play for a few minutes. I only re-launched steam once since the last bug, perhaps it could have changed something. You can dismiss my comment about the artifact update, so far so good.

ROR2 does not work anymore with Proton 5.0 (official from Steam)
switching back to 4.1 or 4.2 work fine

RoR2 works perfectly with proton 5.0-6.
I'm using a vega64 with mesa 19.3.3.
@danilw each time RoR seemed to stop working on my end, was when I needed to reboot my computer after lots of upgrades (via apt). Have you tried that?

okey it fixed with clean prefix.
ROR2 with Proton 5.0.6 work after cleaning prefix.

So the error where the game doesn't launch and a window with the game's logo and loading bar happens whenever you apply a Mesa update, happens a lot on Arch based/rolling release distros. It's fixed by re-installing Mesa and Vulkan packages, hopefully it won't happen when the game is out of early access or if a new Proton version could fix it.

I play ROR2 frequently with steamplay beta enabled for all games using proton 4.11 as well as proton 5.0.

Occasionally, I get strange crashes on my computer which essentially look like the root disk unmounts. The result of this crash is always that I have to restart.

Lately, once I restart, ROR2 will no longer launch, with the cryptic wine/proton Error:

Data folder not found

Details:
unix/data0/matthew/SteamLibrary/steamapps/common/Risk of Rain 2
There should be 'Risk of Rain 2_Data'
folder next to the executable

The reason this is cryptic, is because 'Risk of Rain 2_Data' is in that folder! Additionally, I've verified the integrity of both the proton installation steamplay is using as well as ROR2, and both passed!

ls /data0/matthew/SteamLibrary/steamapps/common/Risk\ of\ Rain\ 2
 MonoBleedingEdge       steam_api64.dll           WinPixEventRuntime.dll
'Risk of Rain 2_Data'   UnityCrashHandler64.exe
'Risk of Rain 2.exe'    UnityPlayer.dll

Anybody have any clue why this might be happening?

For the game does not launch problem, it was coming from my packages. Even though I tried updating them yesterday, it seems the ones from yesterday had the same problem than the packages I had before. But at least one less issue.

I still have the fps issue though, but it seems to be a little better than before (only drops down to 30fps).

EDIT: No more issue since 1.0 (or maybe thanks to package upgrades around this time)

As of the 1.0 release, the game crashes when opening the multiplayer menu.

Here's a log for when this occurs:
steam-632360.log

Same issue as @CubeTheThird, even with Proton 5.13 after using a workaround for a no-launch issue.

Confirmed as well, with Proton 5.13. Here is my latest log:

steam-632360.log

Confirmed with Proton 5.0-9, 5.13, and 5.9-GE-5-ST. Opening the multiplayer menu and attempting to create or join a lobby will cause the game to become unresponsive until forcefully killing the process.

Can confirm that the Multiplayer Menu (the lobby) opens successfully as of Proton 5.13-2.

Risk of Rain 2 has started crashing shortly after launching the game with Proton 5.13-2 on Void Linux. The game launches to a black screen and, if not in fullscreen, this window is created:

After the bar fills up the game crashes. I've tested on 5.0-10 and the game runs well.
steam-632360.log

Latest experimental (1611698283 experimental-5.13-20210126) instantly stopped and log file doesn't even seem to show anything happens:

➜  ~ cat steam-632360_latest.log 
======================
Proton: 1611698283 experimental-5.13-20210126
SteamGameId: 632360
Command: ['/home/walshy/.local/share/Steam/steamapps/common/Risk of Rain 2/Risk of Rain 2.exe']
Options: {'forcelgadd'}
SteamLinuxRuntime: v0.20210105.0-0-g0e6df4c
pressure-vessel: 0.20210105.0+srt1 scout 0.20210106.0
soldier: 0.20210105.2 soldier 0.20210105.2
======================

steam-632360_latest.log

I've had the best result with 4.11-13 (1582308386 proton-4.11-13) - initially, it was failing with:

Xlib:  extension "NV-GLX" missing on display ":0".
Xlib:  extension "NV-GLX" missing on display ":0".
536536.118:002f:0030:err:vulkan:wine_vk_instance_load_physical_devices Failed to enumerate physical devices, res=-3
536536.118:002f:0030:err:vulkan:wine_vkCreateInstance Failed to load physical devices, res=-3

Installing mesa-vulkan-drivers as per StackOverflow answer fixes that and the game launches however it is pretty laggy but works.

So, for me at least, using 4.11-13 gives the best result.

Not sure if this has been mentioned in comments, but anti-aliasing of the game world doesn't seem to be working for me. UI anti-aliasing works totally fine, but there doesn't seem to be any AA performed on the game world itself. Other than that, and a weird issue that crops up sometimes where the end screen for a run doesn't fully load and I have to alt-f4, flawless.

With Proton 6.3-1 after a session of 20+ minutes camera movement becomes very stuttery, reverting to 5.13-6 fixes the issue. Compositor is also disabled.

• RX 580 8GB
• R5 2600X
• Mesa 21.0.1
• Kernel 5.11.11
• Arch Linux
• KDE Plasma 5.21

@wantija I think you are running into https://github.com/ValveSoftware/Proton/issues/3316 Hopefully there will be a fix soon :)

I'm having random crashes recently using Proton 6.3-2. Game works without any issues until it suddenly crashes showing unity crash reported window. Usually crash happens after 20-40 minutes of game, after enabling logging the crash happened after about 5 minutes.

r7 2700x, RTX 2080, kernel 5.11.10, manjaro
https://gist.github.com/mariuszandrzejewski/8416014f49e692887bbca27dd5f8b5e0

• GPU: nvidia 1070
• Driver/LLVM version: 495.29.05
• Kernel version: 5.14.12

4.2-9 and 4.11-13 no longer launch the game. Proton log appears to either fail to create a window or fail to find opengl.dll for unity.

3.16-9 works and 5.0-10 works.

5.13-6 introduces a crash during loading if you leave the window (such as moving mouse to another monitor, moving the window to a different monitor, etc) and has a significant performance regression. (previously reported in 2020)

6.3-7 and proton experimental seems less prone to crashing, but still seems regressed from 5.0-10 and 3.16-9 in terms of performance.

At least for me it seems I was affected by ValveSoftware/steam-runtime#312 (comment) which resulted in the reduced performance of the game as I happened to have the vulkan drivers for intel and my igpu enabled. After removing the intel vulkan drivers the game performs spectacularly.

Hmm If I can replicate it again I will try to report it upstream, however after reinstalling ANV drivers it ended up failing for other reasons that seem more related to proprietary drivers than ANV and the performance issues dont reappear. Perhaps it was just another consequence of failing to upgrade the prefix instead. (setting up my system to actually run on ANV is a bit too painful for me)

I am experiencing a significant lag with the keyboard control response with playing Risk of Rain 2 when I have "repeat keys" enabled. If I disable "repeat keys" the problem disappears, which leads me to believe that it is due to multiple commands sent to the game when holding e.g., "W" to move forward, several "W" commands are queued and sent sequentially.

I tested and verified that the keyboard works as expected with "repeat keys" enabled in other games I have tried, so for me the issue seems to be isolated to RoR2.

I can't get RoR2 to recognize my controller. I have tried both an XBox Series X (BT and USB modes) and an old Logitech Rumblepad. Both work perfectly with native Linux games, Steam and not-Steam. I have tried forcing Steam Input to enabled and disabled. I have also tried 6.3 and 5.13 versions of Proton. RoR2 doesn't recognize either controller under any settings.

steam_system_info.log.gz
steam-632360.log.gz

@stharward So did you have controllers working with other proton games?

user$: steam
steam.sh[21854]: Running Steam on pop 21.10 64-bit
steam.sh[21854]: STEAM_RUNTIME is enabled automatically
setup.sh[21923]: Steam runtime environment up-to-date!
steam.sh[21854]: Steam client's requirements are satisfied

@zensei-n7 Yes, I can confirm that I face the same issues since the DLC update. They changed some performance-related things about the underlying game engine and that has affected the way this game runs under Proton (mostly negatively).

One very important thing is that it is no longer possible to create a multiplayer server on Risk of Rain 2 under Proton, unless you disable e-sync, which severely affects FPS. The game just crashes if you try.

@woalk Thank you for the clarfication. I'm glad that I'm not the only one. I spent days trying to figure out why the performance is inconsistent. Granted that I also have low-end hardware, but this never happened before the update, and I could not accept the fact that it's just the update and not my system or other circumstances.

The fps sometimes drops to 50, but then goes up to 100+ if for example compositor and background app such as Discord are disabled. And the fps can jump and down by simply going from the main menu to the character loadout. I guess I have to see and wait if the devs will patch/improve the performance of the game.

@zensei-n7 While I did submit an official bug report to Gearbox Publishing about the performance and crash, and they told me that they might pass it onto the developers, I highly doubt at the moment that we will see any official patch concerning issues on Linux, as Linux is not an officially supported platform.

This needs to be fixed in Proton by Valve. Maybe it should be moved into a new issue with some explicit logs.

That is fair, but I'm glad to know that it's Proton/Game related issue. I'l just wait for further updates in regards to the game or Proton.

-------- Original Message --------
On Mar 10, 2022, 11:07 AM, Alexander Köster wrote:

@.***(https://github.com/zensei-n7) While I did submit an official bug report to Gearbox Publishing about the performance and crash, and they told me that they might pass it onto the developers, I highly doubt at the moment that we will see any official patch concerning issues on Linux, as Linux is not an officially supported platform.

This needs to be fixed in Proton by Valve. Maybe it should be moved into a new issue with some explicit logs.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: @.***>

@kisak-valve Oh ok, sorry, I couldn't find any specific issue guidelines in neither the README nor the Wiki, so I wasn't sure, especially because those issues are largely caused by the Risk of Rain 2 Survivors of the Void DLC, which could be regarded as a new release.

But in that case, I have attached
here a log from the crash when starting a multiplayer server. It can be mitigated by setting the launch option PROTON_NO_ESYNC=1 %command%, but as I mentioned, with severe drops in performance.

The only thing that stands out to me that's not present in logs where I don't start the multiplayer lobby is this:

CreateFn failed for SteamUser019 User
CreateFn failed for SteamFriends015 Friends
CreateFn failed for STEAMUSERSTATS_INTERFACE_VERSION011 UserStats
CreateFn failed for STEAMSCREENSHOTS_INTERFACE_VERSION003 Screenshots
CreateFn failed for STEAMREMOTESTORAGE_INTERFACE_VERSION014 RemoteStorage
CreateFn failed for SteamMatchMaking009 Matchmaking

Is there anything else that might help in investigating this issue further?

To compare the performance, I usually have shadows enabled in the game, and the fps would be 60+ in-game (with every Proton version, including custom), but now even with low quality shadows, the fps would drop from 90+ (shadows off) to 59 or less in the main menu. I reckon it's worse in-game.

The boot up is also slower than before, even on an SSD. And then there's a slight freeze or stutter when you go to the character loadout from main menu, which usually fixes my performance. This is actually my current workaround alongside with closing other background processes like Discord.

Another thing worth noting is that, when Discord is running in the background, the performance would decrease by roughly 20 fps, and this also happens if the compositor is enabled and can have similar hit; having both processes running is a nightmare with this game. Though, I believe there isn't much reason to enable the compositor, but I feel like it's worth mentioning for the people who use other DEs.

Oddly enough, Discord does not cause a performance hit with Deep Rock Galactic unlike Risk of Rain 2, which I believe is less performance-demanding compared to Deep Rock Galactic. And while the performance impact when the compositor is on is expected (or should be expected), I believe it should not immensely decrease performance: for example, in Deep Rock, I get 7 or 5 fps less when the compositor is on compared to when it's off.

Sorry, too many edits on my message there, but I hope that clears it up.

Multiplayer works on my end, by the way. I did connect to a dedicated server run by a friend of mine, and I never crashed nor disconnected.

Multiplayer works on my end, by the way. I did connect to a dedicated server run by a friend of mine, and I never crashed nor disconnected.

Connecting to a Windows host is no problem for me either. Only when creating a lobby on Linux does the game crash.

I do hope either Proton or RoR 2 patches this performance issue. It looks like Windows user are reporting similar performance issues on the steam discussions.

I decided to give up and simply lower the graphic settings by setting the texture to half instead of full and disable shadows as well. The performance is consistent now, but I dislike how the game looks without shadows on.

Any update on a patch for multiplayer hosting without esync?

Since the newest patch 1.2.3 of Risk of Rain 2, I can host a multiplayer game again without disabling e-sync. I am using Proton 7.0-2, no special launch options.

It still doesn't work for me, huh.

@Justsnoopy30 Did you enable Crossplay? I didn't. Maybe that's the difference?

Nope.

Wait what I just booted it up today and it's working now.

Ah it seems it works on vanilla but breaks when I load with any mods. Even adding just BepInExPack causes it to crash when trying to create a multiplayer game.

Even adding just BepInExPack causes it to crash when trying to create a multiplayer game.

Can't confirm that, have played with plenty of mods without issue. Did you update all of them to the latest version?

Yes.

System Information

• GPU: GTX 1060 6GB
• Driver/LLVM version: 4.6.0 NVIDIA 470.129.06
• Kernel version: 5.4.0-113-generic
• Link to full system information report as Gist: https://gist.github.com/Maclman/ec70a8c3ac9996388587d39bd007d0a4
• Proton version: Proton 7.0-2

Game crashes on host of multiplayer game, disabling esync through PROTON_NO_ESYNC=1 %command% allowed hosting but this caused massive fps stutters.

Getting some shadow flickering in the character selection screen, on both my main machine (RX 6600 XT, Mesa 23.3.3, Proton Experimental) and a Steam Deck (latest stable, default Proton).

I believe that flickering is a thing on windows as well. If not it doesn't persist into the main game

Hello @vadiks2003, this is a bit of a blind guess, but does setting the game's launch options to __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% have an effect?

hello, sorry for late response and making a new issue instead of finding this issue (i was confused of github search ways).

i added these launch options and it is so confusing to be honest. right after i added them into launch options and pressed shift tab, it instatly crashed the game. i decided to re-open the game with PROTON_LOG=1 %command% launch option, and... it didn't crash. i thought maybe the previous launch option has applied only on second attempt of joining the game, so i re-launched the game with absolutely no launch options. it immediately crashed when i pressed shift tab. when i entered PROTON_LOG=1 %command% launch mode, it didn't crash. when i removed all the launch options again, it didnt crash

TLDR: it seems to have helped, in a very confusing way. thank you either way, and i hope this issue won't happen to anybody else

I've` been getting "crashes" on my system that are pretty hard to pin down. The game freezes completely apart from sound, and I have to force-quit it.

I'm on proton experimental, and I have PROTON_LOG set - however, the log is pretty big by the time it crashes. It's not running out of space on disk or anything, but it is up to 2.6GB for this most recent one. It tends to take a while to crash - often a long time into a run, but sometimes at the beginning of a run while the game has been running for a while. Nothing showed in journalctl --user when the freeze happened.

It's also pretty difficult to pin down from the file when it crashes. Luckily, it does gzip down to only 35MB. I've uploaded it to my nextcloud instance here if it's useful to check out - again, it extracts to 2.6GB.

When I managed to look at my log after it had frozen up, the log lines starting with 16743.182:0130:01c4 were showing up, so the freeze happened around that point.

I'm on a Radeon RX470 and AMD Ryzen 5 2600, on Arch with all packages up to date. I'm using Sway as my window manager, but I'm not running gamescope with this game. I'll give that a shot though. This issue is not happening when opening the steam overlay or anything specific - it seems totally random.

I also get full crashes to desktop when getting achievements - sometimes. Not every time, but I just got one then. Unfortunately I didn't have PROTON_LOG running when that one happened - I'll enable it and see if I can speed-run a loadout upgrade.

EDIT:
Got another freeze up - needed to pkill it. This one it quite a lot smaller - only 800MB uncompressed. Same symptoms as the previous comment - video stops, audio continues, no crash to desktop. Achievements worked fine this time, so things have been quite inconsistent.
steam-632360.log.gz

EDIT2:
and again

EDIT3:
This time I crashed when a steam notification came up - I feel like maybe that's the deal, and it's just happening inconsistently. It would explain why I get it on achievements - specifically on steam notifications popping up for them. I didn't manage to reproduce it when opening a new profile in RoR2 and speed-running for the loadout upgrade, which wouldn't have triggered a steam notification because I've had that achievement in the past.
steam-632360.log.gz

I noticed this time that my mouse disappears entering some windows, including the steam client itself, while the game is frozen but not yet killed, so I'm leaning towards this being part of https://github.com/ValveSoftware/steam-for-linux/issues/9586 and/or https://github.com/ValveSoftware/steam-for-linux/issues/9534

EDIT4:
I've now played quite a few hours with the overlay turned off and it hasn't crashed a single time.

The game refuses to load, it just sits at 0% loading and then eventually I get the terminate this unresponsive app.

No crash or errors, it just never loads the game...

Running perfectly fine on my all-AMD hardware, a 6.6.8 kernel and Proton 8.0-4. Also runs fine on Proton Experimental. Hell, even the r2modman .rpm mod manager runs fine and opens the game with 50 mods. Since 2019, I've only played this on Linux (Arch, Fedora, Nobara) and it's run flawlessly. The only time there is instability is if certain unmaintained mods are loaded.

The game refuses to load, it just sits at 0% loading and then eventually I get the terminate this unresponsive app.

No crash or errors, it just never loads the game...

Check your dmesg while it loads.

After I updated my NixOS setup from kernel 6.7.1 to 6.7.4 the game sits at 0% on the load screen and all the processes are marked in htop as Sleeping. It throws these errors in dmesg:

I do not have it in text form. I can reproduce it if it is required.

When I switch to experimental I get only one page protection fault like:

Once I kill the game on 6.7.4 the driver is in a failed state and corrupts pieces of framebuffer of size of the loading indicator going upwards from the initial location the loading indicator got rendered. I have a photo of this, but it contains a telegram window so I do not feel comfortable uploading it. I can reproduce it if needed. The system proceeds to hang after some time in this state with no further fault logs being put in dmesg.

The system specs are:
CPU: Ryzen 7 5700G
GPU: XFX Radeon 7900 GRE
Motherboard: Asus B550-I Strix
64GB of 3600MHz DDR4 RAM in 2 sticks and 1TB nvme drive.

I thought about bisecting the kernel to see what commits make the driver behave in this way, but so far I haven't had time to do this.

As NixOS handles program installation vastly different than other mainstream distros, how does it work on other distros with that hardware?

As NixOS handles program installation vastly different than other mainstream distros, how does it work on other distros with that hardware?

Considering the issue surfaced after updating to kernel 6.7.4 and works on 6.7.1 I think it's either kernel or mesa regardless of how NixOS installs programs, besides I do not have an another distro which is reliable and can use stable kernel or a disk to install it on so I do not think I can test it on another distro. I could use help tracking the issue down.

@ZaxLofful @keij0 I tested with a rx6600, proton 8.0-5 and kernel 6.7.3 and 6.7.5 and I had no issues launching the game. Both kernels were tested with both mesa 24.0.1 and mesa-git (198719e80e)

@simifor I'll retest it with 6.7.5 when march comes, I'm a tad bit busy now.

@Keij0 when you get around to it, and if the problem is still there, you should add PROTON_LOG=1 %command to the launch parameters of the game, this will create a log file steam-632360.log in your home folder for you to upload

Replying to https://github.com/ValveSoftware/Proton/issues/2476#issuecomment-1951341100

I have same issue as described by @Keij0. I am on arch linux and also use RX 7900 GRE (reference model). I can hear music from the game but screen is stuck on loading at 0%.

Other system specs:

kernel: 6.7.9
gpu: RX 7900 GRE
cpu: ryzen 5800x
motherboard: ROG STRIX B550-I GAMING
disk: SSD 2T

steam-632360.log

Multiplayer appears to be somewhat broken with Proton 9.0 and Experimental:

• With Epic crossplay disabled, a multiplayer lobby cannot be created. The button to change the party privacy from Private doesn't work, and the Start button also doesn't work. The player's username also doesn't appear in the sidebar.
• With Epic crossplay enabled, the above issues are not present, but different ones are. Players that join your lobby don't load their usernames, so in-game, their character's name is used as the name in the status sidebar (e.g. "Commando" or "Huntress") and their name appears as a blank space in the chat bar when picking up items. The person I was playing with was also forcefully disconnected after a few stages, and when attempting to exit to desktop, the game showed a Unity crash screen.

Neither of these problems are present in 8.0-5, so it appears to be a regression.

Still running flawlessly on a Ryzen 5 5600X and 6600XT running Nobara Linux on one drive and Fedora on the other.

The logs and videos provided here are from the same sessions.
System info: https://gist.github.com/serebit/839c3b57b12f1579e7b0e1d48d300f42

Proton 8.0-5

This is with crossplay disabled.

steam-632360.tar.gz

https://github.com/ValveSoftware/Proton/assets/12981608/0f132927-f556-4bf9-b894-7f24172041b0

Proton 9.0 Beta

This is with crossplay disabled.

steam-632360.log

https://github.com/ValveSoftware/Proton/assets/12981608/86b34333-221b-4223-89be-3b7ee403935c

Proton Experimental Bleeding-Edge should let you create lobbies with crossplay disabled.

@Keij0 @jgacas your issue seems to be 7900 GRE specific given that you're the only ones that have reported having it. There was a recent change to mesa that might help you, so if you can, I'd try installing mesa-git and see if that helps with risk of rain.

Proton Experimental Bleeding-Edge should let you create lobbies with crossplay disabled.

@Keij0 @jgacas your issue seems to be 7900 GRE specific given that you're the only ones that have reported having it. There was a recent change to mesa that might help you, so if you can, I'd try installing mesa-git and see if that helps with risk of rain.

I think this MR https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/28195 could solve the issue with 7900 GRE. I just need to find time to test mesa-git. Thanks for the heads up.

I've built a config on kernel 6.8.1 and managed to reproduce the issue. I've also checked the Mesa versions. Both the 6.7.1 and 6.7.4 variation from my previous report ran Mesa 23.1.9. The memory protection faults and soft recoveries are still there, although 6.8.1 will reset the GPU fully eventually and log me out. When I log back in then I see no taskbar in Plasma, after a reboot it's fine.

Attaching a Proton log. Let me know if you want a dmesg as well.

steam-632360.log

The log you provided indicates that you are on mesa 23.3.9. The changes I
mention are recent, if you aren't currently using mesa-git then it is not
unexpected that the crashing continues.

El mar, 19 mar 2024 a la(s) 6:02 p.m., Keij0 @.***)
escribió:

I've built a config on kernel 6.8.1 and managed to reproduce the issue.
I've also checked the Mesa versions. The memory protection faults and soft
recoveries are still there, although 6.8.1 will reset the GPU fully
eventually and log me out. When I log back in then I see no taskbar in
Plasma, after a reboot it's fine.

Attaching a Proton log. Let me know if you want a dmesg as well.

steam-632360.log
https://github.com/ValveSoftware/Proton/files/14657352/steam-632360.log

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/2476#issuecomment-2008208577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EAG2BXV4DCO4OTCG3DYZCYYBAVCNFSM4HCPAH52U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBQHAZDAOBVG43Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @simifor

I can confirm that after I built mesa-git-24.1.0_devel.186662.72e1e6e1206.d41d8cd-1-x86_64 and replaced mesa package with it Risk of Rain starts without issues.

I assume that this fix will be part of the mesa 24.1.0 which will probably be release in May.

@jgacas it should also be part of 24.0.4

I can confirm that on Mesa 24.0.5 and Kernel 6.8.9 I am no longer experiencing the bug that I had reported before. 24.0.5 landed in nixos-unstable recently and I just tested it today. I was able to complete a run on single player.

My friend and I are on EndeavourOS with the latest mesa and kernel as of the date on this message. When either of us tries to host, the other lags out. We've tried proton 9.0-2 and experimental bleeding edge. It's not a great experience. Doesn't happen when either of us host for our windows friends or when we play other games together.

@kisak-valve thank you for moving my issue over. I had a little trouble with the logs as it wasn't saving the file until I made a folder and set the path directly PROTON_LOG_DIR=/home/<myusername>/STEAMLOGS

steam-632360.log

lmk if there's any other debugging data I can provide from my side or version compatibility tests I should run.

@JBAnderson5 the log file should have gone to your /home/user folder by just using PROTON_LOG=1. Anyway I tried to reproduce this but sfx works on my side with every proton version you listed. Have you tried verifying the game files and wiping the game's prefix? were the sound effects working for you at some point in the past?

@simifor The sound effects have not worked in the past (I just got the game ~2 weeks ago). I have verified the game files multiple times. I am noticing that after closing the game and validating the files, I consistently get '3 files failed to validate and will be reacquired'.
I just tried uninstalling and reinstalling the game with no success. How do I wipe the game's prefix?

I'm also on Ubuntu, and have the same issue - music works fine, but there are no sound effects.
I also get 3 or 5 files failing to validate.

I'm also on Ubuntu, and have the same issue - music works fine, but there are no sound effects. I also get 3 or 5 files failing to validate.

The sound effects have not worked in the past (I just got the game ~2 weeks ago). I have verified the game files multiple times. I am noticing that after closing the game and validating the files, I consistently get '3 files failed to validate and will be reacquired'. I just tried uninstalling and reinstalling the game with no success. How do I wipe the game's prefix?

I have been having this problem for ages too and have made some progress on fixing it. Also on ubuntu. It started before the seekers of the storm DLC was released, I don't remember making any changes to the proton compatibility and it started randomly. I used to have the sound effects months prior. Validating game files I also get 3 files failing.

I went into /home/username/snap/steam/common/.local/share/Steam/steamapps/compatdata
Risk of Rain 2's steam ID is 632360 so I renamed the respective folder to "632360.old". I uninstalled, then reinstalled the game. Before launching, I verified the game files and it showed all files present. I also set the compatibility to proton 6.3 as this was the only one that seemed to work for me right off the bat. Game booted with sound effects, both in menu and in game.

I went to switch it back to proton 9, but it seemed to break the sound effects again so I had to redo the whole process. There may be other versions that work after doing this process, but I did not experiment with other versions.

After fixing it again, I noticed that it wasn't switching over to proton 9 that broke the SFX, but the fact that this only works on the first boot of the game after reinstall. Quitting to desktop and relaunching the game without making any changes breaks the SFX again. When verifying integrity of the files after closing the game, it goes back to saying 3 files failed to acquire. Verifying the files does not fix the broken SFX.

I tried it a third time, this time staying on proton 9 and it did not work. I tried it a fourth time, but switched it to proton 6.3 and it worked. Rebooting the game broke the SFX and I gave up for the night.

@IanCoolio @Quicco @JBAnderson5 Could you please retest on Proton 10 Beta -- I couldn't reproduce the issue and I'm hoping that the sound effects are fixed there :)

@alasky17 I tried with proton 10.0-1 Beta. It still didn't work. I tried both validating files and reinstalling the game. It still says that "3 files failed to validate" after exiting the app

@alasky17 Sound effects still do not work. I tried deleting the compatdata folder for the game and reinstalled like I did last time, to no avail. I have tried multiple launch options including LD_PRELOAD="" and gamemoderun %command%, all unsuccessful in fixing the sound.

Validating files after launch shows 3 files failing to validate, here's what I get from the content log. Let me know if there's anything else I can provide to help pinpoint the issue.

[2025-05-04 16:45:48] Validation: 0 chunks corrupt and 1 chunks missing of 1 total in file "Risk of Rain 2_Data\StreamingAssets\ConVarNames.txt" [2025-05-04 16:45:48] Validation: missing file "steam_appid.txt" [2025-05-04 16:45:52] Validation: corrupt chunk 4eca19dd5c98b3fe7b57ece5d05c0b05f55b990c has 53d1fd178bcd3508c1f8dd8845cdcc7f072d141a at offset 0 (918 bytes) [2025-05-04 16:45:52] Validation: 1 chunks corrupt of 1 total in file "Risk of Rain 2_Data\Config\config.cfg" [2025-05-04 16:45:54] Validation: full scan in "/home/ian/snap/steam/common/.local/share/Steam/steamapps/common/Risk of Rain 2" found 3/2110 mismatching files (6.45 KB/2.50 GB) in 5 seconds).

@alasky17 @JBAnderson5 @IanCoolio Hi, sorry for the late reply! I have been sucessful in getting sfx working before trying Porton 10 Beta - What I did was delete Steam from Flatpak, and download the .deb file directly from Steam's website. Ever since then it's been working flawlessly, for around 3 weeks or so. Apart from that, I haven't changed anything else. Don't know if that could be a hint or not

A new game patch was just released V1.3.8 with a relevant bugfix patch note:

• Issue with missing music and sound when many other sounds are playing (primarily on Nintendo Switch) should now be resolved - Many other smaller scale audio issues should also now be resolved across all platforms.

I tried with proton 10 Beta and the sound worked, but the music didn't this time. Still have the same issue where 3 files fail to validate after exiting the app

@Quicco That makes me wonder if the issue is just a long path -- that could also explain why we've struggled to reproduce.

@JBAnderson5 @IanCoolio You could try setting "PROTON_SET_GAME_DRIVE=1 %command%" as a launch option to see if that helps. I suspect the files failing to validate is a red herring but I haven't looked into it here yet.

@Quicco @JBAnderson5 @alasky17 Uninstalling steam and reinstalling from the .deb provided on their website also seemed to fix the issue for me! I wasn't able to uninstall from the software center and had to manually delete everything. I also had to reinstall twice but that may have been user error... ended up reinstalling all the games on my main SSD too, including ror2. Currently using proton 10 beta, haven't tried using the other versions. Subsequent boots of the game still have sound so I'm going to assume this is fixed for me. I'll be sure to report back if anything breaks again.

I am glad it was fixed! I also still suspect that the launch option PROTON_SET_GAME_DRIVE=1 %command% should fix it because flatpak notoriously has extra long paths ... @JBAnderson5 If you are still getting the problem, could you try this? If it fixes the issue, we can set this as the default for the game so that other users don't hit it :)

That's great news, glad to hear you got it working! Hopefully it's one step closer to fixing this issue! :)

Proton 10.0-3 brakes steam input on Risk of rain 2, had to revert to 9.0-4.

Hello @blastermaster77, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)

Here is the log :

steam-632360.log

Important to note that the menus are responsive to the input but not the game.

Also if I disable steam input it works on my desktop.

I found a bug: when you type in Cyrillic in a chat, question marks appear instead of letters, although everything works fine in English. I changed the distribution and Proton, but the problem remains. I hope this helps.

GPU : Geforce MX450 driver version 590.48.01
DISTRO : PrismLinux
KERNEL : 6.18.13-lqx1-3-lqx (64-bit)
USED PROTON : 10.0-4
LOGS:
steam-632360.log

@yobenbobin Does LC_MESSAGES=ru_RU.UTF-8 LC_CTYPE=ru_RU.UTF-8 help?