Open KorinFlakes opened 5 years ago
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:
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:
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 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
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:
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
Hello @Hnaguski, in your log, it looks like xaudio2_9/fna failed to initialize the audio device for some reason, then the game fell over.
ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
INFO: OpenAudioDevice failed: ALSA: Couldn't open audio device: No such file or directory
INFO: Assertion failed: 0 && "Failed to open audio device!"
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
======================
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.
Hello @wantija, 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.)
@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
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.
Hello @kkartaltepe, it may be worthwhile to report any crashes you had while the game was rendering with mesa/ANV to the relevant video driver devs if it hasn't been already.
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.
@stharward So did you have controllers working with other proton games?
Is anyone facing performance issues with the game lately? I'm not sure if this is related to the recent updates and DLC of the game or Proton, but in my system, the game would sometimes have poor performance over time, after several stages. The performance issues can also happen in the main menu or when you launch the game.
Restarting the game fixes it, but I'm wondering if there's another permanent solution since it can be annoying to restart the game just to fix that poor performance.
People seem to have similar issues reported in ProtonDB, but I'm not sure. Here are the launch commands I'm using:
__GL_THREADED_OPTIMIZATIONS=1 gamemoderun %command%
Disabling nor enabling these commands did not solve the issue. Any help would be appreciated. I'm on Arch Linux with Nvidia GPU
@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: @.***>
Hello @woalk, friendly reminder that we're using one issue report per unofficially supported game title. This is the right place for all feedback related to running Risk of Rain 2 with Proton.
@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.
Compatibility Report
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.
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.