[DE]Glen Dev Tracker | devtrackers.gg

Update on this: our network partner has confirmed they have a problem and are working on it. They say they'll let us know when they have more information. Thank you for your patience with this and thank you very much to those of you who have sent in logs to help us diagnose this problem.

Comment

08 Aug 18:53 [DE]Glen on Forums - Thread - Direct

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.

Comment

07 Aug 12:51 [DE]Glen on Forums - Thread - Direct

Comment

29 Jul 17:46 [DE]Glen on Forums - Thread - Direct

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 usin...