WEBVTT 00:00:00.160 --> 00:00:05.920 Logitech brought us here to Switzerland to check out the G900 Chaos Spectrum. An 00:00:04.319 --> 00:00:09.840 interesting looking mouse, but with some really bold claims, especially when 00:00:07.680 --> 00:00:13.679 comparing it to a wired mouse, which traditionally would have been a lot 00:00:11.280 --> 00:00:17.920 better in like almost every possible metric. They claim, however, that it has 00:00:16.320 --> 00:00:25.100 now reversed. They're claiming that the G900 is better than a wired mouse. Let's 00:00:21.199 --> 00:00:31.519 do some science and figure it out. 00:00:31.519 --> 00:00:37.840 So, we're starting off in the RF Labs. This is probably one of the most important things about this mouse is its 00:00:36.480 --> 00:00:43.040 wireless performance. That's what they've been trumping really, really hard this whole time. So, we need to 00:00:41.360 --> 00:00:46.079 benchmark it. We're going to test it with huge amounts of interference, 00:00:44.719 --> 00:00:49.680 without interference, all this different kind of stuff, and see how it compares 00:00:47.760 --> 00:00:53.680 to other mice. We're going to do that by coming inside of an anooic chamber, but 00:00:51.680 --> 00:00:57.600 this time it's not an anooic chamber in terms of sound. It's an anooic chamber 00:00:55.440 --> 00:01:00.559 in terms of signals. So RF, Wi-Fi, Bluetooth, all that kind of stuff isn't 00:00:59.039 --> 00:01:05.280 going to be able to leave the room once the door is closed and isn't going to be 00:01:02.160 --> 00:01:06.720 able to come on into the inside. But to 00:01:05.280 --> 00:01:10.000 cause that interference, we have this antenna right here, which is going to be 00:01:08.400 --> 00:01:14.000 shooting out massive amounts of amplified RF, Wi-Fi, and Bluetooth 00:01:12.159 --> 00:01:19.280 signals. What they did was they went to a LAN of about 300 people, measured the 00:01:16.799 --> 00:01:23.600 signal noise, and then amplified that by a little bit more to make a crazy worst 00:01:21.600 --> 00:01:26.960 case scenario. Over on the other side of the room, there's all this foam kind of 00:01:25.119 --> 00:01:29.920 stuff everywhere. That's so that signals aren't bouncing around throughout the 00:01:28.320 --> 00:01:33.360 room, and you just get a solid trajectory, so it's better and more 00:01:31.600 --> 00:01:37.920 consistent for measurement. Here we have the mouse rig. So, this is a jogger that 00:01:35.920 --> 00:01:42.079 keeps a pad moving under the mouse so that the uh actual sensor is constantly 00:01:40.479 --> 00:01:48.399 firing and sending information, which is important because you need the mouse to be actually working. And then the mouse 00:01:44.960 --> 00:01:50.799 is held in place above that. Across the 00:01:48.399 --> 00:01:55.040 room a little bit right here is the receiver. So, this guy is actually 00:01:53.200 --> 00:01:59.360 talking to the mouse. That wire goes through a tube to the outside and then 00:01:56.799 --> 00:02:02.640 we're measuring actually the tracking of the mouse out there where the actual 00:02:01.280 --> 00:02:06.320 interesting stuff is. So, let's check that out. So, as you can see back here 00:02:04.320 --> 00:02:11.760 on the spectrum analyzer, they have a crazy amount of noise being fired in 00:02:08.720 --> 00:02:13.680 that room right now. But over here, you 00:02:11.760 --> 00:02:17.520 can see a tracking tester where it's just tracing the cursor movement of the 00:02:15.520 --> 00:02:21.200 mouse as that jogger is going around. And it is in a very I'm going to reset 00:02:19.360 --> 00:02:24.640 this. You can see it drawing. It isn't a very consistent kind of pattern, which 00:02:23.200 --> 00:02:30.480 is good. There's going to be some drift from the sensor, but that's actually fine. All sensors have some amount of 00:02:27.920 --> 00:02:33.360 drift. Um, but the good thing about it is that it's consistent. It's not going 00:02:31.920 --> 00:02:37.360 all over the place. And if you're not making robotic exact circular movements, 00:02:36.000 --> 00:02:43.280 it's going to be extremely predictable where everything's going to be anyway. So, this is a good sign. And this is for 00:02:41.200 --> 00:02:46.640 the G900. So, now we're testing the Razer Mamba. Exact same scenario. This 00:02:45.519 --> 00:02:51.040 time we're going to try it with the signal noise on and with the signal 00:02:48.720 --> 00:02:55.280 noise off so you can see what it is in a more perfect scenario. The Mamba is 00:02:53.519 --> 00:02:59.760 currently set up and good to go. Powered on. Jogger is running. Antenna is over 00:02:57.519 --> 00:03:03.599 here. Let's go check the results. All right, so the Mamba 2015 is hooked up 00:03:01.599 --> 00:03:07.120 inside. That's what's running right now on the tracking tester. As you can see 00:03:05.519 --> 00:03:10.800 on the spectrum analyzer in the back, there's nothing really going on. That's 00:03:08.560 --> 00:03:16.560 because we have the antenna off. So, what I'm going to do is come back here, 00:03:13.599 --> 00:03:21.120 crank the antenna on. So, I'm going to turn this dial a little bit there. 00:03:18.800 --> 00:03:24.879 That's all good to go. The spectrum is now crazy. You'll see it actually moves 00:03:23.200 --> 00:03:27.920 where it's where it's kind of firing huge amounts of spectrum. So, it's not 00:03:26.319 --> 00:03:31.599 going to be a consistent problem. You can already see on here. I'm going to 00:03:29.920 --> 00:03:36.159 reset it so that we have some more room to actually see it get messed up. But, 00:03:34.480 --> 00:03:39.760 it's jumped all over the place. These lines that you see is where it stopped 00:03:38.239 --> 00:03:43.760 tracking completely for a second and then engaged back in somewhere else. You 00:03:41.840 --> 00:03:46.879 can see that instead of just simple sensor drift, it's actually jumping all 00:03:45.519 --> 00:03:52.000 over the place. I'm going to reset it here. It's going okay at the start, but 00:03:49.360 --> 00:03:56.560 then you see one big jump there. I'll wait for it to do a few more. 00:03:54.480 --> 00:04:00.720 There's one jump right there. So, there's going to be bad spots. Sometimes 00:03:58.319 --> 00:04:04.080 it'll be okay because maybe it's away from where the antenna is firing huge 00:04:02.400 --> 00:04:06.799 amounts of information. But then other times, as you saw before, it might 00:04:05.680 --> 00:04:11.760 actually start jumping all over the place because it's kind of getting overpowered, which is not very good. So, 00:04:10.319 --> 00:04:18.239 there's a line there. There's another line there. It's getting a little bit worse now. Yeah. So, that's the Mamba 00:04:15.360 --> 00:04:22.079 2015. Let's move on. All right. Next up on the chopping block is the Oraoros. A 00:04:20.479 --> 00:04:25.120 little bit of an older mouse. It's currently running on the jogger. Its 00:04:23.600 --> 00:04:28.240 sensor is currently over here. We're good to go. One other little bit of 00:04:26.880 --> 00:04:32.160 information that I want to give you guys is this is the antenna that's receiving 00:04:30.320 --> 00:04:36.000 the signal. So when we show you guys the spectrum analyzer, this is the thing 00:04:34.160 --> 00:04:40.400 that's outputting that information just in case you're interested. So next up, 00:04:37.919 --> 00:04:43.520 Razer Orbus. That's on the inside right now. You see it going with nothing 00:04:42.320 --> 00:04:47.199 really happening on the spectrum analyzer. Seems fine. A little bit of 00:04:45.759 --> 00:04:51.440 sensor drift, which is completely normal. Now let's hurt it a little bit. 00:04:49.520 --> 00:04:55.400 So going to turn things up. 00:04:55.759 --> 00:05:03.440 There we go. Spectrum analyzer is going like crazy. Stuff sweeping across like 00:04:59.520 --> 00:05:05.360 we saw before. Moving back. Now that 00:05:03.440 --> 00:05:09.440 happy little bit of sensor drift is no longer really very happy. As you can 00:05:07.120 --> 00:05:13.600 see, there's already two major jumps and it's completely changed direction. Three 00:05:11.440 --> 00:05:19.360 major jumps now. Yeah. So, not the clean nice patterned 00:05:17.199 --> 00:05:26.160 thing that we saw with the G900. It's a little bit more of a mess. Now looking 00:05:20.880 --> 00:05:28.080 back, there's 1 2 3 4 5 six major jumps, 00:05:26.160 --> 00:05:31.600 I think. And instead of just drifting nicely upwards like it was before, 00:05:29.840 --> 00:05:35.120 you're going up and then cranking way over to the right. And it's probably 00:05:33.199 --> 00:05:39.759 going to screw up again later on. Not the end of the world, but not perfect. 00:05:37.520 --> 00:05:43.440 Last, but potentially not least, is the Sensei. So, we have the Sensei rigged up 00:05:41.600 --> 00:05:47.280 on the jogger, and we have its receiver on the other side. Something to notice 00:05:45.600 --> 00:05:51.440 about the configuration of things as well. The receivers are always placed in 00:05:49.440 --> 00:05:54.880 line with the very front of the mouse. And the way that the jogger works, 00:05:53.039 --> 00:05:59.199 there's little arms going all the way around so that it can hold it in place 00:05:56.880 --> 00:06:02.880 perfectly despite the movement of the actual jogger. And it doesn't have to 00:06:01.520 --> 00:06:07.440 press any buttons. So, it's not pressing left or right buttons. It's not pressing the back button. So, it's not doing any 00:06:05.919 --> 00:06:12.880 of that kind of stuff. And it's holding it in place, which is pretty cool. So, 00:06:09.520 --> 00:06:14.400 the Sensei isn't doing so great. You can 00:06:12.880 --> 00:06:20.240 see on the spectrum analyzer there's nothing really going on. We basically 00:06:16.240 --> 00:06:23.840 have it off. Um, and that's not just 00:06:20.240 --> 00:06:26.080 simple normal nice unified sensor drift. 00:06:23.840 --> 00:06:30.240 That's quite messy. Let's start over again somewhere clean. Give it a nice 00:06:27.759 --> 00:06:34.919 clean slate and then hit it with the antenna as hard as we can go 00:06:35.120 --> 00:06:42.639 just to see what happen. Wow. Okay. So, this one 00:06:40.080 --> 00:06:45.600 that is just that is horrible. So, one of the interesting things that this one 00:06:44.080 --> 00:06:50.400 does that none of the other ones actually had a problem with is you can 00:06:47.600 --> 00:06:55.440 see the lines get kind of squiggly and they start doing weird spirals and 00:06:53.280 --> 00:07:01.440 actually making things that aren't at all the shape of what it's doing, which 00:06:57.360 --> 00:07:03.599 is a huge unusable problem. Again, 00:07:01.440 --> 00:07:07.919 something to remember, this is an insane worst case scenario. It's beyond like a 00:07:06.080 --> 00:07:12.639 normal kind of worst case scenario because they went from a like 300 person 00:07:10.720 --> 00:07:17.280 computer LAN, which is an insane scenario for any wireless device, then 00:07:14.800 --> 00:07:20.960 made it a little bit harder. But this thing is completely failing. The other 00:07:19.120 --> 00:07:26.960 ones were failing pretty hard, and the G900 had zero issues whatsoever. So, I 00:07:24.960 --> 00:07:31.199 think that's pretty cool. So, to create the device, the G900 that beats all of 00:07:29.440 --> 00:07:35.280 the other devices in this crazy worst case scenario test, it takes a lot of 00:07:33.039 --> 00:07:38.800 things. skills, science, testing, all that kind of stuff. It's not just buy 00:07:37.440 --> 00:07:42.880 the better thing, put the better thing in, and then you have a better object. 00:07:40.960 --> 00:07:47.520 It's not that simple. So, what they do is they use simulators in order to test 00:07:45.680 --> 00:07:51.520 what the actual end result is going to be. That's not always perfect, and just 00:07:50.319 --> 00:07:56.560 putting something in there and running a simulator won't magically solve all of your problems. That's where the skill 00:07:54.720 --> 00:08:01.680 component comes in. They're able to get their RF simulator results to be 00:07:58.879 --> 00:08:05.919 extremely similar to their actual measurement through skill. That's 00:08:03.919 --> 00:08:09.919 extremely important because it helps with your iteration process. That way, 00:08:07.759 --> 00:08:13.120 you don't have to build a new full device every single time you want to 00:08:11.520 --> 00:08:17.199 test it, which is going to help a lot because they have to release a product 00:08:14.960 --> 00:08:21.840 sometime. Then they also have to pay attention to where different components 00:08:19.039 --> 00:08:26.400 within the mouse go, like the battery. battery is a huge deal. With some older 00:08:24.160 --> 00:08:30.319 mice that even Logitech had, the positioning of the battery could cause 00:08:28.080 --> 00:08:33.519 weak spots in your signal as it went around. But the sizing and the 00:08:32.159 --> 00:08:39.279 positioning of this battery is a little bit better. They they have it on a different Z-axis within the mouse so 00:08:37.120 --> 00:08:43.440 that the emitter should be able to have a strong signal going all the way 00:08:40.800 --> 00:08:47.440 around. Super cool. Next up, we've got the sensor lab. So, what we're going to 00:08:44.880 --> 00:08:52.080 be doing here is testing motion latency. So, how long it takes for you a movement 00:08:50.480 --> 00:08:56.399 of the mouse to actually go to the computer. We're not worried about the less rest of the latency in the system. 00:08:54.800 --> 00:09:00.560 This is just what Logitech would have control over. So, we're going to do that 00:08:58.480 --> 00:09:04.880 by coming in here and using this turntable. The service on here is just 00:09:02.480 --> 00:09:08.320 like a Steel Series QCK type surface. So, probably something that's pretty 00:09:06.480 --> 00:09:13.279 common in someone's home. We're going to start with the Logitech G900, which is 00:09:10.640 --> 00:09:17.360 already on here. It's not torqued down. It's not too light. It's just kind of 00:09:15.440 --> 00:09:20.080 exactly how much someone would be pushing down on the surface cuz you 00:09:18.720 --> 00:09:24.160 don't want to grind against the mouse pad. You don't want to do anything like that. That would mess up with the 00:09:22.080 --> 00:09:27.680 results. Next up, we'll have a Razer Chroma, which is actually a wired mouse. 00:09:26.080 --> 00:09:32.160 So, we'll compare it against that. And then we have a Mamba 2015, which is 00:09:30.080 --> 00:09:38.000 another competitor wireless mouse. There's a little bit of plus minus here. 00:09:34.800 --> 00:09:39.680 that it could be plus 0 to 1 millisecond 00:09:38.000 --> 00:09:43.600 or anywhere in between due to polling rate. But spoiler alert, it's going to 00:09:41.360 --> 00:09:47.760 win by more than that. So, it doesn't really matter. Another thing I forgot to 00:09:45.279 --> 00:09:53.279 mention is that the mouse is placed very specifically on the turntable mouse pad. 00:09:50.320 --> 00:09:57.200 It's placed at a 45° angle so that X and Y axis are contributing the exact same 00:09:55.600 --> 00:10:01.040 amount. They have to be very precise about these things cuz extra variables 00:09:59.200 --> 00:10:05.040 like that could screw with something in a way that would mess up your results. 00:10:02.720 --> 00:10:09.279 So they have the right amount of tension down, they have the right angle, and 00:10:07.440 --> 00:10:12.080 they have a huge amount of samples, all of which are good. All right. So we're 00:10:10.800 --> 00:10:16.800 going to run our first test here. You can go right now. And what you'll see on 00:10:14.959 --> 00:10:20.880 the screen in a moment is it's going to accumulate data over time. So what's 00:10:18.959 --> 00:10:25.040 actually going to be displayed graphically is rounded a little bit just 00:10:23.360 --> 00:10:30.079 more for presentation so that you can kind of see whereabout things are. But 00:10:27.440 --> 00:10:33.600 below that is more of the hardcore math. No rounding and you can see the mean. 00:10:32.000 --> 00:10:38.320 So, we have to wait a little bit for it to gather some data and then we'll give 00:10:35.440 --> 00:10:44.000 you a more accurate mean. So, after taking 33 samples of movement, the mean 00:10:40.959 --> 00:10:46.399 latency was 4.79 00:10:44.000 --> 00:10:49.600 milliseconds. So, that might not sound impressive yet, but just wait till we 00:10:47.920 --> 00:10:53.839 try the other mice. So, we're about to run test two. This is against the Razer 00:10:51.760 --> 00:10:57.279 Chroma, which is actually a wired mouse. You can see here in the device info, it 00:10:55.519 --> 00:11:01.519 is in fact the Razer Chroma. We're going to be comparing it against our previous 00:10:59.040 --> 00:11:05.760 file, which was running the G900. So, we're going to have blue data showing up 00:11:03.760 --> 00:11:10.160 on the chart. That's for the previous mouse. And the green data you, as you 00:11:08.560 --> 00:11:14.560 can see in here, color green, will be actually for the Chroma. So, let's run 00:11:12.480 --> 00:11:19.680 the test. So, we have our first result, the G900 versus the Razer Chroma. As you 00:11:17.760 --> 00:11:24.000 can see here, the green is much higher than the blue, which means that the 00:11:21.279 --> 00:11:29.680 green lost. This is motion latency. So, you want a low number. As you can see, 00:11:26.240 --> 00:11:31.519 the median for the G900 was 4.8, as we 00:11:29.680 --> 00:11:35.279 already discussed. The blue is the same numbers that we had running on our 00:11:32.880 --> 00:11:40.959 previous test, but the mean for the chroma is about 6.88, 00:11:38.399 --> 00:11:45.680 which is 2 milliseconds more, which is a lot because you have to pay attention to 00:11:43.920 --> 00:11:50.160 each segment of your latency throughout the entire entire uh equation. So, your 00:11:48.560 --> 00:11:55.519 graphics card, your monitor, your mouse, all that kind of stuff. And reducing 00:11:52.079 --> 00:11:57.440 each one by relatively small amounts is 00:11:55.519 --> 00:12:01.120 a huge deal. So, you can get the total number lower. So having Logitech's 00:11:59.360 --> 00:12:05.440 number of the input from their mouse due to motion lower is good. And that means 00:12:03.839 --> 00:12:08.639 that it's lower than a wired mouse, which is pretty damn impressive. Another 00:12:06.959 --> 00:12:13.600 kind of cool thing to look at is that the lowest, so the fastest rate at which 00:12:11.839 --> 00:12:20.560 the motion was able to go from the mouse to the computer for the Razer mouse was 00:12:16.320 --> 00:12:22.880 about 5.5, which tied the highest or 00:12:20.560 --> 00:12:26.720 worst result from the G900. Just kind of a fun little tidbit. So this time the 00:12:24.880 --> 00:12:30.639 mouse we are testing is the Razer Mamba. As you can see in the top, we're 00:12:28.160 --> 00:12:35.200 comparing it yet again against the G900. So the compare with file is the original 00:12:32.639 --> 00:12:39.440 G900 test that we ran again. We're doing 33 33 trials, the exact same that we're 00:12:37.839 --> 00:12:44.320 doing every time. This time it's going to show up as pink. So yeah, let's get 00:12:41.760 --> 00:12:50.480 started. Okay, so we're done testing the Mamba 2015. And this is kind of why I 00:12:47.920 --> 00:12:54.240 haven't liked wireless mice in the past and probably why a lot of people haven't 00:12:51.920 --> 00:12:58.399 either. Look at the data. It's a mess. You've got results from 0.5, which are 00:12:56.480 --> 00:13:04.320 junk data. We'll explain why that's junk data in a moment, all the way up to 00:13:00.480 --> 00:13:06.639 18.5, which is probably caused due to 00:13:04.320 --> 00:13:10.560 lag in the transmission of data over the wireless signal. If it if it misses a 00:13:08.880 --> 00:13:15.440 report and then has to do it later, it's going to be massively delayed. your mean 00:13:12.880 --> 00:13:22.959 is at about 9.3 which is much higher than the 4.79 00:13:19.200 --> 00:13:25.360 of the G900 but probably more within the 00:13:22.959 --> 00:13:30.560 actual capabilities of the sensor. The problems with the junk data and the 00:13:27.360 --> 00:13:32.800 really really high late reported data is 00:13:30.560 --> 00:13:36.800 more due to the implementation of the sensor instead of the standard 00:13:34.480 --> 00:13:40.000 capabilities. Last but not least, we have click latency. So realistically, 00:13:38.639 --> 00:13:43.360 what all of these different stations have been explaining is that we don't 00:13:41.920 --> 00:13:47.360 necessarily need to be afraid of wireless anymore. I was afraid of 00:13:45.839 --> 00:13:51.760 wireless before, but I think that was justified before this mouse came out 00:13:49.440 --> 00:13:56.079 because, as we've seen, there were some problems with wireless mice. Now, click 00:13:53.519 --> 00:13:59.120 latency would be a huge one if it was worse than say a wired mouse. So, what 00:13:57.760 --> 00:14:04.399 we're going to do here is actually measure that. So, I'll explain how we'll do that. Now, they have a wire going 00:14:02.959 --> 00:14:08.240 into here, but you can see that it's not the actual normal one. This is wired 00:14:06.240 --> 00:14:13.040 directly into the switch instead of actually um the mouse itself so that you 00:14:11.440 --> 00:14:19.120 have your wireless adapter still running. That has been done on the G900, 00:14:16.079 --> 00:14:20.720 a Rival 300, and a Razer Chroma. So, you 00:14:19.120 --> 00:14:28.160 can see there's two wires going into each one of these cuz these are more naturally wired mice. Now, I'm going to 00:14:24.000 --> 00:14:30.880 move these guys out of the way. This uh 00:14:28.160 --> 00:14:36.480 wire from the switch is going into a signal adapter. This then sends it to a 00:14:34.399 --> 00:14:43.279 latency measurer. So what this one is recording off the bat is exactly when 00:14:39.600 --> 00:14:45.760 the uh switch is pressed. Um and then it 00:14:43.279 --> 00:14:51.360 starts a timer from that point in time to when this adapter is able to send the 00:14:48.560 --> 00:14:55.839 signal to the USB analyzer. So that's when it actually receives the signal 00:14:53.680 --> 00:14:59.199 that the switch was pressed because that one isn't wired in. That's a wireless 00:14:57.519 --> 00:15:03.920 signal. So you get to see the total latency of the mouse within your system. 00:15:01.920 --> 00:15:07.600 Similar to how we were testing total latency of the mouse in previous 00:15:05.920 --> 00:15:10.959 sections. This isn't the total latency until something would appear on your 00:15:09.760 --> 00:15:16.720 screen because there's other things within that equation like your graphics card and your monitor and whatnot, but 00:15:14.000 --> 00:15:20.399 this is what Logitech can control. So in order to actually run the test, they set 00:15:18.720 --> 00:15:25.360 up this kind of game thing where you go click on the lit up circle. This is just 00:15:23.199 --> 00:15:29.519 causing you to click a number of times at different intervals so it can be 00:15:27.199 --> 00:15:32.880 recorded over here. Much like the motion testing, motion latency testing that we 00:15:31.199 --> 00:15:35.839 did earlier. It'll show up a graph which will have some slightly rounded numbers, 00:15:34.560 --> 00:15:43.279 but we'll give a good visual representation of the results. So, we're going to run this about 30 clicks and 00:15:39.760 --> 00:15:45.199 then get a result after that. 00:15:43.279 --> 00:15:49.920 So, as you can see graphically, our average is at about 4.5. It kind of all 00:15:48.079 --> 00:15:55.279 huddles in a nice bell curve right around that area. And our mathematical 00:15:52.639 --> 00:16:01.040 not really rounded as much average is at about 4.3. Surprisingly similar to the 00:15:58.480 --> 00:16:05.440 latency in our motion input latency test. So yeah, let's move on and try the 00:16:03.440 --> 00:16:09.680 other mice. The first contender is the Steeler Rival 300, which has its 00:16:07.600 --> 00:16:14.000 firmware updated to the most recent one since last Friday. It's a wired mouse, 00:16:11.680 --> 00:16:18.399 so theoretically up until now, it should be faster. So we'll see if it reigns and 00:16:16.399 --> 00:16:21.519 holds that title. Let's begin the results and then compare it against the 00:16:19.600 --> 00:16:27.519 G900. Okay, so looking up here, we can see the 00:16:24.320 --> 00:16:29.519 blue data is from the Logitech G900. The 00:16:27.519 --> 00:16:35.440 green data is from the Steel Series Rival 300. Um, you can see again the 00:16:33.120 --> 00:16:42.800 mean or general average from the Logitech G900 was about 4.5 and now with 00:16:39.759 --> 00:16:44.880 the Rival 300, it's kind of less of a 00:16:42.800 --> 00:16:49.040 more perfect bell curve. The mean looks somewhere around 7.5, though. Moving 00:16:46.880 --> 00:16:53.279 over to the actual math of things, it looks like the average is, yeah, about 00:16:50.399 --> 00:16:58.000 7.6, which is a pretty significant increase, which is not good. You want a 00:16:55.680 --> 00:17:02.079 lower number again. It's more like golf. So, it's not over yet. Let's try one 00:17:00.000 --> 00:17:05.520 more. So, the program can only store two sets of data at a time. So, for round 00:17:04.000 --> 00:17:12.720 three, I'm actually going to have to redo the G900. So, here we go. G900 test 00:17:09.520 --> 00:17:16.720 two, and then the G900 test two will be 00:17:12.720 --> 00:17:20.240 compared against the Razer Chroma. 00:17:16.720 --> 00:17:22.079 Okay, so that's not really very good for 00:17:20.240 --> 00:17:28.400 the other team. Uh, looking at the graphical average now, it's probably at 00:17:24.480 --> 00:17:30.480 like a little bit below 11. And uh, 00:17:28.400 --> 00:17:36.799 yeah, that's about right. 10.9 milliseconds compared to 4.29. 00:17:34.000 --> 00:17:40.960 Sounds like wireless wins. Okay, that was actually kind of awesome. Uh, I'm 00:17:39.840 --> 00:17:47.200 pretty convinced. Let me know what you guys think in the comments down below or on Twitter at Luke Lafr. Thank you to 00:17:45.280 --> 00:17:51.520 Logitech for sending us here. If you guys want to see more stuff, click up 00:17:49.919 --> 00:17:55.360 here. We've got videos that we show. Usually, this goes at the end of the 00:17:53.440 --> 00:17:58.000 outro. This I'm switching the game up. It's going to the beginning this time. 00:17:56.799 --> 00:18:03.039 Like the video if you liked it. Dislike the video if you disliked it. Be sure to stay subscribed so you can see all of 00:18:01.120 --> 00:18:06.240 our Linus Tech Tips content. If you want to use our Amazon affiliate code, that's 00:18:04.640 --> 00:18:10.240 cool. You can buy stuff. We get a fun kickback. It's all nice. If you want to check out the forum, become a 00:18:08.960 --> 00:18:13.830 contributor there. That's super helpful. And if you want a shirt, check out the description down below. See you guys 00:18:12.880 --> 00:18:16.080 next time.