search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.46k stars 1.07k forks source link

The Riftbreaker (demo/Prologue) (1293860 1317860) #4405

Open zaggynl opened 3 years ago

zaggynl commented 3 years ago

Compatibility Report

System Information

I confirm:

attached zip, extracted log file is 443MB [steam-1317860.zip](https://github.com/ValveSoftware/Proton/files/5573107/steam-1317860.zip) [steam-1293860.7z.001.zip](https://github.com/ValveSoftware/Proton/files/5573173/steam-1293860.7z.001.zip) [steam-1293860.7z.002.zip](https://github.com/ValveSoftware/Proton/files/5573174/steam-1293860.7z.002.zip) [steam-1293860.7z.003.zip](https://github.com/ValveSoftware/Proton/files/5573176/steam-1293860.7z.003.zip) (is a multipart 7z file, remove the .zip part, had to add bogus extension otherwise couldn't upload to this issue) ## Symptoms

Game crashes after ~5m of playtime More reports here: https://www.protondb.com/app/1293860

Reproduction

Start game, start prologue, games freezes and crashes after about 5 minutes of playtime.

Comment: the log file has appid 1317860, in steam the URL shows 1293860 for the Prologue, full game ID in Steam URL is: 780310 I've tried both the demo and the Prologue, they behave the same.

zaggynl commented 3 years ago

"eventfd: Too many open files" seems to be key

Workaround: start the game with launch options: PROTON_NO_ESYNC=1 %command%

Edit: was able to finish the demo without any issue with above workaround.

kisak-valve commented 3 years ago

Hello @zaggynl, please run ulimit -Hn and verify it gives you a high value and not 4096.

zaggynl commented 3 years ago

~> ulimit -Hn 524288

kisak-valve commented 3 years ago

Looking at the 1317860 log, it looks like the game hits an access violation (c0000005) around 401467.233, which leads to terminating with uncaught foreign exception.

PraetorianSC4 commented 3 years ago

I'm getting a ERROR: unable to load "riftbreaker_dll_win_Release.dll" error on my end for this game. I've installed vcrun2019 and still experiencing it. Any thoughts on how to deal with this?

coreybruce commented 3 years ago

I'm getting a ERROR: unable to load "riftbreaker_dll_win_Release.dll" error on my end for this game. I've installed vcrun2019 and still experiencing it. Any thoughts on how to deal with this?

Getting the same issue, has anyone else reported this or got a fix?

coreybruce commented 3 years ago

I'm getting a ERROR: unable to load "riftbreaker_dll_win_Release.dll" error on my end for this game. I've installed vcrun2019 and still experiencing it. Any thoughts on how to deal with this?

I made a issue post for the issue :+1:

https://github.com/ValveSoftware/Proton/issues/5061

The Riftbreaker: Prologue fails to run.

Issue transferred from https://github.com/ValveSoftware/Proton/issues/5061. @coreybruce posted on 2021-08-11T06:15:32:

Compatibility Report

System Information

System information: https://gist.github.com/coreybruce/dcd2bec911594c9212d351ac2e7a3f98

I confirm:

Game log: https://gist.github.com/coreybruce/d4f30393cd9923f5cec5e0b5c5d69825#file-steam-1293860-log

Symptoms

Launches the game and it just comes up with a error box

"Unable to load game dll!

ERROR: unable to load: 'riftbreaker_dll_win_Release.dll'"

Than once you click ok the game stops.

Reproduction

Launch game using proton.

kisak-valve commented 3 years ago

Hello @coreybruce, err:module:import_dll Library api-ms-win-core-psm-appnotify-l1-1-0.dll (which is needed by L"Z:\\mnt\\Game Drive\\Steam\\Steamapps\\common\\The Riftbreaker Prologue\\bin\\riftbreaker_dll_win_Release.dll") not found looks like a line of interest from your log.

coreybruce commented 3 years ago

Hello @coreybruce, err:module:import_dll Library api-ms-win-core-psm-appnotify-l1-1-0.dll (which is needed by L"Z:\\mnt\\Game Drive\\Steam\\Steamapps\\common\\The Riftbreaker Prologue\\bin\\riftbreaker_dll_win_Release.dll") not found looks like a line of interest from your log.

I hope this helps you guys out! I'm always happy to report bugs or issues to help improve proton. 😎👌

ghost commented 3 years ago

I made a patch on top of experimental adding the dll and the game is working now.

RazielleS commented 3 years ago

The patch works like a charm. Thank you! Now I have another issue: The game just hangs randomly. Sometimes I can play 15-30 minutes, sometimes it hangs after a few minutes. I noticed that it occurs more in the later game, especially when a lot of enemies with fire and poison effects are around. It also crashed in the GPU benchmark once, but not always.

When starting steam through the console, I don't get any further logs when the game hangs. The screen just freezes but the sound continues. Any hints about how I can get a proper log out of this?

Edit: I already use PROTON_NO_ESYNC=1

Patola commented 3 years ago

A build with this patch from @EsdrasTarsis (and many others) has been made available at https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd

coreybruce commented 3 years ago

How do you use the patch?

Patola commented 3 years ago

@coreybruce you cd to the wine directory of Proton git then do git am /path/to/file.patch. Then you cd .. to the Proton directory and compile the build with make redist. Or, you can download my build and use it as per its instructions.

coreybruce commented 3 years ago

Looks like Proton-6.15-GE-1 now works so I wonder if it's got the patch or did something else to fix it like update something. @Patola I will also test that out and let you know how it goes tho.

Patola commented 3 years ago

Proton-GE got the patch too. I just made my own build because Proton-GE doesn't play well with VR (other games, in that case)

coreybruce commented 3 years ago

Ahh right I see, that's interesting. How is VR on Linux? Alsos to add the game works but it can freeze up so it's not perfect at least from my testing on a Nvidia card.

Patola commented 3 years ago

@coreybruce VR on linux: https://boilingsteam.com/the-state-of-virtual-reality-on-linux/ -- I wrote it a time ago but it largely holds, will probably write a piece or two soon -- and about the game freezing, try lowering the graphical details, specially shadows and effects. I would even suggest to first try it on "low", then if it works try activating stuff in the options.

ExpandingMan commented 3 years ago

Not sure if I should open an issue for this, but I tried the full release today and and I still get

ERROR: unable to load: `riftbreaker_dll_win_Release.dll`

in a windows dialogue box. The above makes it seem like this should be fixed, and I am on proton experimental, but I can't seem to get around this. I took a look and that dll is indeed present in the games bin directory. Any work arounds?

jwtrhs commented 3 years ago

Using the latest GloriousEggroll proton version Proton-6.19-GE-2 has worked for me.

I was getting the DLL errors as above on the full release with Proton 6.3 and Experimental, couldn't start the game at all. But have now loaded into the first mission and everything appears to be running smoothly.

Edit: Spoke too soon. Game boots up but crashes after a few minutes with no error popup.

RazielleS commented 3 years ago

I've got a proton error log from said hang / crash, but I can't really see what is happening. Maybe someone understands more of it or can tell me what parameters I could add for a more detailed log? (command used: PROTON_LOG=1 PROTON_NO_ESYNC=1 %command%)

steam-780310.log

kitliasteele commented 3 years ago

I've been working on figuring things out, and attempting to run FidelityFX Super Resolution on various settings to see if anything would happen. Turned off RGB Hardware Effects as well, and still encountering crashes at very random intervals. One time had over 30 minutes before crash, one within minutes. Came across an interesting FATAL UNHANDLED EXCEPTION in this crash, and I've put it in the log. ESYNC is also off

Append: I'm noticing that save states can take a while to do, last run got stuck and couldn't save. Game will lock up a bit during saving.

steam-780310.log

ExpandingMan commented 3 years ago

Confirmed that GloriousEggroll works fine for me. Some slight graphical issues on directx12, haven't noticed any issues at all on directx11 in about 90 minutes of gameplay.

folknor commented 3 years ago

GE does not work fine for me, it crashes after a seemingly random delay of 1-30 minutes. This, however, does work for me: https://github.com/Patola/wine/releases/tag/protola_6.3-6-6_rbespbgvwd - played for 4+ hours today using that and DX11 + fullscreen. X11+nvidia.

cryzed commented 3 years ago

I unfortunately still get the same crashes, even when using protola-6.3-6-6-rbespbgvwd and the same settings, using DX11, Fullscreen, X11 and NVIDIA. I am testing using the Demo found in the Steam store.

folknor commented 3 years ago

Forgot to mention I also use PROTON_NO_ESYNC=1 %command%, and also when I opened the config tool now to check it's set to DX12 for some reason. Perhaps that's what I ran it with, or the config tool changed reverted it on its own.

cryzed commented 3 years ago

I changed my settings back to Direct X11 and Borderless WIndow, along with that environment variable PROTON_NO_ESYNC=1 and that seems to work (still using protola-6.3-6-6-rbespbgvwd) -- no crash so far. I'm pretty sure it's just related to that environment variable.

ExpandingMan commented 3 years ago

I have a little over 3 hours in it now and have been experiencing intermittent crashes on GloriousEggroll. I've tried with PROTON_NO_ESYNC=1 which might improve it? Crashes are rare enough that I can't tell for sure. If I didn't have trouble getting this game running in the first place I'd suspect this is a non-proton issue as once I get games working I mostly haven't found them crashing.

kitliasteele commented 3 years ago

I have a little over 3 hours in it now and have been experiencing intermittent crashes on GloriousEggroll. I've tried with PROTON_NO_ESYNC=1 which might improve it? Crashes are rare enough that I can't tell for sure. If I didn't have trouble getting this game running in the first place I'd suspect this is a non-proton issue as once I get games working I mostly haven't found them crashing.

I joined in the Discord server and been monitoring bug reports. They seem to have more verbose crashing happening on the Windows builds. So I can only assume that the exceptions aren't showing up as dialogue boxes for Proton users. For Proton, it will just freeze and lock up instead of crashing to error.

I actually had a crash after a couple hours of playing myself, but they are indeed lining up with similar issues on the Windows builds according to the reports.

ExpandingMan commented 3 years ago

That makes sense. I've been testing a lot of games, this is literally the only one that's been crashing. One game (Medieval Dynasty) has abysmal performance, a buhc of games have obnoxious windowing issues and a couple don't work, but none (except this) that crash.

ExpandingMan commented 3 years ago

The game works on whatever version of proton experimental dropped today. Haven't had a chance to play it very much so I don't know about crashes. Interestingly, directx12 is working fine without any of the weird graphical issues I had seen before.

McMarius11 commented 3 years ago

i played the latest build with DX12, DX11 has a black minimap.

Protola 6.3-6-6 rbespbgvwd ( runs 50 minutes then it crashes) Proton experimental (runs 5 minutes till crash) Proton-GE (runs 13 minutes till crash)

OS: Manjaro Linux KERNEL: 5.10.72-1-MANJARO CPU: Intel Core i5-7600K @ 3.80GHz GPU: NVIDIA NVIDIA GeForce GTX 1070 GPU DRIVER: NVIDIA 470.74 RAM: 24 GB

ExpandingMan commented 3 years ago

I have another 3 or 4 hours in this between last night and tonight. All with directx 12, have not experienced any issues. Note there was also a game patch yesterday, I wouldn't be surprised if it fixed some non-proton related issue that eliminated the crashes.

coreybruce commented 3 years ago

I was able to finish the demo but I did have some crashes and at the time frame drops but this was maybe a month or so ago when I played it.

zaggynl commented 3 years ago

Had crash to desktop before PROTON_NO_ESYNC=1. Now using launch options: PROTON_NO_ESYNC=1 %command% with Proton-6.19-GE-2 Played several evenings, had graphical bugs before last Riftbreaker (full game) update, those have not returned. Edit: Crashes to desktop again, trying again now with experimental without any commandline options, seems ok Edit2: no more crashes with current Proton Experimental build, did have graphical distortion on loading the Uranium world, went away after I quit and restart Riftbreaker, may or may not be related to my GPU heating up quite a bit during gameplay.

ExpandingMan commented 2 years ago

This game has been the 2nd most persistently problematic game I've been experimenting with second only to "Medieval Dynasty". Still getting crashes (though when it runs, it runs fine).

See the crash log in this gist, hope it helps!