If the check/repair didn't fix the issue, create a WGcheck report and send it over to the Support team via a ticket.
Also, don't forget Update 0.9.10 arrives early tomorrow morning.
#anchorsaweigh
If the check/repair didn't fix the issue, create a WGcheck report and send it over to the Support team via a ticket.
Also, don't forget Update 0.9.10 arrives early tomorrow morning.
#anchorsaweigh
It looks like a lot of people having problems here are running Nvidia hardware; if this were a problem with Warframe I'd expect it to be hitting AMD GPUs as well, but it doesn't seem to be. Anecdotal evidence suggests it might related to shader microcode translation which is something the drivers do differently in Dx11 (they do more work on the driver-side).
FWIW I've personally clocked about 10 hours of perfectly stable play on two different machines in the past few weeks (GTX 1650 and RTX 2080)) and our QA team has put in way way more time than me and have never seen this. I'm wondering if there's been a recent driver update that's introduced a problem and it's not the game. I hear someone is testing with an older version of their driver and we're waiting to hear back.
I thought there was a way to flush your driver cache in the NVIDIA control panel but I can't find it (I've always done it manually when benchmarking translation stutters). If you're using NVidia and you're brave you can try:
After purging your shader caches your first boot will be extra-hitchy until it's recached everything but it may clear up the long-term problem. In the past we've seen corrupt or bloated shader caches result in weird issues.
Just an update on this: I have started experiencing deadlocks after upgrading to 516.59 so this might be driver related.
I'm trying the 516.79 hotfix release.