Seriously, are the servers run on a bunch of DeLoreans? Samsung Smart Fridges? This is the only game where I'm getting 100ms pings for supposedly NA servers. FPS steady at 60fps and even forced it with fps_max. It doesn't happen in the sandbox, only in public games. Server is peaking with the red dot from the start, and the console is constantly flagging for errors while loading files. I've turned off all graphical settings for the game and it doesn't make a difference. I can consistently keep 60fps and everything max on Helldivers 2 and there's no way you can tell me that this game is more intensive. I know it's a beta but this is basically unplayable.
Absurd Rubberbanding and Warping: Should have just made a back to the future game
- Thread starter hbnrw
- Start date
MissPotato
Member
This game does not handle high packet-loss well. It sounds like your internet is not very stable. May want to try restating your router if you haven't, or perhaps calling your ISP.
I just don't understand how I can roll a ping of 42ms in Helldivers with music and Twitch streaming, but not in Deadlock by itself. Also I've reinstalled twice and verified the files multiple times.
Intel(R) Core(TM) i3-10100F CPU @ 3.60GHz 3.60 GHz
16GB of Ram at 2666
RTX 3060 TI
Took a screenshot from sandbox and then a bunch over the course of a bot match. At no point does my internet peak, likewise my CPU and GPU remain stable through the entire thing. It's definitely not a network issue on my side. Now I did notice that my ping was lower this time sitting at around 50ms which is what I would normally expect. But that definitely did not affect how much rubberbanding I was doing.
Intel(R) Core(TM) i3-10100F CPU @ 3.60GHz 3.60 GHz
16GB of Ram at 2666
RTX 3060 TI
Took a screenshot from sandbox and then a bunch over the course of a bot match. At no point does my internet peak, likewise my CPU and GPU remain stable through the entire thing. It's definitely not a network issue on my side. Now I did notice that my ping was lower this time sitting at around 50ms which is what I would normally expect. But that definitely did not affect how much rubberbanding I was doing.
Attachments
Lady Briar
Active member
As others have said, Deadlock doesn't handle packet loss well. It's not a finished game, remember. I often have to restart my router before playing, or I have huge network issues that I don't see anywhere else. I feel you, its frustrating, but it is most likely our ISPs fault, and Deadlock just not being polished, yet. I suspect it probably doesn't have any of the optimization, yet, needed to smooth over small packet drops and whatnot. But, hopefully, it will soon!
For your sake and mine.
Lady Briar
Active member
Solidarityyyyyy~!
Sir Gamer
Member
Interestingly, this game now uses Steam Datagram Relay, which was not the case some time ago — I remember checking my console to get real server address and then doing a traceroute to look for obvious routing issues. But now I get a virtual SDR id instead. Coincidentally, I've started experiencing microscopic but extremely jarring rubber-banding episodes about once per game, which wasn't a thing back then.
Steam Datagram Relay is Steam's own packet routing network on top of the internet.
The good thing is that now we don't need to be at the mercy of our unreliable and lazy ISPs to do they job — the ISP is supposed to optimize the routes, so that the traffic flows through the internet as fast as possible, routing around overloaded and malfunctioning nodes. But that requires work, and people don't like working, and thus new games often experience routing issues. Steam claims that their SDR can optimize the routes on their side, which means a lazy ISP should not be an issue now.
The bad news is that if Steam fails to find you a good route, there's nothing you can do on your side. But it also means that you should indeed direct your pressure towards the game developers, not your ISP.
Steam Datagram Relay is Steam's own packet routing network on top of the internet.
The good thing is that now we don't need to be at the mercy of our unreliable and lazy ISPs to do they job — the ISP is supposed to optimize the routes, so that the traffic flows through the internet as fast as possible, routing around overloaded and malfunctioning nodes. But that requires work, and people don't like working, and thus new games often experience routing issues. Steam claims that their SDR can optimize the routes on their side, which means a lazy ISP should not be an issue now.
The bad news is that if Steam fails to find you a good route, there's nothing you can do on your side. But it also means that you should indeed direct your pressure towards the game developers, not your ISP.
Can you check if the problem persists with a wired connection?
Unless you have full duplex wifi.
Edit: To go into more depth, Helldivers is PvE and it's easier to interpolate game state to keep it smooth, but because Deadlock is PvP with some sensitive collision-based mechanics, even quality wired connections won't be fantastic with abilities like Abram's shoulder charge. Being on a half duplex connection can make this worse, because your connection can only send or receive at any given time, but not both, which is a problem that will exist even if you have low latency and high bandwidth.
If you look at old Valve titles like L4D2 or TF2, there's some mechanics that are notoriously bad about this, like Chargers or Pyro's airblast.
Unless you have full duplex wifi.
Edit: To go into more depth, Helldivers is PvE and it's easier to interpolate game state to keep it smooth, but because Deadlock is PvP with some sensitive collision-based mechanics, even quality wired connections won't be fantastic with abilities like Abram's shoulder charge. Being on a half duplex connection can make this worse, because your connection can only send or receive at any given time, but not both, which is a problem that will exist even if you have low latency and high bandwidth.
If you look at old Valve titles like L4D2 or TF2, there's some mechanics that are notoriously bad about this, like Chargers or Pyro's airblast.
Last edited:
So I was prepared to eat my words, because after 2 days of trying it rebooting the modem resulted in being able to play 3 games without rubberbanding before it started again. However, that was the only time that this has resulted in a better performance as restarting the modem and router since then has not done anything. So I can only conclude that was a one time fluke. Which really sucks because for the brief time I got to play against other people without warping around was really fun.
-e-
What this person is experiencing is similar to me, except imagine it happening every few seconds, and the ping is 50 - 99.
-e-
What this person is experiencing is similar to me, except imagine it happening every few seconds, and the ping is 50 - 99.
Last edited:
It has now been almost 2 months since this started and if anything, it's only gotten worse. After looking into it more on things like DOTA2, CS GO, and CS2, it's apparent that this isn't a new issue nor one that Valve apparently cares enough to look into. Which is bonkers to me. How can a company that owns and operates one of the largest online retailers, does streaming, and backbone support for a ton of multiplayer games, have such god awful netcoding for their engine? Again, I can play something like BF2042, Helldivers2, among others with no problems. While it's obviously not ramped enough for them to care, it does baffle me that it's an issue to begin with since Source 2 has been out for awhile now.
