-
Notifications
You must be signed in to change notification settings - Fork 1k
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
DARK SOULS III (374320), Nier: Automata (524220), Sekiro: Shadows Die Twice (814380) crash with Proton 4.11 #2929
Comments
for me crashing in proton 4.2 and 3.16 nothing new |
I could play with 4.2-9. |
Working perfectly fine for me on 4-11, I actually just finished the entire game (DLC included) at max settings. Got through the entire thing without a single performance hitch or crash, multiplayer works fine as well and I actually did the entire thing in coop. Should be noted that I'm using the 5.0 kernel but not the valve-experimental one, so no f-sync I suppose(?). GTX 1070 - Nvidia 430.40. Also why are there 6 issue threads for Dark Souls 3? Difficult to keep track of things. |
Sorry. and thank you your notification. more description. |
I fond new fact. |
@aeikum I have reverts commit this and fix this problem. |
@yuiiio Thanks for looking into this. Can you attach a log here of regular 4.11-3, and add |
Thanks ! |
I experience crashes too since 4.11.5. It worked fine with early 4.11.x versions(like 4.11.3). It runs really badly for me: doitsujin/dxvk#1181 |
looks not same problem. |
It doesn't work for me on proton-4.11.6 at all. PROTON_NO_FSYNC=1 doesn't do anything. |
my xrandr output
|
Interesting! |
This affect me still Proton 4.11-9. |
xrandr --listprovides
|
NieR:Automata is crashing for me in Proton 4.11-10 when I try try to leave the settings screen or load any of my saves. They are not corrupted as they open just fine with Proton 3.7-8, 3.16-9 and 4.2-9. I didn't get it in 4.11-9 and below, but starting with 4.11-10 the game crashes with similar error to @yuiiio's log file. I have attached my own NieR:Automata Proton crash log. Here, I ran the game with 4.21-GE-2, but the same thing happens in Proton 4.11-10. I've tried moving the game across drives and I still get the error - even on my main boot drive. If I switch to Proton 4.2-9 (the lowest version I can use at the moment, as I reinstalled) then the game works fine. The log details an interesting error to do with a page fault: I tried deleting the shader cache folder, deleting the game's Proton prefix, and even reinstalling the game. No success, unsurprisingly as this seems to be an issue with the newer versions of Proton. Hopefully someone can come along and check the logs and give us an idea of what's wrong! ^_^ OS: Arch Linux w/ KDE Plasma Log: steam-524220.log |
Can confirm the crash still occurs with Proton 4.11-11 |
@sonic2kk Have you tried disabling ACO? I'm just curious if that would change the behavior at all. |
@alasky17 I have, it made no difference sadly. I've tried different versions of Proton, and the latest known working version for me was 4.11-8. Proton 4.11-9 may have worked but I don't recall. I know that Proton 4.11-10 and up don't work. A patch must have been added somewhere in the Proton versions that broke it. Versions starting with Proton 3.7-8 (the default version Valve recommends for NieR:Automata) up to Proton 4.11-8 all work with and without ACO, as I've tested on every release starting from then. The late 3.16-9, released while 4.2 was in circulation I believe, also works with and without ACO. I tested Proton-tkg 5 as well (which I believe is based on WINE-Staging by default and I assume the "5" means WINE 5.0), and while it gives different results it ultimately gives the same vein of error. It softlocks the game again when trying to leave the settings menu and when trying to load a save/create a new save. However, the game's music still plays. The error I got when testing with Proton-tkg 5 was pretty much the same as with Proton 4.11-10, 4.11-11 and Proton-4.21-GE-2: If needed, I can provide additional logs. I should also mention that I've never ran into this error before with any other games in my library. I've tested around 150 games with Proton across my old and new PC hardware, with only 2 not working due to codec issues and 1 not working because of anti-cheat. The rest all worked fine, and did not produce this error. Suffice to say that for me only NieR:Automata is having this fault issue. |
@sonic2kk Thank you for trying that and for the details! I will keep thinking about this. |
Dark souls 3 is also crashing for me a lot: dump. |
And I also experienced another kind of crash: #3358 |
You can revert commits to know if it is the same or another problem. |
Crash is still present with all of the same symptoms in Proton 4.11-12. The updated DXVK has made no difference |
The same crash is also still present with Proton 5.0-1. All the symptoms are the exact same,
I compared two different log files from Proton 4.2-9 and Proton 5.0-1, and the only notable difference I could find was that Proton 5.0-1 was loading the PE overrides that were added in Proton 4.11 - However, I have definitely ran NieR:Automata with Proton 4.11, at least up to Proton 4.11-8. I've tested a number of other game since I initially commented on this issue and haven't ran into this problem with any other games. I have since acquired DARK SOULS III which is reportedly causing issue but have not gotten around to installing or testing it. I'll attach both log files for Proton 5.0-1 and Proton 4.2-9. I have not tried going back to versions <= Proton 4.11-8, the latest version I have that I can confirm works is Proton 4.2-9. The only other time I've read someone having a similar issue was someone having issues with "Yakuza Kiwami (834530)" in the ProtonDB server. This was never resolved and was talked about almost a year ago. I did some investigating and found this issue on the RedHat issue tracker from 2008. Someone suggested it was an issue with map addresses. I didn't make the file in OS: Arch Linux w/ KDE Plasma |
As expected, NieR:Automata still crashes with Proton 5.0-2 with all of the same symptoms. I'm also currently running on Mesa 19.3.4. I also tested GloriousEggroll's Proton-GE-5.1 release, with no luck. Again, crashes in the same way. Proton 4.2-9 still works, but it is perplexing that only a handful of people are reporting this issue. |
|
@yuiiio |
This fix is now a part of TkGlitch's Proton-tkg build, which can be found on their PKGBUILDS repo. Building Proton-tkg from source should now allow you to play the three games listed here. If you follow the instructions on the repo you'll have it built in no time. You don't need to add a custom patch for the game to work anymore on that build of Proton! Looking at the code they added, it's part of a hacks patchset and explicitly mentions these three games. I can only personally verify NieR:Automata but I trust that it works. Maybe someone smarter than me can explain why exactly these games broke with later versions of Proton, and why this fix works. But, that's not too terribly important. What matters is that now these games work! |
Hello. Thanks for your patience on this issue. This should be fixed now in the Proton 5.13-1 release. |
thanks! |
@aeikum Just tested with the latest 5.13-1 downloaded through Steam. NieR:Automata works for me out of the box with that version. Worth the wait! |
Nier:Automata gives me white screen and frezzes OS, however adding # Use OpenGL-based wined3d instead of Vulkan-based DXVK for d3d11, d3d10, and d3d9.
"PROTON_USE_WINED3D": "1", into |
Compatibility Report
System Information
steam-374320.log
I confirm:
Symptoms
crash when cursor hover and show "graphics" tab in system settings.
no effects PROTON_NO_FSYNC=1.
The text was updated successfully, but these errors were encountered: