Hung graphics drivers

[kohlrak]

It's taken a bit of testing, but I was finally able to narrow down a setting that let me play the game, but it's horrible. I'm hoping that with this thread, maybe someone can find a solution that doesn't involve blaming Capcom (which would be productive, but my hopes aren't high because I'm of the opinion that it's a bug in Capcom's shader code). I'm aware there's at least a few others with the unresponsive GPU issue, but I cannot be certain it still has the same cause. So, with that out of the way, what i've noticed:

-The crash only happens in the plains, both in the beta and in the benchmark.

-The crash trigger is not currently known, and it doesn't seem to be reproduceable by triggering a specific action. However, I have yet to make it through a hunt with any large monster without my fix, so it's easy to re-enact, just not on command. As such, cannot consistently make it crash in the benchmark.

-The crash will manifest as a D3D error regarding DXGI_ERROR_DEVICE_HUNG. On linux it manifests as "amdgpu: ring gfx_0.0.0 timeout" (not sure what the nvidia equivalent on linux is)

-Max settings, lowest settings, it doesn't care. With my card, i'm certain i'm hitting above 60FPS consistently on medium settings, let alone lowest. Enable vsync, disable vsync, still doesn't care. Frame limit? Doesn't matter.

What i've tried:

-Updating graphics drivers (well, all drivers)

-Recompiling shaders by deleting the shader cache

-Pretty much every setting, a special focus was put on things related to shaders

-Rebooting

-Updating UEFI/BIOS

-Frame Generatiion

Now, here's the part that sucks: so far the only thing that has allowed me to make a whole hunt is Frame Generation. No crashes with frame generation enabled, but of course it looks absolutely awful and headache inducing. Given that adjusting framerate and fidelity settings had no impact, I don't particularly believe that it's actually related to frame count or performance (but the root cause may negatively be impacting performance, but i can't know for sure). Unlikely to be heat related, as frame generation would not prevent that.

I'm intentionally leaving out specs to avoid a snipe hunt: i'm well over recommended specs and this about not crashing, rather than performance.

[NeoX]

Originally posted by kohlrak:

It's taken a bit of testing, but I was finally able to narrow down a setting that let me play the game, but it's horrible. I'm hoping that with this thread, maybe someone can find a solution that doesn't involve blaming Capcom (which would be productive, but my hopes aren't high because I'm of the opinion that it's a bug in Capcom's shader code). I'm aware there's at least a few others with the unresponsive GPU issue, but I cannot be certain it still has the same cause. So, with that out of the way, what i've noticed:

-The crash only happens in the plains, both in the beta and in the benchmark.

-The crash trigger is not currently known, and it doesn't seem to be reproduceable by triggering a specific action. However, I have yet to make it through a hunt with any large monster without my fix, so it's easy to re-enact, just not on command. As such, cannot consistently make it crash in the benchmark.

-The crash will manifest as a D3D error regarding DXGI_ERROR_DEVICE_HUNG. On linux it manifests as "amdgpu: ring gfx_0.0.0 timeout" (not sure what the nvidia equivalent on linux is)

-Max settings, lowest settings, it doesn't care. With my card, i'm certain i'm hitting above 60FPS consistently on medium settings, let alone lowest. Enable vsync, disable vsync, still doesn't care. Frame limit? Doesn't matter.

What i've tried:

-Updating graphics drivers (well, all drivers)

-Recompiling shaders by deleting the shader cache

-Pretty much every setting, a special focus was put on things related to shaders

-Rebooting

-Updating UEFI/BIOS

-Frame Generatiion

Now, here's the part that sucks: so far the only thing that has allowed me to make a whole hunt is Frame Generation. No crashes with frame generation enabled, but of course it looks absolutely awful and headache inducing. Given that adjusting framerate and fidelity settings had no impact, I don't particularly believe that it's actually related to frame count or performance (but the root cause may negatively be impacting performance, but i can't know for sure). Unlikely to be heat related, as frame generation would not prevent that.

I'm intentionally leaving out specs to avoid a snipe hunt: i'm well over recommended specs and this about not crashing, rather than performance.

Have you considered giving us a full list of the hardware you have this issues with?
Also you are aware Linux is not officialy supported, so there will never be a focus on fixing an issue on an unsupported system. Do you have the same on Windows?

[XGear]

Dont worry, its not your fault, this game is Dragons Dogma 2 - 2.0 level of performance. Runs bad at everything and is doomed by birth. Dont waste your money with this, wait a year for developers try finish this, for now it is a waste of money.

[NeoX]

Originally posted by XGear:

Dont worry, its not your fault, this game is Dragons Dogma 2 - 2.0 level of performance. Runs bad at everything and is doomed by birth. Dont waste your money with this, wait a year for developers try finish this, for now it is a waste of money.

Please focus on getting your grief to reach stage 5. You comment does not help in any way.
Having an app/game crash on an unsupported system, has nothing to do with your personal performance issues and outdated hardware.

[kohlrak]

Originally posted by NeoX:

Originally posted by kohlrak:

