WEBVTT 00:00:00.160 --> 00:00:02.560 Unless you make a habit of living under a rock, 00:00:02.560 --> 00:00:06.080 or if you're just not that into gaming, that too, 00:00:06.080 --> 00:00:08.160 you've probably seen the headlines, 00:00:08.160 --> 00:00:12.560 AMD FreeSync working on GeForce cards. 00:00:12.560 --> 00:00:16.020 And it's true, but there's a catch. 00:00:16.020 --> 00:00:19.580 So the current methods for enabling FreeSync 00:00:19.580 --> 00:00:21.660 on a GeForce graphics card 00:00:21.660 --> 00:00:26.460 require you to also have an AMD GPU in your system 00:00:26.460 --> 00:00:30.060 that is capable of supporting FreeSync itself. 00:00:30.060 --> 00:00:32.960 So today's video then has us trying it out 00:00:32.960 --> 00:00:35.060 to see if it's worth the hassle 00:00:35.060 --> 00:00:39.340 to save money on a G-Sync monitor. 00:00:39.340 --> 00:00:41.580 And while we're at it, 00:00:41.580 --> 00:00:44.960 we were thinking maybe we'd try to run G-Sync 00:00:44.960 --> 00:00:46.980 on an AMD graphics card. 00:00:57.660 --> 00:01:00.020 Rosewill's new Prism S500 case 00:01:00.020 --> 00:01:02.500 lights the way with its array of RGB fans, 00:01:02.500 --> 00:01:03.480 tempered glass panel, 00:01:03.480 --> 00:01:04.280 and spacious, 00:01:04.280 --> 00:01:07.200 and you can even use it as a display in the interior. 00:01:07.200 --> 00:01:09.520 Click the link below to learn more. 00:01:09.520 --> 00:01:12.040 So let's start with how this works. 00:01:12.040 --> 00:01:14.840 There are actually two different ways to go about this. 00:01:14.840 --> 00:01:18.400 There's the GPU way and the APU way. 00:01:18.400 --> 00:01:21.840 So we'll be using the APU method for the uninitiated. 00:01:21.840 --> 00:01:25.600 And APU is AMD's name for a CPU 00:01:25.600 --> 00:01:28.520 that has a graphics processor built into it. 00:01:28.520 --> 00:01:30.400 Now, normally, as soon as you install 00:01:30.400 --> 00:01:32.040 a dedicated graphics card, 00:01:32.040 --> 00:01:33.700 your onboard graphics gets disabled, 00:01:33.700 --> 00:01:35.800 when you can use this. 00:01:35.800 --> 00:01:37.740 But for what we're doing, 00:01:37.740 --> 00:01:41.100 we actually need to force the Vega 11 GPU 00:01:41.100 --> 00:01:44.920 that's built into our Ryzen 5 2400G on. 00:01:44.920 --> 00:01:48.540 So we're gonna change IGFX multi-monitor to enabled, 00:01:48.540 --> 00:01:51.420 and we are going to set the primary video device 00:01:51.420 --> 00:01:53.820 to our onboard graphics. 00:01:53.820 --> 00:01:55.780 Let's go ahead and reboot. 00:01:55.780 --> 00:01:57.420 Now, while we wait for that to happen, 00:01:57.420 --> 00:02:00.720 let's talk about what's going on under the hood here. 00:02:00.720 --> 00:02:03.580 If you watched our gaming on Linux video a little while ago, 00:02:03.580 --> 00:02:06.880 we showed a piece of software called Looking Glass 00:02:06.880 --> 00:02:10.260 that Wendell from Level 1 Techs was using to game 00:02:10.260 --> 00:02:13.460 with very low latency in Linux 00:02:13.460 --> 00:02:16.940 by running the game effectively in a virtual machine 00:02:16.940 --> 00:02:20.520 that was running Windows and then capturing its output. 00:02:20.520 --> 00:02:25.040 TLDR, the API that Windows is using here is called DXGI. 00:02:25.040 --> 00:02:28.520 And what it does is essentially mirror the output 00:02:28.520 --> 00:02:32.540 from one card to another with very little delay. 00:02:32.540 --> 00:02:33.480 Though, there is no delay. 00:02:33.480 --> 00:02:35.160 There is still a delay. 00:02:35.160 --> 00:02:36.300 So as you can see here, 00:02:36.300 --> 00:02:39.360 we've already got our GeForce driver installed and working. 00:02:39.360 --> 00:02:40.680 So the next thing we need to do, 00:02:40.680 --> 00:02:42.300 we've already downloaded it here, 00:02:42.300 --> 00:02:46.080 is install the drivers for our Radeon graphics. 00:02:46.080 --> 00:02:48.220 Now that our Radeon drivers are installed, 00:02:48.220 --> 00:02:51.300 which, yes, is working correctly, 00:02:51.300 --> 00:02:54.240 we need to change our display configuration 00:02:54.240 --> 00:02:55.100 a little bit here. 00:02:55.100 --> 00:02:58.660 So what we want is our FreeSync monitor 00:02:58.660 --> 00:03:01.650 plugged into our onboard graphics, 00:03:01.650 --> 00:03:03.870 and we want nothing plugged 00:03:03.870 --> 00:03:06.630 into our GeForce graphics card. 00:03:06.630 --> 00:03:07.750 One cool thing, by the way, 00:03:07.750 --> 00:03:10.210 is that because of the way that this works, 00:03:10.210 --> 00:03:13.190 in theory, we could actually do the same thing 00:03:13.190 --> 00:03:15.870 with Intel's upcoming integrated graphics 00:03:15.870 --> 00:03:17.530 with FreeSync support. 00:03:17.530 --> 00:03:19.990 That's not confirmed at this time yet though. 00:03:19.990 --> 00:03:22.690 So now that all of this is done, 00:03:22.690 --> 00:03:24.810 we can go into our display settings. 00:03:24.810 --> 00:03:26.850 Then on the bottom, 00:03:26.850 --> 00:03:30.650 we're going to see an option here for graphic settings. 00:03:30.650 --> 00:03:33.550 Now, all we need to do is add whatever we want to run. 00:03:33.550 --> 00:03:35.330 We want to run here. 00:03:35.330 --> 00:03:37.790 Okay, so now we go into options, 00:03:37.790 --> 00:03:41.990 and then we just need to set our graphics preference. 00:03:41.990 --> 00:03:44.450 So we're going to set that to high performance, 00:03:44.450 --> 00:03:45.950 right about here. 00:03:45.950 --> 00:03:48.150 See, here's our power saving GPU. 00:03:48.150 --> 00:03:50.190 Here's our high performance one. 00:03:50.190 --> 00:03:53.350 Now, when we launch this demo, 00:03:53.350 --> 00:03:59.340 theoretically, FreeSync technology will work. 00:04:00.630 --> 00:04:02.030 We can actually test it too. 00:04:02.030 --> 00:04:03.450 Check this out. 00:04:03.450 --> 00:04:05.490 So let's go ahead and, 00:04:05.690 --> 00:04:08.160 turn AMD FreeSync off. 00:04:08.160 --> 00:04:10.720 Oh, we got to turn V-Sync off for one thing. 00:04:10.720 --> 00:04:12.680 Okay, there we go. 00:04:12.680 --> 00:04:13.580 That's more like it. 00:04:13.580 --> 00:04:18.540 Now let's turn FreeSync off and boom, there's our tearing. 00:04:18.540 --> 00:04:20.000 Let's go ahead and do an FPS sweep 00:04:20.000 --> 00:04:22.220 so we can get some really nasty tearing there. 00:04:22.220 --> 00:04:23.930 Yep. 00:04:23.930 --> 00:04:33.980 Now let's turn FreeSync back on. 00:04:33.980 --> 00:04:36.040 Okay, so let's try Counter-Strike. 00:04:36.040 --> 00:04:38.060 So V-Sync's off. 00:04:38.060 --> 00:04:40.700 Let's see how smooth this is. 00:04:40.700 --> 00:04:45.800 So in theory, this DXGI thing only adds about one to two 00:04:46.220 --> 00:04:48.540 milliseconds of additional lag. 00:04:48.540 --> 00:04:50.760 So for the people out there claiming they can feel 00:04:50.760 --> 00:04:52.320 the difference, okay, maybe, 00:04:52.320 --> 00:04:55.040 but you're probably super human because at 60 frames 00:04:55.040 --> 00:05:00.440 per second, that is, what does that work out to? 00:05:00.440 --> 00:05:03.100 Wait, oh wow, this feels like ass. 00:05:03.100 --> 00:05:05.620 I think this is running on the wrong GPU. 00:05:05.620 --> 00:05:09.450 So it's a little kludgy for every one of your, 00:05:09.450 --> 00:05:11.190 there we go, for every one of your programs, 00:05:11.190 --> 00:05:12.830 you're going to have to actually change that. 00:05:12.830 --> 00:05:14.710 Let's see if we can just re-maximize it 00:05:14.710 --> 00:05:16.980 and it'll run on the right one. 00:05:16.980 --> 00:05:18.420 Yeah, that super did not work. 00:05:18.420 --> 00:05:20.060 Let's try relaunching it. 00:05:20.060 --> 00:05:22.220 There we go. 00:05:22.220 --> 00:05:23.760 That's more like it. 00:05:23.760 --> 00:05:24.600 All right. 00:05:24.600 --> 00:05:29.570 I am getting a frigging mess ton of tearing here. 00:05:29.570 --> 00:05:30.770 When you're running FreeSync, 00:05:30.770 --> 00:05:33.270 are you supposed to enable V-Sync within the game? 00:05:33.270 --> 00:05:34.420 Yeah. 00:05:34.420 --> 00:05:35.920 Oh, well there's our problem. 00:05:35.920 --> 00:05:39.420 Also the developer console isn't enabled, crying out loud. 00:05:39.420 --> 00:05:41.820 One problem with CSGO though is that it's not demanding 00:05:41.820 --> 00:05:44.260 enough for us to dip below 60 frames per second. 00:05:44.260 --> 00:05:46.580 So it's not really giving us a benefit over just running V-Sync. 00:05:46.580 --> 00:05:50.320 Other than theoretically a little bit less lag. 00:05:50.320 --> 00:05:52.200 So what we're going to do then, 00:05:52.200 --> 00:05:54.660 is we're going to fire up Deus Ex Mankind Divided. 00:05:54.660 --> 00:05:56.620 Can really tell it's much smoother. 00:05:56.620 --> 00:05:59.450 Wow, I suck. 00:05:59.450 --> 00:06:00.450 All right. 00:06:00.450 --> 00:06:01.610 So here we go. 00:06:01.610 --> 00:06:04.430 Now we are right in the sweet spot 00:06:04.430 --> 00:06:06.830 where we're going to be benefiting from our FreeSync display 00:06:06.830 --> 00:06:10.090 where we're not quite able to maintain 60 frames per second, 00:06:10.090 --> 00:06:14.370 but we're right in that 45 to 50 FPS range. 00:06:14.370 --> 00:06:15.770 What kind of annoying thing about this game 00:06:15.770 --> 00:06:18.030 is it has some on-screen effects 00:06:18.030 --> 00:06:21.050 that kind of look like tearing, but we are not, 00:06:21.050 --> 00:06:24.980 oh, see like that, but that's not that, that's me dying. 00:06:24.980 --> 00:06:28.370 I can't believe that this is working. 00:06:28.370 --> 00:06:30.650 Like this just blows me away. 00:06:30.650 --> 00:06:31.490 Okay. 00:06:31.490 --> 00:06:34.130 So remember how I said that because of the way this works, 00:06:34.130 --> 00:06:37.950 we could in theory use Intel's iGPU for FreeSync 00:06:37.950 --> 00:06:41.290 with an NVIDIA card actually churning through the frames. 00:06:41.290 --> 00:06:44.210 Once those come out, that got us thinking, 00:06:44.210 --> 00:06:46.710 what if we did it the other way around? 00:06:46.710 --> 00:06:48.530 What if you're on team red? 00:06:49.050 --> 00:06:50.710 Like a Vega 64, 00:06:50.710 --> 00:06:55.720 but some baller new gaming monitor is only available 00:06:55.720 --> 00:07:10.090 in a G-Sync flavor. 00:07:10.090 --> 00:07:11.290 Wow, that happened so fast. 00:07:11.290 --> 00:07:12.690 I didn't even get a chance to show you guys. 00:07:12.690 --> 00:07:13.570 Check this out. 00:07:13.570 --> 00:07:16.310 So as soon as we plugged it in, boom, 00:07:16.310 --> 00:07:18.290 G-Sync display connected. 00:07:18.290 --> 00:07:20.060 What? 00:07:20.060 --> 00:07:21.560 So we'll go ahead and fire that up. 00:07:21.560 --> 00:07:24.500 Enable G-Sync, enable G-Sync for all the things. 00:07:24.500 --> 00:07:29.060 Now all we have to do is the same process, but in reverse, 00:07:29.060 --> 00:07:32.300 going into our graphic settings and going, okay, CS go. 00:07:32.300 --> 00:07:34.140 We don't want high performance. 00:07:34.140 --> 00:07:36.320 We want power saving. 00:07:36.320 --> 00:07:40.880 Now we can launch Counter-Strike. 00:07:40.880 --> 00:07:44.580 And in theory, we'll be running G-Sync 00:07:44.580 --> 00:07:46.480 for our NVIDIA graphics card, 00:07:46.480 --> 00:07:49.040 but we'll actually be rendering with our onboard graphics. 00:07:49.040 --> 00:07:54.040 Now that wouldn't make a lot of sense in this case, 00:07:54.040 --> 00:07:57.960 but if you were running something like a Vega 64, 00:07:57.960 --> 00:08:01.800 and then you just installed like a GeForce 950 or something 00:08:01.800 --> 00:08:02.960 in another slot, you couldn't do that. 00:08:02.960 --> 00:08:03.800 You couldn't do that. 00:08:03.840 --> 00:08:06.600 You could make it work. 00:08:06.600 --> 00:08:08.580 Whether or not you should make it work 00:08:08.580 --> 00:08:09.700 is another question though, 00:08:09.700 --> 00:08:14.700 because unless someone automates this GPU switching process, 00:08:15.580 --> 00:08:19.440 it is a bit of a pain in the butt, at least at this time. 00:08:19.440 --> 00:08:23.320 And it's not that cost-effective 00:08:23.320 --> 00:08:28.540 because one way or another, you will have to have two GPUs. 00:08:28.880 --> 00:08:30.120 Would you look at that? 00:08:30.120 --> 00:08:32.000 It feels a little laggy, 00:08:32.000 --> 00:08:35.060 but that's because we're running at 33 frames per second. 00:08:35.060 --> 00:08:36.340 There's no tearing, 00:08:36.340 --> 00:08:39.600 and it's as smooth as it could be given the situation. 00:08:39.600 --> 00:08:42.500 Now, one way that you could make the solution make sense 00:08:42.500 --> 00:08:45.300 would be if you had some old compatible hardware 00:08:45.300 --> 00:08:49.240 lying around, or actually maybe if you're team green 00:08:49.240 --> 00:08:51.020 in terms of your gaming rig, 00:08:51.020 --> 00:08:53.500 but you wanted to hook your gaming machine 00:08:53.500 --> 00:08:56.680 up to one of Samsung's FreeSync TVs, for example, 00:08:56.680 --> 00:08:59.600 because until BFGDs actually make their way to the market, 00:08:59.600 --> 00:09:03.540 there are no large format G-Sync displays. 00:09:03.540 --> 00:09:05.040 That could be pretty cool. 00:09:05.160 --> 00:09:06.780 But in most cases, 00:09:06.780 --> 00:09:08.820 you'll probably end up spending 00:09:08.820 --> 00:09:11.100 more than you are actually saving 00:09:11.100 --> 00:09:15.160 or very close for what isn't an amazing experience. 00:09:15.160 --> 00:09:18.240 The real takeaway is that we shouldn't have to do 00:09:18.240 --> 00:09:19.580 any of this. 00:09:19.580 --> 00:09:22.620 FreeSync and VESA Adaptive Sync 00:09:22.620 --> 00:09:25.140 are both industry standards at this point. 00:09:25.140 --> 00:09:28.560 And NVIDIA, if you're listening, 00:09:28.560 --> 00:09:31.220 we're not saying that you need to ditch G-Sync. 00:09:31.220 --> 00:09:35.160 We know that you guys have special green G-Sync socks, 00:09:35.160 --> 00:09:36.220 that you pour on it, 00:09:36.220 --> 00:09:39.540 that makes it a little better in your opinions. 00:09:39.540 --> 00:09:40.980 Personally, I haven't looked at it 00:09:40.980 --> 00:09:42.060 with a high speed camera yet, 00:09:42.060 --> 00:09:43.900 but you guys think it's better, so okay. 00:09:43.900 --> 00:09:48.620 We're just saying that like CUDA and OpenCL, 00:09:48.620 --> 00:09:51.500 there's no reason that you couldn't support both, 00:09:51.500 --> 00:09:53.980 especially since as we've demonstrated here, 00:09:53.980 --> 00:09:57.660 there's no physical link reason 00:09:57.660 --> 00:10:01.190 that you couldn't support both. 00:10:01.190 --> 00:10:05.630 Team Group is sponsoring this video with their Delta RGB SSD. 00:10:05.630 --> 00:10:09.190 Yes, my friends, it's an RGB SSD. 00:10:09.190 --> 00:10:10.890 They've got three versions available. 00:10:10.890 --> 00:10:13.510 So the USB gives off our rainbow wave, 00:10:13.510 --> 00:10:15.310 while the five volt and the 12 volt 00:10:15.310 --> 00:10:18.810 are able to be configured with a variety of RGB software. 00:10:18.810 --> 00:10:20.050 They've got read and write speeds 00:10:20.050 --> 00:10:22.130 of up to 560 megabytes per second. 00:10:22.130 --> 00:10:23.790 And this is pretty cool. 00:10:23.790 --> 00:10:26.430 If you click the link below, you can enter a giveaway 00:10:26.430 --> 00:10:30.630 and the winner can choose either a 500 gig Delta RGB SSD 00:10:30.630 --> 00:10:35.840 or their T-Force RGB 16 gig RAM kit. 00:10:35.840 --> 00:10:36.780 So thanks for watching guys. 00:10:36.780 --> 00:10:41.630 If this video sucked, then I see you NVIDIA employees. 00:10:41.630 --> 00:10:42.680 I see you. 00:10:42.680 --> 00:10:44.780 But if you liked it, you can hit the like button, 00:10:44.780 --> 00:10:46.400 get subscribed, or maybe consider checking out 00:10:46.400 --> 00:10:47.700 where to buy the stuff we featured 00:10:47.700 --> 00:10:49.320 at the link in the video description. 00:10:49.320 --> 00:10:50.460 Also down there is our merch store, 00:10:50.460 --> 00:10:51.820 which has cool shirts like this one 00:10:51.820 --> 00:10:54.660 and our community forum, which you should totally join.