WEBVTT

00:00:00.080 --> 00:00:04.799
you want a faster GPU how do you get one

00:00:03.120 --> 00:00:08.000
well instead of turning your air conditioning into a chiller AMD wants

00:00:06.960 --> 00:00:11.360
you to fiddle with the settings uh

00:00:10.480 --> 00:00:15.920
yeah according to them you can get 40

00:00:14.080 --> 00:00:21.359
more performance out of your existing hardware without spending a dime and AMD

00:00:19.039 --> 00:00:27.320
sponsored this video so that we could go through their numbers and explain to you

00:00:23.760 --> 00:00:27.320
how to do it

00:00:33.920 --> 00:00:40.480
all right let's imagine you're AMD and you're trying to make the next fastest

00:00:38.160 --> 00:00:45.040
GPU in the world what do you do well in the past you leaned on two

00:00:42.800 --> 00:00:49.200
things to increase your performance more transistors and if that didn't work more

00:00:48.079 --> 00:00:53.680
power the problem is adding more transistors

00:00:51.520 --> 00:00:56.559
and power will be impossible unless you want to enter big dumb territory at this

00:00:55.760 --> 00:01:02.079
point right now high-end gpus draw close to

00:00:59.039 --> 00:01:05.360
500 watts you know what also draws 500

00:01:02.079 --> 00:01:07.760
watts this 500 watt space heater

00:01:05.360 --> 00:01:12.159
unlike Linus my computer room isn't very big so in the summer i have to seriously

00:01:10.000 --> 00:01:16.400
undervolt my system to avoid poaching in my own sweat until i move there's just

00:01:14.640 --> 00:01:21.439
no way that i'm buying a card with an over 350 watt TDP i'm sure i'm not the

00:01:19.439 --> 00:01:24.880
only one even if the raw heat output isn't a problem people in the office

00:01:23.280 --> 00:01:28.799
have actually heated their homes by mining in the winter so i guess it's a

00:01:27.360 --> 00:01:33.200
feature not a bug in north america we've got garbage 120

00:01:31.439 --> 00:01:38.000
volt power out of most of our outlets meaning that from a single circuit you

00:01:34.960 --> 00:01:39.439
can get 1800 watts max we're actually

00:01:38.000 --> 00:01:44.720
getting close to the point where desktops will need a dedicated circuit

00:01:42.240 --> 00:01:50.079
like forget plugging in a blender or a vacuum on the same circuit as your pc

00:01:47.200 --> 00:01:54.720
now in europe they use 240 volt power so overloading a circuit is less of a

00:01:51.680 --> 00:01:57.119
problem for them however european wars

00:01:54.720 --> 00:02:02.880
have been pretty bad for energy prices lately and they've gone from high to

00:01:59.680 --> 00:02:04.799
absolutely insane if gpus get any more

00:02:02.880 --> 00:02:10.080
power hungry it could get to the point where around a freaking war zone is

00:02:07.439 --> 00:02:14.000
gonna noticeably affect your power bill all right so if we can't feasibly add

00:02:12.319 --> 00:02:18.239
more power then we're gonna need more transistors and this is typically

00:02:15.840 --> 00:02:23.120
accomplished by physically shrinking the transistors i'm sure you're familiar by

00:02:20.319 --> 00:02:26.720
now with terms like 12 nanometer seven nanometer five nanometer and so on and

00:02:25.599 --> 00:02:33.120
so forth the problem is that the cost of developing new process nodes has gone

00:02:30.080 --> 00:02:34.640
from very expensive to oh my god that's

00:02:33.120 --> 00:02:39.040
a lot of money now to be clear chip makers are willing

00:02:37.280 --> 00:02:43.040
to make those investments but the process nodes are going to start

00:02:40.720 --> 00:02:46.560
sticking around for longer to ensure that they get a return

00:02:44.560 --> 00:02:51.440
AMD was able to get around this a bit by switching to 3d chip stacking in the

00:02:48.840 --> 00:02:55.840
5800x3d and i'm sure we'll be seeing way more 3d chip architectures in the future

00:02:53.760 --> 00:03:00.080
but that still isn't going to help us completely break the laws of physics

00:02:58.319 --> 00:03:04.480
we are getting scary close to the point where if you make transistors smaller

00:03:02.000 --> 00:03:07.760
quantum tunneling becomes a big problem now i'm not going to pretend to fully

00:03:05.840 --> 00:03:13.040
understand quantum tunneling but basically if the transistors are too

00:03:10.080 --> 00:03:17.360
small the electrons will sometimes just pass straight through have that happen a

00:03:15.440 --> 00:03:20.800
couple of times and mr blue screen is going to be paying you a visit

00:03:19.120 --> 00:03:25.040
all of this is to say then that in the future we're going to have to make games

00:03:22.480 --> 00:03:28.640
run faster by working smarter rather than harder and the first way that AMD

00:03:26.959 --> 00:03:34.720
is doing this is with smart access memory or sam the tl didn't watch about

00:03:31.840 --> 00:03:38.239
sam is that if you have an AMD CPU and a GPU

00:03:35.840 --> 00:03:42.319
go enable it right now and you could get a 5 to 10 performance improvement in

00:03:41.040 --> 00:03:50.959
many games how did AMD do this well in the past a CPU could only access

00:03:47.239 --> 00:03:53.440
256 megabytes of the GPU's vram at a

00:03:50.959 --> 00:03:58.480
time which was fine back when you were sneakily watching new grounds on the

00:03:55.200 --> 00:04:00.640
school computers but in 2022 your CPU

00:03:58.480 --> 00:04:04.959
should be able to access gigabytes of vram at a time and with smart access

00:04:02.720 --> 00:04:09.120
memory you can do just that to enable smart access memory simply hop

00:04:06.959 --> 00:04:13.200
into the BIOS make a detour to make sure that docp is enabled by the way that's a

00:04:11.200 --> 00:04:17.919
tech tip and then click this button right up here that says resize bar

00:04:15.760 --> 00:04:21.919
i don't know how common this button is so you might have to head over to

00:04:19.519 --> 00:04:26.639
advanced mode go to advanced pci subsystem settings and enable above 4g

00:04:24.160 --> 00:04:30.960
decoding then set resize bar support to auto and boom

00:04:28.720 --> 00:04:33.840
now your games run faster and you didn't have to spend any money you can

00:04:32.400 --> 00:04:38.000
celebrate by picking up a swag at ltdstore.com

00:04:36.160 --> 00:04:43.360
now sam might have been able to get frodo to mount doom nice joke love it by

00:04:40.400 --> 00:04:46.160
the way but it might not be enough to get you the frame rates that you're

00:04:44.560 --> 00:04:50.080
looking for that's where fidelity affects super resolution and Radeon

00:04:48.000 --> 00:04:56.240
super resolution come in they're both essentially the same idea except that

00:04:53.280 --> 00:05:01.120
fsr is optimized for specific gains and leaves hud elements at native resolution

00:04:58.639 --> 00:05:05.360
while rsr is implemented in the drivers and can be used on any game we'll be

00:05:03.520 --> 00:05:08.560
using fsr for the rest of the video unless i'm specifically talking about

00:05:07.360 --> 00:05:13.840
rsr basically what fsr does is render the

00:05:11.039 --> 00:05:18.880
game at a lower resolution then use a combination of ai and sharpening to fill

00:05:16.639 --> 00:05:22.000
back in the lost pixels this can give you a massive increase in performance

00:05:21.280 --> 00:05:27.680
like 10 to 50 depending on your settings

00:05:25.680 --> 00:05:32.160
but it does come with the caveat that you're going to be decreasing image

00:05:29.120 --> 00:05:33.440
quality the question is by how much

00:05:32.160 --> 00:05:37.919
and this is where i'd like to shout out AMD for a second typically for this kind

00:05:36.160 --> 00:05:43.280
of testing i would just set up a single computer and only test on that but AMD

00:05:40.639 --> 00:05:48.320
actually sent us over three systems to target three different popular gaming

00:05:45.520 --> 00:05:53.440
resolutions and the results between the different resolutions tell a really

00:05:50.160 --> 00:05:56.720
interesting story first of all at 1080p

00:05:53.440 --> 00:05:59.120
you should only use fsr or rsr if you

00:05:56.720 --> 00:06:04.000
absolutely have to even slight downgrades in resolution can

00:06:02.000 --> 00:06:08.639
lead to an image that's softer than 10 ply toilet paper so if you need that

00:06:06.160 --> 00:06:12.960
extra 20 of performance you should try and get it by dropping the in-game

00:06:10.400 --> 00:06:16.000
settings rather than enabling fsr i'll put some examples on the screen but

00:06:14.560 --> 00:06:19.520
realistically youtube compression is going to have its day with it so unless

00:06:17.759 --> 00:06:23.919
you're subscribed on Floatplane this might not be that meaningful to you