It's taken a bit of testing, but I was finally able to narrow down a setting that let me play the game, but it's horrible. I'm hoping that with this thread, maybe someone can find a solution that doesn't involve blaming Capcom (which would be productive, but my hopes aren't high because I'm of the opinion that it's a bug in Capcom's shader code). I'm aware there's at least a few others with the unresponsive GPU issue, but I cannot be certain it still has the same cause. So, with that out of the way, what i've noticed:

-The crash only happens in the plains, both in the beta and in the benchmark.

-The crash trigger is not currently known, and it doesn't seem to be reproduceable by triggering a specific action. However, I have yet to make it through a hunt with any large monster without my fix, so it's easy to re-enact, just not on command. As such, cannot consistently make it crash in the benchmark.

-The crash will manifest as a D3D error regarding DXGI_ERROR_DEVICE_HUNG. On linux it manifests as "amdgpu: ring gfx_0.0.0 timeout" (not sure what the nvidia equivalent on linux is)

-Max settings, lowest settings, it doesn't care. With my card, i'm certain i'm hitting above 60FPS consistently on medium settings, let alone lowest. Enable vsync, disable vsync, still doesn't care. Frame limit? Doesn't matter.

What i've tried:

-Updating graphics drivers (well, all drivers)

-Recompiling shaders by deleting the shader cache

-Pretty much every setting, a special focus was put on things related to shaders

-Rebooting

-Updating UEFI/BIOS

-Frame Generatiion

Now, here's the part that sucks: so far the only thing that has allowed me to make a whole hunt is Frame Generation. No crashes with frame generation enabled, but of course it looks absolutely awful and headache inducing. Given that adjusting framerate and fidelity settings had no impact, I don't particularly believe that it's actually related to frame count or performance (but the root cause may negatively be impacting performance, but i can't know for sure). Unlikely to be heat related, as frame generation would not prevent that.

I'm intentionally leaving out specs to avoid a snipe hunt: i'm well over recommended specs and this about not crashing, rather than performance.

Have you considered giving us a full list of the hardware you have this issues with?

I have, and as stated originally, I'm afraid in doing so it'll lead us down the wrong path. I'm seeing posts here related to both AMD and nVidia, so by stating what I have may lead us down the hardware path. This is very clearly a software issue, with a software solution. By clarifying the hardware, we are off track. I assure you, though, on setting above ultra (setting ultra does not turn everything to highest) i was able to achieve a 28790 (84fps average), which the benchmark said was Excellent, so we can rule out performance of the hardware. My hardware is also new to me, but the card has been out for at least a year.

Also you are aware Linux is not officialy supported, so there will never be a focus on fixing an issue on an unsupported system.

I'm aware. But it's not a Linux exclusive issue, either. If it were a linux specific issue, i would expect a linux specific solution (fix for linux driver, fix for kernel, or whatever linux-specific thing is broken).

Do you have the same on Windows?

I have a completely different windows problem: I don't have windows. That said, I know the windows equivalent of the error code for a reason: others are having it, and they use windows.

Sorry if I seem obtuse, here, but I'm seeing how the other threads made by others are going and I'm trying to rule out the things that are already debunked and focus on new ideas. I'm suspecting either an issue in Capcom's code (most likely), but i made this thread on the off chance that this could be a setting related issue that is cross platform that someone's heard of before.

[Skyatails]

I haven't run wilds on linux since the beta and I currently don't have a linux install, but I think I know this issue. If you're running AMD, the driver has a tendency to run the GPU at higher frecuencies than it's rated for(If you look here on the discussions or in the beta's discussions you'll see people saying it's trying to boost to 3200 MHz with is just crazy), causing a driver timeout. Try using an app called "CoreCTRL" to limit the max frecuency of the card is running at (like 200-300 MHz bellow the default). Obviusly it'll impact preformance but it's better than not being able to play at all.

[kohlrak]

Originally posted by Skyatails:

I haven't run wilds on linux since the beta and I currently don't have a linux install, but I think I know this issue. If you're running AMD, the driver has a tendency to run the GPU at higher frecuencies than it's rated for(If you look here on the discussions or in the beta's discussions you'll see people saying it's trying to boost to 3200 MHz with is just crazy), causing a driver timeout. Try using an app called "CoreCTRL" to limit the max frecuency of the card is running at (like 200-300 MHz bellow the default). Obviusly it'll impact preformance but it's better than not being able to play at all.

I think i read something about this. Would not help windows users (unless somehow they have the same problem [overclocking]), but i'll have to try it. Unfortunately i'm out of time for testing, need to go to sleep for work and beta will be gone tomorrow. Will be able to keep trying with the benchmark, though.

But i also read this issue is caused by a number of other things, too. Apparently elden ring used to trigger this on amdgpu drivers with some sort of weird screen refresh thing.

[BowserMane]

So I've tried every solution I could find out there and my game would still freeze up after 5-10 min of playing. The only solution that actually worked for me was installing MSI Afterburner (https://www.msi.com/Landing/afterburner/graphics-cards) and decreasing the clockspeed to -300. I'm able to play the game on the highest graphics with FSR - Balanced and haven't had a crash for a few hours now.

[FreeSeraphim]

I've been crashing a lot, and looking through the event viewer i think its an issue with Microsoft's gameinput service. I removed it but have yet to test it again. You might want to look into that as well