WEBVTT

00:00:00.120 --> 00:00:05.879
if you've got an NVIDIA graphics card you may have noticed that the majority

00:00:03.639 --> 00:00:10.280
of their driver updates are labeled as game ready drivers with the idea being

00:00:08.400 --> 00:00:14.879
that in addition to Bringing General updates that benefit everyone these

00:00:12.320 --> 00:00:20.119
drivers are optimized for a specific new game and are released very near or even

00:00:17.400 --> 00:00:24.199
on the game's launch day but guess what with a few exceptions downloading the

00:00:22.000 --> 00:00:28.000
latest driver for your graphics card probably isn't going to give you a

00:00:26.000 --> 00:00:32.559
massive performance boost even in that new game huh so what are they they

00:00:30.199 --> 00:00:36.800
actually do well we'll get to that but first a quick history nugget it turns

00:00:34.800 --> 00:00:42.879
out this misconception about performance goes all the way back to the days of the

00:00:38.840 --> 00:00:44.559
Reva TNT an NVIDIA product from 1998

00:00:42.879 --> 00:00:50.480
there was a famous driver for the Reva TNT called Detonator that actually did

00:00:48.440 --> 00:00:55.920
boost performance significantly due to the inclusion of optimizations for AMD

00:00:52.680 --> 00:00:58.280
CPUs that previous drivers lacked this

00:00:55.920 --> 00:01:01.840
was great press for NVIDIA but unfortunately it ended up setting

00:00:59.879 --> 00:01:05.799
setting an expectation that drivers would be some kind of Silver Bullet for

00:01:03.760 --> 00:01:10.360
performance issues the issue with that is they're usually not and a big part of

00:01:08.600 --> 00:01:14.400
the reason it's rare to see big performance jumps with new drivers these

00:01:12.159 --> 00:01:19.240
days is that devs work closely with NVIDIA while the game is in development

00:01:17.439 --> 00:01:22.920
this isn't to say you never see significant performance increases with

00:01:20.880 --> 00:01:26.920
new NVIDIA drivers but it's not as common as you might think especially as

00:01:25.119 --> 00:01:31.360
tweaks to the drivers are often made with specific games in mind well before

00:01:29.360 --> 00:01:35.200
launch meaning that if you've updated your drivers with any regularity there's

00:01:33.520 --> 00:01:40.360
a good chance your game will perform just fine even if you're not yet using

00:01:37.720 --> 00:01:45.920
the specific game ready driver for that game NVIDIA has over an 80% market share

00:01:43.680 --> 00:01:50.119
in the discrete GPU market so it probably isn't a surprise that they have

00:01:47.799 --> 00:01:54.479
plenty of contacts at Major game studios there's actually a regular Cadence where

00:01:52.200 --> 00:01:58.000
NVIDIA sends out pre-release drivers to developers on Mondays and from there

00:01:56.479 --> 00:02:01.920
there's back and forth between the game developers and the NVIDIA folks to get

00:02:00.039 --> 00:02:07.000
things to play as nicely as possible before launch day and while NVIDIA can't

00:02:04.600 --> 00:02:12.239
possibly test every single Hardware configuration they do have over 4500

00:02:10.160 --> 00:02:16.239
combinations they test that go all the way back to 2012 as of the time this

00:02:14.720 --> 00:02:20.360
video was shot in case you were wondering this is how they figure out

00:02:18.280 --> 00:02:25.120
what the optimal settings for your PC are in GeForce experience but enough

00:02:22.840 --> 00:02:28.440
context already what specifically about these drivers do they tweak before

00:02:26.720 --> 00:02:32.319
release we'll tell you right after we thank the sponsor of this video

00:02:30.080 --> 00:02:36.720
hostinger building a website can be daunting but hostinger can make things

00:02:34.599 --> 00:02:41.120
easy with their intuitive AI enabled features choose from 150 fully

00:02:39.040 --> 00:02:45.519
customizable templates then tailor them to suit your needs with AI powered

00:02:43.159 --> 00:02:51.200
writing and picture making tools they even provide you with a free domain name

00:02:47.720 --> 00:02:53.400
free SSL and your very own email account

00:02:51.200 --> 00:02:57.720
what you can also work on your site on the go with their mobile site Builder

00:02:55.959 --> 00:03:01.959
check out hostinger at the link below and use code techquickie to get 10% off

