-
Notifications
You must be signed in to change notification settings - Fork 161
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
Doom 2016 crashes after a while #175
Comments
update: 2020.Q3.2 still behaves exactly the same |
It is a regression caused by [PR650] Rationalized user data usage |
seems like with 2020.Q3.3 this is fixed? I've played for roughly 30min and no crashes, so I'm going to close this issue now |
Sorry that was wrong, I accidentally deleted the amdvlk icd file so I just started doom with radv instead of amdvlk. This issue is obviously still present with 2020.Q3.3 |
Fixed in llpc dev branch with GPUOpen-Drivers/llpc@44a8e50 |
GPUOpen-Drivers/llpc@44a8e50 will be promoted to master branch at v-2020.Q3.5( not v-2020.Q3.4) |
@zeratax issue fixed in v-2020.Q3.5 please verify that, thanks! |
yay it does work! and also 10% faster than radv so that is also super cool |
Playing Doom 2016 with RADV works perfectly fine and even amdvlk seems to work great with improved performance until you reach a certain point in the game when it suddenly crashes. most of the time when starting a new campaign it happens when I pick up the helmet.
When the game crashes the music still continues and I can see my mouse, but I can't alt-tab and after a while the frozen image gets replaced by something like this:
after a while I press the power button which then results in this:
I sometimes recover the session like this and the display-manager/x-server restarts.
I tried starting from different saves I had and with different resolutions and settings, but it always crashes a few minutes in.
Also maybe interesting, but Doom eternal doesn't seem to crash, but I've only yet tried 30minutes.
I can't use renderdoc when the game crashes, but I created a capture before it crashes if that's from any interest:
RenderDoc.tar.gz
here is my steam proton log and vulkaninfo output:
vulkaninfo and protonlog.tar.gz
I have mangohud installed, which might be reported in these logs, but deinstalling it doesn't seem to change anything.
This part from the log of my display-manager around it restarting also seems interesting:
display-manager.log
Edit: wayland also seems to behave the same
The text was updated successfully, but these errors were encountered: