Proton: Risk of Rain 2 (632360)

Created on 30 Mar 2019  ·  76Comments  ·  Source: ValveSoftware/Proton

Compatibility Report

  • Game: Risk of Rain
  • App Id: 632360

System Information

  • GPU: GTX 1060
  • Driver/LLVM version: NVIDIA 418.56
  • Kernel version: 4.15.0-46-generic
  • Sys-info
  • Proton version: 4.2-1

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

  • Proton Logs (gdrive link)

Game runs flawlessly out of the box, no performance issues (everything on max) or any other major issues. The only problems I have found are the mouse cursor not appearing in Steams overlay (I don't get this problem in other games). Also if you alt-tab out, occasionally when you tab back in the character view will start spinning. This can be easily fixed by alt-tabbing back out and in again.

Game compatibility - Unofficial Regression

Most helpful comment

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

All 76 comments

Hello @KorinFlakes, please opt into Steam's beta client and retest the overlay's behavior.

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

Hello @Pobega, please retest with mesa 19.0. My hunch is that the game wants to use VK_EXT_transform_feedback and that was merged shortly before 19.0.0 for mesa/anv.

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

Risk of Rain 2 (632360) - Game shutdown on boot.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2538.
@NewfolderGames posted on 2019-04-14T13:51:46:

Compatibility Report

  • Name of the game with compatibility issues: Risk of Rain 2
  • Steam AppID of the game: 632360

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

steam-632360.log

Symptoms

When game is installed in a folder that contains non-english character, game starts up with blank black screen and shutdowns few seconds after. (Installing on other folder solved problem)
Other games (Rimworld, Prison Architect) doesn't have same problem.

Reproduction

  1. Installed Risk of Rain 2 in primary library(/home/hdd/게임/Steam).
  2. Started game.

Risk of rain 2 no longer starts with 4.2.3

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2558.
@AlexandreBonneau posted on 2019-04-19T07:11:24:

Compatibility Report

  • Name of the game with compatibility issues: Risk of rain 2
  • Steam AppID of the game: 632360

System Information

  • GPU: Vega 64
  • Driver/LLVM version: Mesa 18.3.4
  • Kernel version: 4.19.0-4-amd64
  • Link to full system information report as Gist:
  • Proton version: 4.2.3

I confirm:

  • [x] that I haven't found an existing compatibility report for this game and that version of proton
  • [x] that I have checked whether there are updates for my system available.

Symptoms

When clicking 'Play', Steam briefly shows that you are running the game, but no windows are shown and you are immediately back to the 'non-playing' state.

Reproduction

Using Proton 4.2.3, then click Play.

Note: RoR2 works out of the box with 4.2.2 and 3.16-9 Beta

The system information.
The steam-632360.log file.


@KorinFlakes commented on 2019-04-19T08:36:28:

Still working for me on 4.2-3, although I'm on Nvidia/Intel.

  • GPU: GTX 1060 (6gb)
  • Driver/LLVM version: Nvidia 418.43
  • Kernel version: 4.19.32-1-MANJARO
  • Link to full system information report as Gist: System Info
  • Proton version: 4.2.3
  • Log file: RoR2-Log

@HonkingGoose commented on 2019-04-19T10:04:48:

Hi, we only use one report per unofficially supported game. This game is tracked at: https://github.com/ValveSoftware/Proton/issues/2476

@kisak-valve this is a duplicate.


@AlexandreBonneau commented on 2019-04-19T10:40:51:

ah, sorry, I was not sure about the wording there


@aeikum commented on 2019-04-19T13:22:02:

/mnt/espace3/SteamLibrary/steamapps/common/Proton 4.2/dist/bin/wineserver: error while loading shared libraries: libwine.so.1: wrong ELF class: ELFCLASS32

This is worrying. Do any games work in 4.2-3 for you?


@AlexandreBonneau commented on 2019-04-19T19:37:24:

Some yes ;

Works (as usual):
Castle crashers
DOOM 2016

Does not work anymore:
RoR2
Mortal Kombat Komplete Edition


@Skiski commented on 2019-04-20T07:43:09:

I've tried and I can play RoR2 with Proton 4.2-3.
I sometimes have the problem of games not launching, just quitting without showing anything, but usually, if I try again or restart Steam, it works.


@AlexandreBonneau commented on 2019-04-20T09:48:35:

@Skiski can you be more specific? Are you using an AMD Vega 64 card too? Which distro? Mesa version? etc.

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.

Game has stopped working for me as of today. Tested with both Proton 4.2-3 and 3.16-9-Beta. It launches, then loads a unity update window then crashes and closes.

Ubuntu 18.04
Intel i7-5930K
AMD 290X
oibaf ppa

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)

My proton logs

Update: it works again.

Risk of Rain 2 multiplayer broken on latest proton (4.8-8)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2841.
@A-UNDERSCORE-D posted on 2019-06-27T18:30:02:

Compatibility Report

  • Name of the game with compatibility issues: Risk Of Rain 2
  • Steam AppID of the game: 632360

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.


steam-632360.log

Symptoms

Risk of Rain 2's multiplayer system does not appear to work

Reproduction

  1. Open RoR2
  2. Hit multiplayer
  3. notice the greyed out options

Hello @A-UNDERSCORE-D, this sounds similar to the networking trouble mentioned at https://github.com/ValveSoftware/Proton/issues/2629#issuecomment-506098394.

You can test Proton 4.2-7 which has been made temporarily available while that issue is being investigated by going to Steam -> Library -> Tools, right click on Proton 4.2 and select properties, then select 4.2-7 from the dropdown on the Betas tab.

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

Thanks for testing, Proton 4.2-9, which just shipped should have resolved your issue.

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.

Hello @serebit, @dmarcuse, sounds like you've encountered #3316.

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

When running steam through console, launching the game gives this output:

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.

Hello @pasimko, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box. Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

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.

Hello @TheGreatestJannet, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the crash, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

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?

Hello @TheGreatestJannet, most Proton logs compress well. Can you try throwing it in an archive and retry?

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.

Hello @l0llygag, optirun gets OpenGL to run on the nVidia card, but not Vulkan. You may want to try out primus_vk and make sure you have vulkan-intel and lib32-vulkan-intel installed.

These are the lines of interest from the log:

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

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.

Risk of Rain 2 hangs launching indefinitely

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3595.
@DoubleRHR posted on 2020-03-03T03:14:15:

Compatibility Report

  • Name of the game with compatibility issues: Risk of Rain 2
  • Steam AppID of the game: 632360

System Information

  • GPU: Quadro P500
  • Driver/LLVM version: Nvidia 430.50
  • Kernel version: 5.3.0-40-generic
  • Proton version: 5.0-3, 4.2-9
    Gist here
    Screenshot from 2020-02-28 20-47-55

Hi, recently my game has stopped launching at all. Usually I force it to use Proton 4.2-9, but that has just stopped working. It does not work with other versions of proton, and only started acting up once proton 5 was released.
Occasionally a unity crash screen (attached) pops up. When Proton 4.11-2 was released I had the same issue, but fixed it by using 4.2-9 instead. The application never stops displaying as "currently running" unless I manually kill it--the game hangs indefinitely. I have verified the file integrity of the game, and have cleared the download cache. I have also tried restarting my computer, logging out of steam, and uninstalling/reinstalling the app.


@wantija commented on 2020-03-03T08:23:55:

I had this issue recently, had to re-install mesa, lib32-mesa, mesa-vulkan ect but it worked fine after that. I have an RX 580, but try re-installing/updating your Nvidia drivers? No idea what caused it.

Hello @DoubleRHR, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

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

Compatibility Report

Name of the game with compatibility issues: Risk of Rain 2
Steam AppID of the game: 632360

System Information

