3 ms·
I recall many years ago playing Team Fortress. 100ms ping time was decent. But whenever it got the 30ms range my score kill / death ratio would skyrocket. Th
by treeman79 5y ago
I recall many years ago playing Team Fortress. 100ms ping time was decent. But whenever it got the 30ms range my score kill / death ratio would skyrocket. They later implemented code to stop low pingers from dominating.
Same thing with mouse. Wireless mouse feels unnaturally sluggish to me now. Was years before I realized that it wasn’t just in my mind and most gamers use wired.
- snvzz 5y agoMost people underestimate the effects of latency. If 0.1s makes any sense (as in humans processing 10 events per second), which I do honestly doubt, then 100ms -> 30ms still means that the other party is almost one full event behind. That's massive.
- beebeepka 5y agoMost people haven't played Quake/UT/CS competitively. Btw, with modern games 30ms isn't just one full event/server tick behind. Multiplayer shootets do have 100 or higher tick rates now, so 30 would be more like 3 cycles behind
- snvzz 5y agoI meant human ticks, not server ticks. Still, it only goes to show it matters at so many levels. Like, if using a 60Hz screen with 30ms latency, you're always almost 2 frames behind, so you always react 2 frames late, compared to another 60Hz screen person at the same ping with, say, 2ms latency.
- teddyh 5y agoSo you're the LPB! https://web.archive.org/web/20050214193844/http://archive.gamespy.com/dailyvictim/index.asp?id=194 https://web.archive.org/web/20050214193844/http://archive.ga...
- treeman79 5y agoNice. I used to have a full size house fan pointing at my open team Fortress server. If I recall more the 8 people and it would overheat anyways.
- beebeepka 5y ago100 ping is no small amount, especially with skill games where almost everyone is trying their best. Assuming you're talking about TF the Quake mod here. Not that I advocate for wireless mice but modern gaming wireless mice do not suffer from lag issues