Occasional Freezing/Rubberbanding [Solved]

[kiryusha_blinkov]

Having this issue myself and I didn't post about it because I assumed the issue was that my PC specs don't meet the minimum system requirements. I gained access to Deadlock on Jun 20, 2024 and did not have this issue the first day that I played. I cannot point out which patch after that when this issue started for me. I noticed that when I'm near my team or following the "creeps" the game runs perfectly fine. The issue begins when I start fighting an enemy player and/or I cast an ability. I don't know how to watch my previous matches to post a match ID but I may start recording my gameplay to show the issue.

OS: Windows 10 Pro 64-bit
CPU: Intel Core i7 4790K
RAM: 16.0GB
GPU: ATI Radeon RX 580 XFX 8GB

Edit: I switched to DirectX11 for today and the game ran as it did the first time. I guess Vulkan needs work.

What are Deadlock's the system requirements?

 

[pyatin5502]

So far every match I've played has had some ping, or latency spike, or desync, and it happens every 8-10 minutes. My player just starts spazzing out and teleporting. Sometimes it's a solid 3 second freeze that then catches up to the game. Wondering if anyone else has experienced this.

Still happens to me
Some desync happens, then I get a loong delay between inputs and actions, animations on my char cease to work and cloth/hair objects like Abrams' coat stretch out to infinity. Found no proper way to unstuck myself, just have to endure the 5 minute paralysis and hope it won't come back. Kinda like a cramp in your leg
Sometimes, it's in the beginning of the match, sometimes after respawn. One time I got paralyzed this way after my old mouse acted up, causing my PC to view it as an unknown USB device. I know my hardware is kinda old, but everything else works well enough, except for this horrible bug.

 

[negativz]

For those experiencing this issue have you noticed it happening in any other Source engine games you play? I've recently noticed it happens in Team Fortress 2 as well, so now I'm convinced it's a hardware issue with Source engine.

 

[negativz]

For those having the same issue, turns out it was connection related. The modem was failing. After replacing it, the issue went away.