GPU: Radeon RX 580
Driver/LLVM version: amdgpu-pro 18.40-697810
Kernel version: 4.15.0-91-generic
Proton version: 5.0-5, 4.11-13

I've not been able to get this game to run under any version of Proton. Steam says that it successfully launches, but the game itself never seems to actually launch.

proton_log output:
steam-632360.log

@khandnalie are your vulkan drivers correctly installed? Do other games work?

@thunder1410 I just updated them and re-tested on every version of proton I have available, and nothing. It just stops before the screen is even visible. Other games works just fine. Overwatch, Bioshock Infinite, Grim Dawn are some of the ones I've plaid in just the past couple days without issue.

@khandnalie This is a bit of a long shot, but you could try unplugging anything unnecessary (extra monitor, controllers, etc) temporarily to see if one of those is tripping a rare bug?

@alasky17 I don't have anything extra plugged in. Single monitor, no controller. just mouse and keyboard. I'm using pretty much stock standard ubuntu too, so idk what it could be.

Got it runnning, had to completely uninstall then reinstall my graphics drivers

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

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.

Risk of Rain 2 doesn't run with Proton

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3760.
@Primo909 posted on 2020-04-13T10:08:58:

Compatibility Report

  • Name of the game with compatibility issues: Risk of Rain 2
  • Steam AppID of the game: 632360

System Information

  • GPU: GTX 980m
  • Driver/LLVM version: nvidia 440.64
  • Kernel version: Ubuntu 5.3.0-7642.34~1584408018~19.10~21df4b1-generic 5.3.18
  • Link to full system information report as Gist:
    Systeminfo.log

  • Proton version: 5.0-5

I confirm:

  • [+] that I haven't found an existing compatibility report for this game.
  • [+ ] that I have checked whether there are updates for my system available.

steam-632360.log

Symptoms

I launch the game the Steam says initializing and install VCredist then the game "launches" but the game doesn't open. I can only close it by force exiting steam

Reproduction

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.

Just in case this can help somebody else,

I had an issue running ROR2 on Proton 5.0-x after the March 31 update (artifacts update)

I'm using Ubuntu with Kisak's PPA (God bless Kisak)

ROR2 would crash with Proton 5.0-x but work with Proton 4.11-x, it turned out that I had some old leftover vulkan icd files on /etc/vulkan/icd.d

I removed the old icd files and reinstalled Kisak's mesa, specifically:

apt install --reinstall mesa-vulkan-drivers libgl1-mesa-dri

And voila! all problems gone on ROR2 and Proton 5.0-x

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?

Hello, I have some issues with Risk of Rain 2.

When I install it for the first time, it runs perfectly at the beginning. But after some play time (20-30 minutes), it starts having temporary fps issue (from 60fps to 30fps for 5-10 seconds), and as time goes on, this fps issue happens more often and is harsher (down to 5fps and longer). It happens also on early levels or when there is no enemy, I also checked my CPU/RAM usage, but nothing was happening.

When I close the game and try to reopen it, it works, but if I try adding mods, it doesn't apply them, it continues running vanilla.

When I close steam and reopen it, the game does not open anymore (it doesn't open any window and the button on steam goes back to the Play state), even if I reinstall the game.

It seems that if I uninstall the game, reboot my computer and install it again, it goes back to it runs perfectly at the beginning, but after some play time, it will start lagging again.

__System information:__ https://gist.github.com/SpartanPlume/875b91b90ae0df6f826a65c863aacea7
__The logs when the game doesn't launch:__ steam-632360.log
__Proton version:__ Proton 5.0-9, I tried using other Proton versions just in case, but it does not change anything.

The last time I remember being able to play without issue is in December (didn't play since then).

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.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

leifmetcalf picture leifmetcalf  ·  3Comments

Elkasitu picture Elkasitu  ·  3Comments

prototype99 picture prototype99  ·  3Comments

kforney picture kforney  ·  3Comments

shanefagan picture shanefagan  ·  3Comments