This video isn’t sponsored or in any way associated with Nvidia, I just felt like some of the comments the first video received needed following up on using FACTS and LOGIC and Fluffykins.
See the first video on input latency here: https://youtu.be/NE0qg_8k0BE
0:00 – Latency misconceptions
1:31 – CS2 VS CS:GO / CS:S Latency
2:23 – Vsync
3:43 – Gsync + Vsync + Framerate cap
5:01 – Upscaling adds latency?
5:28 – Power consumption VS Input Latency
8:10 – Nyquist’s Theorem VS Slow-mo capture
8:41 – ULMB2
9:26 – Microwave VS wireless mouse
21 Comments
Why bother testing if you'll ultimately overlook the game's key issues and praise Valve anyway? After over a decade, what's the point? It seems you're out of touch with reality, perhaps due to indifference or misunderstanding. At LAN events, where there are no cheaters, life seems great. But don't be shocked if Valve never releases an anticheat system; they, like you, seem content collecting data and laughing at trivial matters. Using your platform for such pointless activities… You might as well eat sand, though you probably prefer glue.
If you put your t-shirt over your mouse usb plug and blow into it, it helps your input lag.
We need more cat!!
muzzle flash has nothing to do with the bullet hitting the target.
please fix your subtitles
6:44 "gaming can't max out all of the processorís cause, nor its power"
These weird accented letters are all over, not to mention that you used "cause" instead of "cores" (I know you're british but come on).
lol, the microwave banter was great. I have had a hard time finding microwaves that interfere with any wireless communications in a hot minute, but I have had microwaves that fizzled my wifi long ago. Can't imagine there are any more produced too much nowadays since the majority of the world is online in some way.
The cat is the true latency. They distract you with snuggles while you are trying to game. You should do a test to see how you do in a match without the kitty vs how you do with the kitty!
It is extremely astounding how much the cs community has been having a meltdown about this game being “unplayable” now when so much of the issues either didn’t exist or have been patched out.
I’m sure there’s some stuff to iron out still, but any time anyone dies now it’s the games fault and not theirs
cat!!!!!!
I like your feline's face
What about motion latency when swiping the mouse and aiming cuz it feels so shitty even with decent fps
Wait what? I forgot CS2 exist, boring dead game. Not to mention broken, Im not even good and I got global in csgo 2 years ago by rushing every round as CT with mp9. Through molotov. And bhopping around corners. Fun, but just too easy and gets old. CS Source is the last ever good competitive game to have existed. Other than Super Mecha Champions (which most of you normies havent even heard about). Im still gona watch the video tho, the science of this stuff is cool
As someone who uses microwave as a mousepad, I appreciate your last test a lot ty
3:28 idiotic statement. The way fast sync works makes it the choppiest possible mess, way way way worse than just no vsync (unless you are running the game at like 3000fps I mean. Then it wont be as choppy and only medium amounts trashier compared to vsync OFF)… Which doesnt consern me tbh, that you give this awful advice – way to handicap my opponents if i ever get back into CS2.
Try use soldering tool when play. Maybe it is works
not sure about this box.. it also works when you not in the game but just in the lobby, so maybe it just registers mouse click and not engine response in game. try comparing latency in the lobby vs in the game, if theres no difference its useless. there is a chance they used it to compare game response to mouse response, like difference between muzzle flash and box flash
I love the fact that your cat always looks mad.
So it was all a myth that a wireless mouse has a higher input lag
Fuck cs2 biggest shit game ever
Is the latency sensor sensitive enough to notice a disappearing digit in the ammo count? For example, you have 10 rounds then fire and it becomes 9 with the second digit disappearing. You could increase HUD scale and set the colour to white to help.
Even if the Reflex test box is tied to the game, to me it introduces another layer of uncertainty. What if the game has a bug which delays input processing inside of the engine itself? How could any external tool capture that? I understand that Reflex is implemented in-engine via an API but that gives no assurance that the game receives and handles the input immediately. Given your cross-checking, it does appear to tie up for CS2. It might not for another title, or if a new bug is introduced.
Latency is all good for CS2, but how many time I die behind walls is something that needs fixing. People can say it's the same in GO, but for me personally it's nowhere near close.