00:06:21.440 --> 00:06:28.560
at 1440p however it's more of a mixed bag depending on the game assassin's

00:06:25.919 --> 00:06:32.240
creed valhalla for example looks great with rsr enabled with a nearly

00:06:30.479 --> 00:06:36.160
imperceptible loss in image quality during the majority of your gameplay

00:06:34.240 --> 00:06:41.440
tiny tina's wonderland and horizon zero dawn are less favorable due to how fsr

00:06:38.960 --> 00:06:45.919
works however tiny tina's wonderland a borderlands offshoot has hard black

00:06:43.919 --> 00:06:50.560
lines around basically everything which can become a nightmare for aliasing and

00:06:48.560 --> 00:06:54.240
in a lot of situations can end up looking worse than if you didn't enable

00:06:52.080 --> 00:06:58.720
it at all horizon zero dawn on the other hand has everything close to the player

00:06:56.000 --> 00:07:02.880
looking great but the benchmark has a lot of stone textures that can start

00:07:00.479 --> 00:07:07.360
looking a little strange in the distance fsr can have some trouble deciding what

00:07:04.880 --> 00:07:10.560
to do with a line about a pixel thick when it's upscaling and this is

00:07:08.960 --> 00:07:14.639
especially true if it's on a moving object and this is especially true at

00:07:12.960 --> 00:07:18.319
lower quality settings should that pixel be light should it be

00:07:16.479 --> 00:07:22.639
dark it's hard to say given the amount of information that it has to go off of

00:07:20.560 --> 00:07:27.199
this is compounded by the fact that fsr 1.0 has no temporal component it just

00:07:25.440 --> 00:07:31.039
sees the frame as it is with no knowledge of what came before or what is

00:07:29.360 --> 00:07:34.960
expected to come after which can lead to shimmering like i mentioned before where

00:07:33.039 --> 00:07:38.319
a pixel with a fine black line can actually change from light to dark frame

00:07:37.199 --> 00:07:42.240
by frame AMD knows however that the lack of

00:07:40.319 --> 00:07:46.479
temporal information is a problem with fsr 1.0 compared to its competitors and

00:07:44.720 --> 00:07:52.000
they've actually included temporal information in the recently released fsr

00:07:48.639 --> 00:07:53.360
2.0 that tech looks really promising

00:07:52.000 --> 00:07:57.919
based on the small amount of testing that i've seen but currently it's not

00:07:55.120 --> 00:08:01.440
supported in many games unlike rsr that can be enabled for any title through

00:07:59.680 --> 00:08:07.599
Radeon software back to testing 4k is where fsr 1.0

00:08:04.960 --> 00:08:10.800
really seems to come into its own here we've got enough pixels that even a

00:08:09.199 --> 00:08:14.479
6950xt sometimes struggles to keep frame rates

00:08:12.800 --> 00:08:20.400
high if you also want to turn up your details and fsr is getting enough pixels

00:08:17.440 --> 00:08:24.720
in to spit a good image out my complaints in tiny tina's wonderland and

00:08:22.319 --> 00:08:27.360
horizon zero dawn are basically gone with the small lines and textures

00:08:26.080 --> 00:08:31.120
getting rendered with almost zero weirdness and while if you're really

00:08:29.759 --> 00:08:35.360
looking for it you might be able to find some shimmering in the distance

00:08:32.800 --> 00:08:39.120
you'd have to be playing one hell of an unimmersive game for you to be

00:08:37.519 --> 00:08:42.640
distracted enough by it to notice anything going wrong

00:08:40.719 --> 00:08:46.720
my main takeaways though are that you should absolutely enable smart access

00:08:44.320 --> 00:08:52.160
memory and if you're gaming at 1440p or 4k

00:08:47.680 --> 00:08:54.959
at least give fsr a try it works on AMD

00:08:52.160 --> 00:08:59.519
and NVIDIA gpus i mean heck even Intel integrated ones so if your poor older

00:08:57.440 --> 00:09:03.279
GPU is struggling this could be a way to claw back some frames it's probably a

00:09:01.920 --> 00:09:07.040
lot better than letting your monitor do the upskilling that's for sure

00:09:05.200 --> 00:09:11.279
so huge thanks to AMD for sponsoring this video if you guys enjoyed it maybe

00:09:09.040 --> 00:09:17.680
go check out our play button pc really that's an odd one to throw too

00:09:13.279 --> 00:09:17.680
it's a good video go check it out