00:02:59.840 --> 00:03:06.239
off rather than pushing drivers to squeeze every possible frame per second

00:03:04.200 --> 00:03:11.120
from an upcoming game the general approach with game ready drivers is to

00:03:08.200 --> 00:03:15.920
ensure stability for example NVIDIA has outright disabled resizable bar support

00:03:13.440 --> 00:03:19.680
for certain games as it actually caused performance degradation with certain

00:03:17.680 --> 00:03:23.720
Hardware configurations something that notably happened with Hitman world of

00:03:21.720 --> 00:03:28.000
assassination where NVIDIA turned off the feature on systems with Intel CPUs

00:03:26.040 --> 00:03:33.040
to prevent a performance hit but if you had an AMD CPU in left resizable bar on

00:03:31.680 --> 00:03:37.360
because it wasn't causing performance issues that's not fair not only that

00:03:35.680 --> 00:03:41.400
tweaks like this tend to be for an entire product stack so for example if

00:03:40.040 --> 00:03:48.799
there's a problem with an optional feature that's being seen with a lot of RTX 480s it's often switched off for the

00:03:46.280 --> 00:03:53.319
entire love lace architecture instead of creating a situation where that feature

00:03:51.000 --> 00:03:58.840
has to get retested on a per card basis for every subsequent driver release and

00:03:56.280 --> 00:04:04.000
of course resizable bar is just one of a huge number of levers NVIDIA can pull

00:04:01.319 --> 00:04:08.000
dlss other AI features and the actual Cuda cores themselves all need to be

00:04:06.200 --> 00:04:12.840
able to support a massive number of games which is part of the reason modern

00:04:09.959 --> 00:04:16.720
GPU drivers have gotten so huge your new game ready driver has specific code

00:04:15.000 --> 00:04:21.320
describing how to behave when you're playing this specific new game NVIDIA

00:04:19.400 --> 00:04:25.360
has actually tried to strip out unnecessary components to get driver

00:04:23.240 --> 00:04:29.680
sizes down from around a Gigabyte to around 600 megabytes which is still

00:04:27.639 --> 00:04:34.960
pretty gigantic and with all of those variables game ready drivers still can

00:04:32.080 --> 00:04:39.840
and sometimes do cause issues even after extensive testing this is part of the

00:04:36.919 --> 00:04:44.360
reason NVIDIA also offers Studio drivers geared toward even greater stability for

00:04:42.080 --> 00:04:49.080
Content creators which aren't pushed out as frequently as game ready drivers the

00:04:47.000 --> 00:04:54.240
issues that game ready drivers sometimes face are a possible point in favor of

00:04:51.479 --> 00:04:58.880
AMD's slower release Cadence for its whql certified radon drivers and

00:04:57.520 --> 00:05:03.600
something that the two companies have publicly critici ized each other on of

00:05:01.080 --> 00:05:07.960
course AMD has also had issues with its drivers at times with their anti-ag plus

00:05:06.320 --> 00:05:12.919
feature causing Gamers to run into problems with anti-che software in late

00:05:09.800 --> 00:05:15.160
2023 standing out as an example so

00:05:12.919 --> 00:05:18.680
slower cadences aren't necessarily a perfect solution either and the

00:05:17.000 --> 00:05:23.800
industry's transition towards the directx12 API has actually shifted more

00:05:22.000 --> 00:05:28.319
of the onus for getting things right towards the game developers and away

00:05:25.960 --> 00:05:32.560
from GPU companies the intent behind this is to give Developers more control

00:05:30.360 --> 00:05:37.919
over their own game engines but an unintended and common consequence has

00:05:35.319 --> 00:05:42.440
been that devs can violate the directx12 spec when they actually believe they're

00:05:39.919 --> 00:05:47.720
following it so I wouldn't expect those hot fix drivers that Target a specific

00:05:44.800 --> 00:05:51.960
problem to go away anytime soon it's not exactly like trillion dollar companies

00:05:49.880 --> 00:05:55.440
can't make mistakes hey thanks for watching that whole video like it if you

00:05:53.639 --> 00:05:58.479
liked it dislike it if you disliked it check out our other videos comment below

00:05:57.000 --> 00:06:04.880
with video suggestions and don't forget to subscribe and follow what are you

00:06:00.560 --> 00:06:04.880
doing here if you didn't like the video