WEBVTT

00:00:00.000 --> 00:00:04.560
Everyone knows that adding latency to your gaming experience is bad,

00:00:04.560 --> 00:00:08.640
but exactly how much latency is too much latency?

00:00:08.640 --> 00:00:11.640
At what point can you legitimately blame the lag

00:00:11.640 --> 00:00:17.160
for being hard stuck at Copper 7? To find out, we've assembled a crack team

00:00:17.160 --> 00:00:20.200
of four certified gamers that range in skill level

00:00:20.200 --> 00:00:24.560
from absolute hack all the way to Godlike.

00:00:24.560 --> 00:00:28.680
And we're gonna tell you exactly how much input latency it takes

00:00:28.680 --> 00:00:34.120
to measurably affect your KD ratio. And all of this is possible thanks to ASUS

00:00:34.120 --> 00:00:37.680
who sponsored this video. We'll be using their ROG gaming peripherals,

00:00:37.680 --> 00:00:41.080
including their new 27 inch tandem OLED monitor

00:00:41.080 --> 00:00:44.920
that can switch between 720p, 720 Hertz,

00:00:44.920 --> 00:00:48.880
and 1440p, 540 Hertz using just a hotkey.

00:00:48.880 --> 00:00:52.800
And it can do all of that without relying on display stream compression.

00:00:52.800 --> 00:00:56.760
But enough ado, let's do this.

00:00:56.760 --> 00:01:00.920
Every test subject will use one of the three identical setups behind me.

00:01:00.920 --> 00:01:05.560
They use the same high performance ASUS PCs, the same low latency gaming peripherals,

00:01:05.560 --> 00:01:08.640
and the same silky smooth mousing surfaces

00:01:08.640 --> 00:01:13.280
courtesy of these desk pads from lttstore.com. The real star of the show today though

00:01:13.280 --> 00:01:19.000
is these black boxes. Inside each one of these is an Arduino Leonardo

00:01:19.000 --> 00:01:23.680
that connects to this USB hub. This setup allows us to add latency

00:01:23.680 --> 00:01:27.760
in one millisecond increments from zero to 100 milliseconds,

00:01:27.760 --> 00:01:31.640
which I remind you is one tenth of a second.

00:01:31.640 --> 00:01:34.760
That would be terrible, or would it?

00:01:35.720 --> 00:01:42.480
Each participant will complete three sets of tests while David here secretly changes their latency in between

00:01:42.480 --> 00:01:45.640
and then benchmarks their gaming performance using AMELabs.

00:01:45.640 --> 00:01:48.640
It's important to note that we tested our base system latency

00:01:48.640 --> 00:01:53.440
at about 12 and a quarter milliseconds, which we will be adding to whatever we have on our box,

00:01:53.440 --> 00:01:57.680
which will give us our theoretical click to photon latency.

00:01:57.680 --> 00:02:01.160
We did consider adding latency to different parts in the chain,

00:02:01.160 --> 00:02:04.920
but in our preliminary testing, we found that it didn't have a major impact,

00:02:04.920 --> 00:02:08.400
and so we decided to keep it in one spot to keep it simple and consistent.

00:02:08.400 --> 00:02:12.040
But enough with the boring facts. Let's game.

00:02:12.040 --> 00:02:15.800
I'm a 30 year old unk at this point.

00:02:15.800 --> 00:02:18.040
I go buy a baby no money.

00:02:20.600 --> 00:02:25.600
And I make music and I play video games occasionally jelk.

00:02:26.040 --> 00:02:29.840
My gaming ability out of 10, I used to be pretty good,

00:02:29.840 --> 00:02:33.240
but now I'm garbage because all these 12 year old kids

00:02:33.240 --> 00:02:37.840
are just insane. I don't really play much like competitive gaming anymore

00:02:37.840 --> 00:02:41.080
because it's just unhealthy. Ready? Lock in bro.

00:02:42.920 --> 00:02:48.080
Baby no accuracy. I mean 45, come on now. Did I have any, latency or no?

00:02:48.080 --> 00:02:52.240
No, no, no, no, no, no, no, no. Whoa, whoa, whoa, whoa. That's part of your best in the variable.

00:02:52.240 --> 00:02:57.320
Whoa, man. Oh my God, I'm sweating. Literally dripping in sweat.

00:02:57.320 --> 00:03:02.000
Brother, he hit 50K. High score. Wait, hold on, wait, you're actually tall.

00:03:02.000 --> 00:03:05.600
Wait, wait, yo, crazy. All right, this next one's gonna be a dude.

00:03:05.600 --> 00:03:08.920
Oh, this one, this next one, wrap the whole thing up.

00:03:08.920 --> 00:03:12.600
This is straight order. It looks so easy when you watch someone else do it.

00:03:12.600 --> 00:03:18.080
You're just like, bro, just point at the thing. Oh, we've reached new depths.

00:03:18.080 --> 00:03:22.120
Wow, bro. New lows. It's got some tips. No, there's tips for you.

00:03:22.120 --> 00:03:25.200
There's tips. There's tips. Keep it up.

00:03:25.200 --> 00:03:28.600
Okay. Yeah. And there's another tip on the bottom saying,

00:03:28.600 --> 00:03:30.720
like, yeah, we're getting weird latency issues.

00:03:32.720 --> 00:03:36.800
That was better. Hey, look at the, it's suggesting you become a pro.

00:03:36.800 --> 00:03:42.000
Just the arms hurting now. Oh, it's getting real now.

00:03:42.000 --> 00:03:45.600
All right, what if I, what if I walk in like this?

00:03:45.600 --> 00:03:49.120
Closer to the strain, less input the light closer. Yeah, yeah.

00:03:50.320 --> 00:03:55.400
Oh, locked in position. I really don't think this is going to help.

00:03:55.400 --> 00:03:58.680
Oh, wait, more. Definitely had latency there too.

00:03:58.680 --> 00:04:01.920
Okay. Okay, pro perspective though. Is this actually useful?

00:04:01.920 --> 00:04:06.920
This is useful, maybe 20% of the time, in my opinion.

00:04:08.440 --> 00:04:13.440
One, two, three, four, five, six, seven, eight,

00:04:13.760 --> 00:04:17.840
nine, 10, 11. Oh, wait, the counting is going to fail.

00:04:17.840 --> 00:04:22.920
Wait, wait, wait. Wait, hold on. Crazy, crazy. Overflicks, underflicks, perfect flicks.

00:04:22.920 --> 00:04:27.040
I just want to be an okay flick. There's too many unders. Yeah, there's a lot of under.

00:04:27.040 --> 00:04:31.120
What does that mean? That means you're shooting lower. You're tracking it, but you're shooting it

00:04:31.120 --> 00:04:34.800
basically way too behind it. Yeah, good job, good job. All right.

00:04:34.800 --> 00:04:38.120
Solid, solid, solid, solid. Solid, solid. That's solid.

00:04:49.000 --> 00:04:53.760
My name is Leon Kim. Also known as Kanata. I'm a professional Fortnite player for Dignitas.

00:04:53.760 --> 00:04:57.640
I think I'm really good at gaming and like I can go

00:04:57.640 --> 00:05:00.720
like basically go to any game and be good at it.

00:05:00.720 --> 00:05:03.160
I think I'm like 8.5 out of 10.

00:05:08.920 --> 00:05:14.840
I think you're underselling yourself. Okay. Whenever you are ready, go for it.

00:05:14.840 --> 00:05:18.040
I bet, I'm starting. Always going for a big score.

00:05:18.040 --> 00:05:22.520
This one's lucky easy. His movements are so much more precise than mine.

00:05:22.520 --> 00:05:26.000
This guy's lucky messing with the input delay over here. You can't really tell on this one though,

00:05:26.000 --> 00:05:29.440
cause this one's just easy. Like I could be on like 20 Hertz type of thing

00:05:29.440 --> 00:05:33.800
and it'll be fun. Damn. It's not that, it's not that hard.

00:05:33.800 --> 00:05:37.440
Yeah, it's too easy over here. Okay, this one is crazy.

00:05:37.440 --> 00:05:40.720
This one like you move and you're not even moving.

00:05:40.720 --> 00:05:45.440
Like I want to move, but it's like, it's like I'm dragging through mud type of movement.

00:05:45.440 --> 00:05:49.160
It's like someone's holding my legs back in a race. Damn dude.

00:05:49.720 --> 00:05:53.360
Pop my reaction time go up. All right, next test.

00:05:53.360 --> 00:05:58.000
Okay, this one is bad. Oh yeah. Okay, that was terrible.

00:05:58.000 --> 00:06:01.400
Oh my God, that was terrible. Tenses up your forearms too much.

00:06:01.400 --> 00:06:05.760
Last time I did it. Oh my God. Oh, that's terrible. Oh, this one's really bad.

00:06:05.760 --> 00:06:10.160
Like the pixels aren't even working. No, it's over, it's over.

00:06:10.160 --> 00:06:13.360
No, that one was impossible. They were all the input delays.

00:06:13.360 --> 00:06:17.200
Actually, it's actually just affecting the whole thing. Okay, this one feeling good.

00:06:18.200 --> 00:06:21.680
Okay, that one felt better.

00:06:21.680 --> 00:06:25.400
That one felt a lot better. All right, last one.

00:06:25.400 --> 00:06:29.760
Damn, your ARM actually does like tense up, bro. Like it actually like messes you up.

00:06:32.800 --> 00:06:36.880
How long is this thing? Damn, you're so close to 67%.

00:06:36.880 --> 00:06:39.960
Oh my God. I hit 67. Oh no, you were at 67.

00:06:41.960 --> 00:06:46.800
You guys are too old for this man. Okay, this one was cuck, this one's cuck.

00:06:46.800 --> 00:06:51.320
This one's cuck, this one's cuck, this one's cuck. Oh my God, it's really bad.

00:07:02.680 --> 00:07:07.840
As many of you will know, I'm Linus from Linus Tech Tips. Love technology, love gaming.

00:07:07.840 --> 00:07:13.200
Not really as good at gaming as I am at tech. I'm confident that I will be able to try my best.

00:07:13.200 --> 00:07:16.920
Locking, bro. For I don't feel it. Oh, that one looks bad. I click to begin.

00:07:16.920 --> 00:07:19.120
Okay, you're not supposed to influence the test.

00:07:22.480 --> 00:07:28.200
Okay. Pretty good. So theoretically, the more latency that you add,

00:07:28.200 --> 00:07:31.960
the reaction time should just naturally go up. Well, here's the thing.

00:07:31.960 --> 00:07:38.360
We're not adding so much latency that your human reaction time and movement

00:07:38.360 --> 00:07:43.640
is likely to be a major factor. The latency we're adding is more likely to make it

00:07:43.640 --> 00:07:47.160
so that you will overshoot things. And you're not as,

00:07:47.160 --> 00:07:50.360
it's like you're not as connected to the machine.

00:07:50.360 --> 00:07:53.720
Are the routes the exact same? No, no, there's randomly generated.

00:07:53.720 --> 00:07:57.640
Okay, yeah. How many of the variables do you guys have? No, no, don't worry about that.

00:07:59.640 --> 00:08:01.320
Next task. Okay.

00:08:04.240 --> 00:08:05.080
Pretty good.

00:08:07.560 --> 00:08:10.000
Hey man, I'm trying to be positive reinforcement here.

00:08:13.640 --> 00:08:22.480
So my name is Typical Gamer,

00:08:22.480 --> 00:08:26.080
and I've been live streaming and making videos since 2009.

00:08:26.080 --> 00:08:31.920
So I'd rate my gaming ability out of 10. For Fortnite, I would put it at like a 8.5.

00:08:31.920 --> 00:08:35.280
I feel like there's gotta be, yeah, there's latency on this one already. They pre-fired it.

00:08:35.280 --> 00:08:39.360
Yeah. Don't even, don't think about that though. Just do your best every time.

00:08:39.360 --> 00:08:42.880
Yeah, come on, Typical Bro. Oh, I'm so good.

00:08:42.880 --> 00:08:46.120
I'm still good, I'm still good. Okay. All right.

00:08:46.120 --> 00:08:49.600
Damn. Wait, hold on. Oh, yeah, you're good.

00:08:49.600 --> 00:08:53.120
And watch all out. And watch all out. It's 56.

00:08:53.120 --> 00:08:57.000
Damn. Whoa. Unks got it, Unks got it.

00:08:57.000 --> 00:09:01.640
Unks literally got it. Oh my, oh, what is this?

00:09:01.640 --> 00:09:05.440
Oh, this is maximum delay. That was easy. Holy.

00:09:06.520 --> 00:09:08.560
That was so bad. All right, last one.

00:09:10.040 --> 00:09:13.760
Bricked up right now. What? What?

00:09:13.760 --> 00:09:18.320
That is a four-night term though. Bricked up? Yeah, it's when you have mass break.

00:09:18.320 --> 00:09:21.920
Oh, I lost a break? I don't know about that one, dude. Can you give me your break?

00:09:21.920 --> 00:09:23.520
I've heard that one before.

00:09:34.800 --> 00:09:39.080
We have enough data at this point, but one thing we thought would be kind of interesting

00:09:39.080 --> 00:09:43.520
would be to go head to head and find out just how much latency it takes

00:09:43.520 --> 00:09:46.720
for one of our more typical gamers

00:09:46.720 --> 00:09:51.720
to be one of, well, typical gamer, but also like the better gamers.

00:09:51.720 --> 00:09:55.240
Are you interested to know? Let's do it.

00:09:55.240 --> 00:09:58.680
Actually, I'm talking, let's do it. Oh, yeah, yeah, yeah, yeah. You're talking to your viewers.

00:09:58.680 --> 00:10:03.280
No, I mean, leave a comment below if you are. All right, ready?

00:10:03.280 --> 00:10:05.800
Let's go. Come on, match starting. My lock-in Linus.

00:10:07.200 --> 00:10:10.720
Ready, three, two, one, peek. You saw my left. No, I'm not gonna.

00:10:10.720 --> 00:10:13.960
I don't want it. Move this way. I could stay alive.

00:10:13.960 --> 00:10:17.440
Go this way. Okay, look down. I could be a live man.

00:10:17.440 --> 00:10:20.960
I could be a live man. Ready, three, two, one, peek. No, I don't want it.

00:10:20.960 --> 00:10:24.040
You should peek. I think it's a really good time to peek.

00:10:24.040 --> 00:10:24.880
Just peek.

00:10:27.960 --> 00:10:32.800
Whoa! Oh! Wow, that was disgusting.

00:10:35.240 --> 00:10:37.760
Okay, they have nerfed me, I will say.

00:10:39.120 --> 00:10:42.120
I told you, bro. Oh! I told you.

00:10:43.440 --> 00:10:47.320
It's obvious. Always right side. It's obvious, man.

00:10:47.320 --> 00:10:51.000
Obvious right side right there. Okay, this is, okay, now it feels a little wavy.

00:10:51.960 --> 00:10:55.880
Oh! Okay, Linus. He was locked in on that.

00:10:55.880 --> 00:10:59.160
Yeah, it feels like I'm like, it's like a pendulum when I'm swing.

00:11:01.000 --> 00:11:05.120
Oh my. Awareness, it's a negative awareness, man.

00:11:05.120 --> 00:11:08.760
Now? Did you just call me negative awareness?

00:11:09.760 --> 00:11:14.800
What kind of a thing to say is that? We are now at 75 milliseconds.

00:11:14.800 --> 00:11:19.440
Oh! Oh my God! I don't know how to do that. Wow, that's a tough go.

00:11:20.440 --> 00:11:24.200
All right, let's go, bro. Let's swap. Are we swapping? Yeah, let's swap in.

00:11:24.200 --> 00:11:27.520
GG, GG. Good game, good game. GG.

00:11:27.520 --> 00:11:30.840
Dude, this is probably the dopest lab I've ever been a part of.

00:11:30.840 --> 00:11:34.880
What is this? Oh my, what the?

00:11:34.880 --> 00:11:39.440
F***. No, why is he not actually nasty? You know what I'm saying? Yeah, this is disgusting.

00:11:39.440 --> 00:11:42.520
You gotta find awareness on it. You saw that, right? You saw that shot?

00:11:42.520 --> 00:11:46.400
Yeah, but that's just being better at it. That had nothing to do with awareness.

00:11:46.400 --> 00:11:51.120
He knew where you were just as much as you knew where he was. You just are way faster.

00:11:51.120 --> 00:11:54.800
All right, don't play the same way you're doing too much, you're doing great. Okay, you need awareness.

00:11:54.800 --> 00:11:58.600
You guys are the worst coaches ever. He's never gonna peek it twice, all right?

00:11:58.600 --> 00:12:01.000
Unless right now, that he's aware that I said that.

00:12:02.080 --> 00:12:06.040
Oh! Got that, dude. I had that.

00:12:06.040 --> 00:12:09.600
F***. Maybe like, okay, he's so sweaty, bro.

00:12:09.600 --> 00:12:12.840
He's actually nuts. He's actually nuts.

00:12:12.840 --> 00:12:17.200
Now is maybe a good time to talk about the monitor. Tandem OLED, that gives you boosted brightness,

00:12:17.200 --> 00:12:21.240
as well as better longevity according to ASUS. They've got their true black glossy coating,

00:12:21.240 --> 00:12:26.560
so you get that gorgeous OLED contrast, and it looks almost as good from the back.

00:12:26.560 --> 00:12:31.920
Got transparent accents. RGB, absolutely flipping gorgeous.

00:12:31.920 --> 00:12:36.080
It is gorgeous. Oh, and don't forget that it has ROG OLED Care Pro,

00:12:36.120 --> 00:12:40.520
which includes the Neoproximity Sensor, which means the display will turn off when you step away,

00:12:40.520 --> 00:12:44.880
and back on when you step back to games. Okay, we're at 50 milliseconds.

00:12:44.880 --> 00:12:48.400
50 milliseconds. No way! What?

00:12:48.400 --> 00:12:52.040
Peek, bro. Peek that? Yeah, peek. Should I peek it?

00:12:52.040 --> 00:12:56.360
Peek it. You think so? Yeah, do it. All right, three, two, one.

00:12:56.360 --> 00:12:59.720
F***. F***. F***. F***.

00:13:00.720 --> 00:13:04.720
No! Oh! Let's go!

00:13:05.000 --> 00:13:08.920
Awareness. Awareness, coach. Maybe no chill.

00:13:08.920 --> 00:13:12.160
Yeah, get clapped, bro. He's got to hit it all.

00:13:14.800 --> 00:13:17.880
Bam! Give this guy more latency.

00:13:17.880 --> 00:13:21.160
No, no, no, we're gonna work it, we're gonna work it. Give this guy more latency. Yeah, give me some latency, bro.

00:13:21.160 --> 00:13:25.280
One more? Give him more. Give him more latency. Put it in the hands of God there for a second.

00:13:25.280 --> 00:13:28.280
That's all that. Prayed it went the right way.

00:13:28.280 --> 00:13:32.640
Oh, I had that. I swear, I swear you didn't put it in the wall like I was.

00:13:32.640 --> 00:13:36.160
Yeah, I know. See that?

00:13:36.160 --> 00:13:40.920
See how I just did that? You think I'll repeat this thing? Oh!

00:13:40.920 --> 00:13:46.040
Let's go! F***! He just sat there, like, I should have just...

00:13:46.040 --> 00:13:49.760
Let's go, dude. He's losing confidence. Losing confidence, losing confidence.

00:13:49.760 --> 00:13:52.960
No awareness? Yeah, ego challenge. Ego challenge.

00:13:52.960 --> 00:13:57.200
Every opportunity. Oh, how much has he got now, David?

00:13:57.200 --> 00:14:00.840
75. Give me like 100, bro. Oh, it's over. Give me like 120, I swear.

00:14:00.840 --> 00:14:05.680
It's over. It's over, you won. It's over. A lot more analysis is going to be needed for the AIM Lab stuff,

00:14:05.680 --> 00:14:09.440
but what is clear from the 1v1 is whether you call it awareness,

00:14:09.440 --> 00:14:14.080
whether you call it experience. If you're not good at the game,

00:14:14.080 --> 00:14:17.640
no amount of latency advantage is going to make you good at the game

00:14:17.640 --> 00:14:22.480
compared to someone who's got it. It was a great time.

00:14:22.480 --> 00:14:25.720
Yeah, I mean, it was a... What day is it today? Wednesday?

00:14:25.720 --> 00:14:28.800
It's a good day to be a Wednesday. It was a lot of fun.

00:14:28.800 --> 00:14:32.560
Yeah, I had a great time. That was pretty fun. I actually had a good time playing that.

00:14:32.560 --> 00:14:39.200
AIM Labs with a different latency. Like, I can see why it affects gaming heavily.

00:14:39.200 --> 00:14:43.600
That was rough. Like, I know that I'm average,

00:14:43.600 --> 00:14:48.840
but standing next to someone who's not average just makes it so much more apparent.

00:14:48.840 --> 00:14:52.000
What surprised you the most about today?

00:14:52.000 --> 00:14:56.320
That this is your guys' job. It's really sick.

00:14:56.360 --> 00:15:00.760
Like, the ability to basically just do science with the bros.

00:15:00.760 --> 00:15:04.880
It's sick. So, how'd it go?

00:15:04.880 --> 00:15:09.880
Initial testing, it was super clear right away that input latency has a big impact on gaming performance.

00:15:09.880 --> 00:15:13.640
At just 10 milliseconds, we were seeing almost a 7% drop,

00:15:13.640 --> 00:15:18.800
and by 50 milliseconds, over 25% drop in scores, on average.

00:15:18.800 --> 00:15:23.400
Really, that is surprising to me, because as one of the test subjects,

00:15:23.480 --> 00:15:27.880
I would say that at just a small amount of input latency,

00:15:27.880 --> 00:15:32.800
I didn't feel it. It didn't bother me. For me, there was very much a threshold,

00:15:32.800 --> 00:15:36.840
but you're saying that across our four subjects,

00:15:36.840 --> 00:15:40.800
even a little bit clearly matters. Yes, even before you can feel it,

00:15:40.800 --> 00:15:45.040
which everyone sort of made comments at about 35 to 50 milliseconds about,

00:15:45.040 --> 00:15:49.440
because it's so jiggly. Even before then, it's a pretty clear line down.

00:15:49.440 --> 00:15:54.680
And what I also found interesting was that each task had a different difference from the input latency.

00:15:54.680 --> 00:16:01.240
The biggest difference was the second one. Distraction one. Everyone had a very clear decline across all skill sets.

00:16:01.240 --> 00:16:05.320
The third one was a pretty similar linear, and the thing I found really interesting

00:16:05.320 --> 00:16:09.080
about the first test is that its secondary measurement was just reaction time,

00:16:09.080 --> 00:16:12.360
and I assumed that the more input latency I added,

00:16:12.360 --> 00:16:15.400
it would linearly add to the reaction time score,

00:16:15.400 --> 00:16:19.680
but it seemed like it kind of compounds. When you added like 50, it would increase

00:16:19.680 --> 00:16:23.120
by 100 milliseconds. So there's kind of like a compounding effect

00:16:23.120 --> 00:16:28.800
in the tracking aim click. But one thing that I realized was that 10 to 50 milliseconds

00:16:28.800 --> 00:16:32.760
was not granular enough. I chose those metrics because when I was testing,

00:16:32.760 --> 00:16:36.000
that's when I could start to feel it. So like, oh, that's gonna be, you know, the thing.

00:16:36.000 --> 00:16:39.440
So that's what you were doing the second time. We did a second round of testing

00:16:39.440 --> 00:16:44.280
with three millisecond increments. Surely you're not gonna be able to tell a difference

00:16:44.280 --> 00:16:49.160
from like three to six milliseconds. The first round of this ad hoc testing

00:16:49.160 --> 00:16:52.720
was really interesting, where there is a clear pattern down

00:16:52.720 --> 00:16:55.800
to about seven, eight, nine percent

00:16:55.800 --> 00:17:00.480
at the nine millisecond range, but there was a weird jump at six milliseconds performance

00:17:00.480 --> 00:17:03.480
where at six milliseconds of added input latency,

00:17:03.480 --> 00:17:08.200
the average performance was higher than zero, which made zero sense,

00:17:08.200 --> 00:17:11.640
not logically, not intuitively, but I wasn't really satisfied with that.

00:17:11.640 --> 00:17:15.080
So I tested another like 14, 15 people. Oh.

00:17:15.080 --> 00:17:17.360
Those results were weirder.

00:17:18.360 --> 00:17:23.000
And so it goes down at three milliseconds, up a little bit again at six milliseconds,

00:17:23.000 --> 00:17:27.080
and then down to almost the same at nine. So nine and three are almost identical.

00:17:27.080 --> 00:17:31.840
So I started to be wonder, does it not matter below 10 milliseconds?

00:17:31.840 --> 00:17:36.000
But then I separated top performers from bottom performers.

00:17:36.000 --> 00:17:40.000
Oh. And in the top performers, it's a super clear line,

00:17:40.000 --> 00:17:43.920
like undeniably just 3% each added three milliseconds.

00:17:43.960 --> 00:17:48.200
So if you're any good, then functionally speaking,

00:17:48.200 --> 00:17:51.520
there is no limit to how low you want your latency to be.

00:17:51.520 --> 00:17:56.680
Yeah. We could try to get a system that would get us less than the 12 and a half that we were testing with.

00:17:56.680 --> 00:18:01.160
Right. But it's not a realistic scenario. And for the best gamers though,

00:18:01.160 --> 00:18:04.520
that could potentially make it ever. See, I was not expecting this. Me neither.

00:18:04.520 --> 00:18:08.240
I was hoping that this video would tell people that it's really your gaming skill.

00:18:08.240 --> 00:18:11.280
That's the problem. Like your peripherals are fine, but what I found out is that.

00:18:11.280 --> 00:18:15.080
And that is, wait, and that is true to a degree. Yes.

00:18:15.080 --> 00:18:21.960
I mean, you saw how much latency we had to add to either Canada or a typical gamer, right?

00:18:21.960 --> 00:18:28.000
For me to have any shot of hitting them. But if you have the game sense or what did,

00:18:28.000 --> 00:18:32.080
what did Canada call it? Oh, awareness. You gotta find awareness on it.

00:18:32.080 --> 00:18:36.760
You saw that, right? You saw that shot? Awareness, just a negative awareness.

00:18:36.760 --> 00:18:39.800
Then there is no limit functionally that we found.

00:18:39.800 --> 00:18:43.320
No, we can confidently say that as little as three milliseconds

00:18:43.320 --> 00:18:48.960
impacts gaming performance for high, not even high, above average gamers.

00:18:48.960 --> 00:18:52.040
Huh. It's the takeaway that I find interesting

00:18:52.040 --> 00:18:55.400
is that most peripherals now are pretty low latency.

00:18:55.400 --> 00:18:58.720
Gaming mice are. Sub one millisecond. Sub one millisecond, if they're good.

00:18:58.720 --> 00:19:02.480
But I bet there's a lot of you out there that are playing competitive games on Bluetooth mice

00:19:02.480 --> 00:19:07.040
or on the wrong monitor mode. Monitors are often the biggest source of input latency.

00:19:07.040 --> 00:19:11.160
If you're gaming on a display that also has a film mode, make sure you are off that.

00:19:11.160 --> 00:19:14.240
Because that's how you get to 100 milliseconds of delay.

00:19:14.240 --> 00:19:17.760
And that was enough to get you on level with a pro gamer.

00:19:17.760 --> 00:19:23.560
Right. And when we say source of input latency, we mean because technically it's not the input,

00:19:23.560 --> 00:19:27.560
but it's the input to your eyes that will affect when you put your input in.

00:19:27.560 --> 00:19:30.800
It also makes sense that all the eSports teams are all in the same cities

00:19:30.800 --> 00:19:35.040
because that 25 milliseconds extra of LA to Dallas

00:19:35.040 --> 00:19:38.840
is enough to drastically affect your performance.

00:19:38.840 --> 00:19:43.240
Well, there it is. I mean, ASUS will be happy about that. PC gaming, is it pay to win?

00:19:45.000 --> 00:19:48.560
Well, if you have the awareness, then yes.

00:19:48.560 --> 00:19:52.000
If you don't, then there's not much you can do about it.

00:19:52.000 --> 00:19:57.480
I was kind of hoping there'd be some ambiguity here because obviously ASUS sponsored the video

00:19:57.480 --> 00:20:01.360
and it's in their best interest for lower latency, high performance peripherals

00:20:01.360 --> 00:20:05.760
to make a difference to gaming. Just like we would, sponsored or not,

00:20:05.760 --> 00:20:10.320
all we're doing is giving you guys the results that we have, semi-scientific as they are.

00:20:10.320 --> 00:20:13.440
You can check out. We'll have maybe some downloads of the graphs

00:20:13.440 --> 00:20:16.520
if you guys wanna see them down below. Oh yeah, for sure. Yeah, we'll have a little package for you guys.

00:20:16.520 --> 00:20:20.160
We'll also have links to all the products that we use down there in the video description.

00:20:20.160 --> 00:20:24.000
Or you can check out the LTC Labs website for our growing database of in-depth testing

00:20:24.000 --> 00:20:28.240
of gaming peripherals, including latency measurements of mice and keyboards.

00:20:28.240 --> 00:20:31.560
Huge thank you. Typical gamer, baby no money,

00:20:31.560 --> 00:20:36.000
and Kanata for joining us today. I had a ton of fun, at least as much fun

00:20:36.000 --> 00:20:39.040
as the last time we did a video like this, which maybe you should check out.

00:20:39.040 --> 00:20:42.120
It was more focused on how many frames per second you need

00:20:42.120 --> 00:20:46.680
before it affects gaming performance. And the results may surprise you

00:20:46.680 --> 00:20:52.040
if you completely weren't paying attention today. It turns out more is better.
