this post was submitted on 15 Feb 2024
82 points (100.0% liked)

Technology

37712 readers
216 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ColeSloth@discuss.tchncs.de 4 points 8 months ago (1 children)

Not by much. My average ping on cable was around 30ms with no packet loss. On t-mo 5g it's usually around 50ms with no packet loss.

Fifty is still a good ping. Even for fps gaming. Stuff doesn't get dicey until you've gone over 80. As further, I've had no gaming issues at all with it.

[–] beefcat@beehaw.org 1 points 8 months ago* (last edited 8 months ago) (1 children)

An added 20ms is pretty noticeable in a video game. That's more than one whole extra frame in a game running at 60 fps. Liberal use of client-side prediction means it won't feel the same though, and instead of manifesting as delayed input response, you get more instances of being shot around corners and hits not registering.

But the bigger problem is packet loss, which leads to occasional lag spikes. Just like with frame rates, the average latency isn't the whole story. Those 1% lows are just as important to ensuring a smooth and consistent experience.

[–] ColeSloth@discuss.tchncs.de 1 points 8 months ago (1 children)

I've stated to someone else, but there isn't any packet loss. I can cmd line ipconfig a 20x ping to a server and not lose a single packet.

Also, losing a single frame is nothing. You aren't getting shot when you wouldn't have over 20ms.

Online shooters are always a no win situation anyhow, unless you happen to be one of the top 200 players of that game in your region. Outside of that all the games place you with a bunch of similar stat players. You don't play with all random people. You get grouped up with people like you, so you never really get to even know if you're "one of the best" players or if you're worse than most. You either play them to be extremely competitive and you're one of a handful of players good enough to actually be one of the best, or you're just playing for fun. If you're just playing for fun then 20ms is really, really, not important.

[–] beefcat@beehaw.org 1 points 8 months ago* (last edited 8 months ago)

20 packets is a very small sample size.

ping also won't necessarily capture all lost packets over wifi. Many are lost and re-transmitted by the wifi hardware without anything higher in the stack being aware.

Online shooters are always a no win situation anyhow, unless you happen to be one of the top 200 players of that game in your region. Outside of that all the games place you with a bunch of similar stat players. You don’t play with all random people. You get grouped up with people like you, so you never really get to even know if you’re “one of the best” players or if you’re worse than most. You either play them to be extremely competitive and you’re one of a handful of players good enough to actually be one of the best, or you’re just playing for fun. If you’re just playing for fun then 20ms is really, really, not important.

This is just not true. I play online shooters pretty casually, but I've been playing them regularly since 2001. When my ping time in Overwatch or Apex goes from the usual 35 to 55-60, it feels pretty noticeable in-game. Even though I'm nowhere near top 500. If you don't notice the difference, that is great, but it doesn't mean everyone else has the same experience.