> If the game is running at 500fps, it registers within 2 milliseconds, even though you won't see the action for up to 16.67 milliseconds later.

Okay I think I follow this, but I think I'd frame it a little differently. I guess it makes more sense to me if I think about your statement as "the frame I'm seeing is only 2ms old, instead of 16.67ms old". I'm still not seeing the action for 16.67ms since the last frame I saw, but I'm seeing a frame that was produced _much_ more recently than 16.67ms ago.

Thanks for the explanation, it helps!

▲

mattmanser 4 days ago | parent [-]

This is mostly like high fidelity audio equipment, or extreme coffee preparation. Waste of time for most people.

I used to play CS:Go at a pretty high level (MGE - LE depending on free time), putting me in the top 10%. Same with Overwatch.

Most of the time you're not dying in a clutch both pulling the trigger situation. You missed, they didn't, is what usually happens.

I never bothered with any of that stuff, it doesn't make a meaningful difference unless you're a top 1%.

But there's a huge number of people who play these games who THINK it does. The reason they're losing isn't because of 2ms command registrations, it's because they made a mistake and want to blame something else.

	▲	vintermann 4 days ago \| parent [-]
		I'm sure that's true, but low latency can just plain feel good. I don't play FPSses at all, and I can totally understand how low latency helps the feeling of being in control. Chasing high refresh rates and low latency seems a lot more reasonable to me than chasing high resolution.