New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Risen (40300) #554
Comments
Confirmed. Works great here too. No issues. |
Confirmed. Distro: Linux Mint 19 Tara |
I don't know if it's my setup - Arch Linux, kernel 4.18.5, Proton beta - but while the game runs perfectly, saves are lost between sessions. It seems that they're written to |
For me, Risen does not start. Distribution: openSUSE Tumbleweed Full specs: https://gist.github.com/buschmann23/f0040553d4bc4bdeb567778bd52f7946 |
Works fine... |
There's a (fshack related?) regression in Proton experimental, changing resolution ends up with a too small game when decreasing and too big game when increasing the resolution. Doesn't happen on stable Proton. |
@DadSchoorse I'm seeing very similar behavior on 6.3-8 as experimental-6.3-20220119. Sometimes it gets the resolution right, and sometimes its too big or too small. If you have specific resolution change steps that are continually problematic on experimental and never problematic on 6.3-8, feel free to leave more details and I can take another look :) |
Okay, I did some more tests now: I changed the resolution from 1920x1080 (my display's native res) to 1600x900 and back to 1920x1080. So you are right that it's not working 100% correctly on 6.3-8, but experimental is always broken for me. |
The game has to be played with Proton 5.0-10 (in my case), and both "Original game from 2009" and "None" version of the game ("Betas" tab) work the same. The game used to work flawlessly (don't remember which Proton I was using) in May/June of 2022, and there was an update this January (2023), which apparently broke something. Shut up material (as in, I talk too much, more detail etc.): I played the game flawlessly a year ago, exactly in May/June 2022, and the game worked flawlessly. I do not remember which Proton version I was using back then. Additional thing is that Risen 1 got an update this year, which might've broken a few (million) things (just like it did with Gothic to me, where the game ran well, but I got more crashes than ever, only because of THQ Nordic's patch in like 2020 or 2021). |
Hello @4164696f73, please add |
https://gist.github.com/4164696f73/b053542782d8940e8bb3b261ae0fa51d Gistfile1 = System Info Also additional info which I just noticed (by accident): I disabled the fullscreen (again, by accident) and I set it back again (with my window manager) while the videos/intros were loading, and, surprisingly, the game did launch, but the game was tiny with everything else being black. Check this screenshot. This happened on Proton Experimental just now when I was taking the Proton log. Also, it taxes the CPU when you do this (30+% CPU usage vs. barely 10% on Proton5). And I can reproduce it: when the game is launching, it'll create a black screen and your mouse is still visible, during this time you have the opportunity to disable and enable fullscreen with your WM, and the game will launch in a tiny window, fully functional. However, without doing it, it'll hang. From what I saw in the log, it's something pid related? I checked it on Dwm (suckless' Window Manager) and AwesomeWM (logs are from Dwm), and in both cases the same issue (although, I did not toy with the fullscreen in Awesome because I have a few important windows opened that I can not close even for 10 mins currently) - game launches until the videos pop, and then decides it's time for a break. |
Thanks, looking over the details, your system is configured to use AMDVLK. As a quick test, can you check how the game behaves with mesa/RADV? |
I'd love to do that, but I don't know how to do that. I'm not that technical, still learning Linux in general. Wouldn't really want to risk anything if there's some files I have to edit, but if it's just installing something (Mesa/RADV), I'm in. |
@4164696f73 I was able to confirm that you found a regression of some sort - thank you for reporting! In the meantime while we work on fixing this, feel free to use Proton 5.0 or PROTON_USE_WINED3D=1 %command% as a launch option in order to avoid the regression. I would still suggest switching to mesa/radv as that generally has better behavior -- unfortunately, I'm not an expert on how to switch if you are using AMDVLK. |
So, I searched a little, and according to Gentoo and Arch wiki, AMDVLK is enforced by default, but it can be switched with an environment variable - |
Works fine on Proton Beta. Gallium nine yields much better performance.
The text was updated successfully, but these errors were encountered: