WEBVTT

00:00:00.240 --> 00:00:08.200
oh boy I can't wait to play the new Indiana Jones

00:00:04.319 --> 00:00:11.120
game huh hang on a minute Billy for

00:00:08.200 --> 00:00:16.080
modern games you'll need Modern Hardware with Ray tracing Ray tracing what's that

00:00:14.879 --> 00:00:21.840
Mr Murdoch why it's quite an old technology

00:00:19.119 --> 00:00:26.560
but now done in real time thanks to powerful accelerators in your GPU that

00:00:24.880 --> 00:00:32.640
sounds expensive it is very expensive but you

00:00:30.160 --> 00:00:40.960
don't want your games to look ugly do you ugly like you well I guess not but I

00:00:38.920 --> 00:00:48.399
don't have enough money for a new GPU what can I do it's easy you just need to

00:00:44.360 --> 00:00:50.960
find a sponsor like our sponsor server

00:00:48.399 --> 00:00:54.719
part deals save big on refurbished recertified and even new hard drives

00:00:53.239 --> 00:01:03.199
delivered straight to your door with free 2-day us shipping use our link and

00:00:57.280 --> 00:01:03.199
enter code lt5 off to get $5 off any

00:01:09.840 --> 00:01:14.840
order yep it's true Indiana Jones and

00:01:13.119 --> 00:01:19.720
the great circle is the first game that was developed from the ground up to use

00:01:17.000 --> 00:01:25.240
ra tracing not as an option to make the lighting a bit more realistic but as a

00:01:21.720 --> 00:01:28.000
core required component of the game so

00:01:25.240 --> 00:01:32.880
we've set up two test systems one using the latest and greatest at the time of

00:01:29.600 --> 00:01:34.560
film NVIDIA's RTX 490 and one using

00:01:32.880 --> 00:01:39.399
NVIDIA's entry point into R Trace lighting Splendor the60 we're at 15

00:01:37.360 --> 00:01:43.280
frames that being said on both PCS we've set everything to Max on the 490 side

00:01:41.640 --> 00:01:46.640
we're still 4K native we have everything turned on except for path tracing

00:01:45.360 --> 00:01:51.360
there's still a lot of raate tracing that's happening like the reflections you can see in the window big thing I've

00:01:49.640 --> 00:01:56.240
noticed is that even in raid Trace games there's still just visual anomalies like

00:01:53.880 --> 00:02:01.079
his hair kind of changing color we are consistently above 60 frames a second

00:01:57.960 --> 00:02:03.479
Which is far above what I expected in

00:02:01.079 --> 00:02:09.080
this scenario but there is one thing NVIDIA really bunged up and that's the

00:02:05.719 --> 00:02:11.680
messaging we call RTX Ray tracing but in

00:02:09.080 --> 00:02:16.599
truth most games even this one only switch to Global Ray Trace illumination

00:02:14.160 --> 00:02:21.480
if you turn on path tracing I'm very impressed with the 49s ability to do

00:02:19.319 --> 00:02:24.879
over 60 frames a second and I've had to verify the settings many many times to

00:02:23.319 --> 00:02:28.640
make sure that I'm not secretly using dlss but that's going to tell you

00:02:26.599 --> 00:02:34.280
nothing about how the starter point for Ray tracing is going to do the 2060 and

00:02:31.480 --> 00:02:37.040
immediately you'll notice that the 2060 has a bit of challenge giving us the

00:02:35.560 --> 00:02:42.920
performance we'd like to see and so why don't we turn down some settings and give this thing a chance one thing to

00:02:39.760 --> 00:02:44.760
note is that Indiana Jones does a vram

00:02:42.920 --> 00:02:48.519
test when it boots if you have 12 or less gigs of vram it's it's going to set

00:02:46.440 --> 00:02:53.640
it to the lowest settings if you use a custom exe you can actually boot the

00:02:50.680 --> 00:02:56.680
game and skip that vram check uh to get access to those settings but uh

00:02:55.519 --> 00:02:59.840
unfortunately if you try and turn them on the game will crash actually we're

00:02:58.599 --> 00:03:05.040
going to leave 4K we're going to turn turn on some dlss baby 23 frames a

00:03:03.239 --> 00:03:09.200
second this is incredible even with an internal resolution of 1080p we are

00:03:07.040 --> 00:03:12.879
still having around 20 frames a second what if you have a 2060 and you want to

00:03:10.560 --> 00:03:17.840
make it actually run let's turn down some settings this game is running on

00:03:14.440 --> 00:03:20.080
the 2060 at a native 1080p High settings

00:03:17.840 --> 00:03:24.159
and it looks drastically worse which is no surprise but this is still a rate

00:03:22.159 --> 00:03:28.519
Trace experience if you bought your card 6 years ago you would still be able to

00:03:26.080 --> 00:03:31.920
play these games in Fairly High Fidelity oh those Reflections are

00:03:30.360 --> 00:03:36.640
oh remember when there was bright light reflecting on the floor from that window

00:03:33.920 --> 00:03:42.159
David remembers now it's clear that the 2060s first generation Our Tor were not

00:03:40.000 --> 00:03:47.000
chosen wisely in terms of future proofing but as you can see you don't

00:03:44.599 --> 00:03:51.599
need full rayra Global illumination for a game to look really impressive and it

00:03:50.239 --> 00:03:57.000
could be argued that NVIDIA's big selling point for this generation

00:03:54.200 --> 00:04:00.760
somewhat came true even if lonus wasn't wrong that you'd be better off waiting

00:03:58.120 --> 00:04:05.120
for a second third or fourth four or fifth gen card but why are we switching

00:04:02.879 --> 00:04:10.920
in-game lighting to Ray tracing more importantly why are we doing it now it's

00:04:08.280 --> 00:04:14.519
been used in film for decades and long before it was a selling feature on the

00:04:12.200 --> 00:04:18.359
side of GPU boxes even video games were using it to create the pre-bake lighting

00:04:16.239 --> 00:04:22.199
Maps used in traditional rendering we'll get to that but first you may already

00:04:20.759 --> 00:04:26.479
know the difference between path tracing and rasterization but let's lay them out

00:04:24.560 --> 00:04:30.160
just in case rasterization is the process of converting vector graphics or

00:04:28.639 --> 00:04:34.880
polygons and their inter intersecting points into a raster image which

00:04:33.039 --> 00:04:39.199
consists of pixels shaders are then applied that best approximate what those

00:04:37.000 --> 00:04:43.960
pixels should look like based on lighting texture and material properties

00:04:41.520 --> 00:04:48.919
path tracing often used interchangeably with the term Ray tracing even though

00:04:46.120 --> 00:04:53.080
they aren't exactly the same thing simulates the path of light rays as they

00:04:50.960 --> 00:04:56.880
travel through a scene hitting objects bouncing reflecting refracting or being

00:04:55.520 --> 00:04:59.720
absorbed Based On A material's Properties there are numerous methods

00:04:58.520 --> 00:05:05.440
that impact the accuracy of the simulation recursive Ray tracing for instance has Shadow rays that are sent

00:05:03.320 --> 00:05:09.600
out at each Ray intersection Point towards light sources and Photon mapping

00:05:08.080 --> 00:05:13.759
emits light particles from the light sources of a scene in a preliminary

00:05:11.160 --> 00:05:18.960
rendering pass but the principle of both Ray tracing and path tracing Remains the

00:05:15.479 --> 00:05:21.960
Same simulate light by tracing the paths

00:05:18.960 --> 00:05:24.680
of rays through a scene how many Rays

00:05:21.960 --> 00:05:30.360
you ask well that depends but the short answer is if you want to do it right a

00:05:27.440 --> 00:05:34.400
lot and when you do it right it offers a big advantage in terms of realism

00:05:32.639 --> 00:05:38.199
especially in scenes with Dynamic lighting like open worlds with day and

00:05:36.199 --> 00:05:43.080
night cycles as for why we're doing it now well it was inevitable the industry

00:05:40.880 --> 00:05:47.840
has wanted to for a long time and for good reasons don't take my word for it

00:05:45.160 --> 00:05:51.680
or inv videas but Pixar describes it as conceptually and mathematically simple

00:05:49.919 --> 00:05:55.520
and elegant that means that not only does Ray tracing code take up much less

00:05:53.720 --> 00:05:59.080
storage than the large light Maps we need for pre-baked lighting but no

00:05:56.960 --> 00:06:02.440
longer making those light Maps or adding extra lights to simulate indirect

00:06:00.800 --> 00:06:06.680
lighting should both save developers time and in result make for prettier

00:06:05.000 --> 00:06:10.080
games that was one of the key sales pitches for rate tracing that the

00:06:08.039 --> 00:06:14.319
reduction in manh hours outweighs the increased Hardware costs the only

00:06:12.080 --> 00:06:19.319
problem is that in the context of gaming The increased Hardware cost falls on the

00:06:16.639 --> 00:06:23.319
gamers whose gpus now need to perform those lighting simulations continuously

00:06:20.960 --> 00:06:28.080
every time they play a game Power build what power build and there are other

00:06:25.440 --> 00:06:32.440
costs NVIDIA has taken a lot of our money during RTX is awkward adolescence

00:06:30.479 --> 00:06:37.759
and maybe more importantly there's a cost in performance the most expensive

00:06:35.039 --> 00:06:43.240
gaming GPU at least until you can get its replacement over here is the RTX 490

00:06:40.759 --> 00:06:47.919
it has over three times the ray tracing prowess of the underwhelming first

00:06:45.120 --> 00:06:52.960
generation RTX cards and still can't consistently render a native 4K 60 Path

00:06:50.880 --> 00:06:59.759
traced experience even the newly announced $2,000 RTX 5090 is advertised

00:06:57.360 --> 00:07:03.960
to only hit 28 frames per second natively in cyberpunk with all the ray

00:07:01.720 --> 00:07:09.080
traced bells and whistles AI assisted upscaling with dlss is meant to make up

00:07:06.360 --> 00:07:15.440
for that and if my lovely assistant will move oh yeah you can see clearly it can

00:07:12.919 --> 00:07:19.319
deliver impressive results but from talking to one of pl's old games

00:07:17.000 --> 00:07:22.960
industry contacts Gamers aren't the only ones feeling like this transition might

00:07:21.360 --> 00:07:28.319
have been rushed a little bit see the pitch to developers including to our

00:07:24.960 --> 00:07:30.240
contact was of course Time Savings but

00:07:28.319 --> 00:07:34.599
the time that they saved from less manual lighting work ended up getting

00:07:32.160 --> 00:07:38.800
replaced with more time testing and optimizing performance on those

00:07:36.240 --> 00:07:43.199
underwhelming early generation cards optimization that usually resulted in

00:07:41.000 --> 00:07:47.240
turning down visual settings which in many cases left us with image quality

00:07:45.400 --> 00:07:51.000
that didn't look that much better than traditional rasterization as hard run

00:07:49.280 --> 00:07:55.000
box pointed out in an excellent recent deep dive those compromises caused some

00:07:52.919 --> 00:07:59.520
glaring issues such as noise and artifacting appearing as a a boiling

00:07:57.599 --> 00:08:03.280
effect those can be caused by low r counts needing to accumulate lighting

00:08:01.080 --> 00:08:07.199
information over multiple frames and suboptimal D noising techniques if you

00:08:05.520 --> 00:08:11.599
haven't experienced rate tracing at home it can be hard to tell sometimes YouTube

00:08:09.479 --> 00:08:15.039
compression and screenshots will cover a lot of those sins furthermore devs are

00:08:13.759 --> 00:08:20.000
still learning how to implement ra tracing both technically and artistically and the available tools are

00:08:18.360 --> 00:08:23.840
more rudimentary than their rasterized equivalent for example our contact set

00:08:22.039 --> 00:08:27.919
that key features such as light linking where lights will affect certain objects

00:08:25.440 --> 00:08:31.280
and not others are not as simple to use in Ray traced scenes some some of you

00:08:29.759 --> 00:08:35.599
might be old enough to remember the era of Bloom video game Graphics where every

00:08:33.560 --> 00:08:38.440
surface was slathered in a soft fuzzy glow that made it look like you were

00:08:36.640 --> 00:08:41.919
playing the game in a foggy mirror games like Burnout Paradise Twilight Princess

00:08:39.959 --> 00:08:46.440
and Oblivion come to mind and just as Bloom and motion blur and depth of field

00:08:44.480 --> 00:08:51.240
and other visual tricks went from flashy and new to overused and disgusting to

00:08:49.200 --> 00:08:55.320
intelligently applied I think raate tracing will hit those same milestones

00:08:53.160 --> 00:09:00.040
in due time strangely enough the strongest use case today for raid

00:08:57.000 --> 00:09:01.600
tracing in our opinion is the dazzling

00:09:00.040 --> 00:09:06.320
effect it can have when implemented into older titles either through discrete

00:09:03.480 --> 00:09:09.680
remasters custom mods or RTX remix NVIDIA's Suite of modding tools designed

00:09:08.000 --> 00:09:14.320
to make transformative upgrades of old PC games super easy I recently played

00:09:12.640 --> 00:09:19.200
through the original fear with added rate tracing via reshade and it was n

00:09:17.160 --> 00:09:23.600
transformative even though it pushed a 20-year-old game back to sub 60fps

00:09:21.600 --> 00:09:27.279
performance part of that performance hit is the hybrid raster and R Trace

00:09:25.560 --> 00:09:31.320
rendering committing to full rate tracing can actually improve performance

00:09:29.079 --> 00:09:35.720
like we've seen in Metro Exodus enhanced Edition or Indiana Jones so once raid

00:09:34.279 --> 00:09:39.680
tracing Tech has evolved to the point where most games fully transition to

00:09:37.959 --> 00:09:45.040
raid Trace rendering we may experience a bump in overall playability and maybe

00:09:41.760 --> 00:09:46.640
just maybe GPU makers can reduce the die

00:09:45.040 --> 00:09:52.920
space use for raster performance in exchange for even more raid tracing

00:09:48.200 --> 00:09:55.120
prowess or dare I say cost savings gosh

00:09:52.920 --> 00:09:59.760
that would be real nice the worst part of all this is that until we fully solve

00:09:57.399 --> 00:10:04.240
the chicken egg problem these issues will linger and the transition is

00:10:02.200 --> 00:10:09.160
clearly going to take some time I mean nearly one in every 30 PC Gamers is

00:10:06.600 --> 00:10:14.800
still running a 1060 for God's sake that came out in 2016 so I don't blame you

00:10:12.120 --> 00:10:19.560
guys for asking yeah it's pretty but is Ray tracing even worth it worth it like

00:10:17.519 --> 00:10:25.680
our new more compact commuter backpack at LTC store.com okay Jokes Aside only

00:10:23.120 --> 00:10:29.560
you can answer that question but what I can say is that no matter who you are

00:10:28.120 --> 00:10:33.240
you've got your head in this sand if you think that R tracing isn't happening and

00:10:31.560 --> 00:10:37.320
that you won't need it at some point I mean I remember back when people thought

00:10:35.240 --> 00:10:41.320
that fancy mesh shaders were just deployed to sell new graphics cards but

00:10:39.399 --> 00:10:45.079
I think in hindsight most people would agree now that we're better off for

00:10:43.160 --> 00:10:50.240
their widespread implementation I mean Allan Wake 2 looks incredible and runs

00:10:48.000 --> 00:10:54.040
well on lower-end Hardware as long as it's somewhat recent and has an

00:10:52.079 --> 00:10:59.800
up-to-date feature set but these things take time and I can hear a lot of you

00:10:56.680 --> 00:11:01.160
saying well yeah sure it's cool but

00:10:59.800 --> 00:11:07.079
I'm going to wait till it can be done natively with real frames no AI but I

00:11:05.160 --> 00:11:10.880
think it's becoming clear that that's not happening the real solutions are

00:11:09.360 --> 00:11:14.839
going to come in the form of optimizations like improvements to

00:11:12.880 --> 00:11:19.720
proprietary Solutions like dlss Ray reconstruction or generalized shortcuts

00:11:17.279 --> 00:11:25.040
like better distribution rate tracing because the thing is even in offline CG

00:11:22.800 --> 00:11:28.519
rendering studios are still using optimized shortcuts instead of brute

00:11:26.639 --> 00:11:33.880
forcing more rays and that's when we're talking about some sometimes 24 plus

00:11:30.880 --> 00:11:36.560
hour render times for a single frame so

00:11:33.880 --> 00:11:41.160
if you want your game to hit 60 plus frames per second you're going to have

00:11:39.000 --> 00:11:46.959
to accept that some Corners are going to be cut to bring the time down um 5.2

00:11:44.680 --> 00:11:51.839
million times really I don't think the problem is real-time rate tracing itself

00:11:49.279 --> 00:11:56.120
or even the AI upscaling techniques but rather that we've been forced to live

00:11:53.480 --> 00:11:59.560
through and pay for their infancy once we've worked through the current

00:11:57.200 --> 00:12:03.880
shortcomings we could see r traced motion blur and depth of field that can

00:12:01.880 --> 00:12:08.200
push cinematic realism to a whole other level or Hardware level support for

00:12:06.200 --> 00:12:13.240
advanced features like bidirectional path tracing to reduce noise at an equal

00:12:10.600 --> 00:12:17.639
render time and maybe even the promise of easier developer side implementation

00:12:15.600 --> 00:12:22.519
actually coming true so instead of seeing the new Indiana Jones as the

00:12:19.360 --> 00:12:24.720
harbinger of GPU pain and suffering I'm

00:12:22.519 --> 00:12:30.120
choosing to see it kind of like the hint of a whisper of a twinkle of a bright

00:12:27.399 --> 00:12:35.000
light at the end of a very expensive albeit beautifully lit

00:12:32.600 --> 00:12:41.040
tunnel speaking of the light I can see it no wait that's just a segueway to our

00:12:38.240 --> 00:12:45.360
sponsor server part deals Enterprise drives can be expensive and when you're

00:12:42.959 --> 00:12:49.680
trying to buy multiple at a time that cost well multiplies it's a good thing

00:12:47.920 --> 00:12:53.720
the folks at server part deals are there to help they sell recertified

00:12:51.600 --> 00:12:57.839
refurbished and even brand new hard drives stocking options from go-to

00:12:55.600 --> 00:13:01.800
Brands like Western Digital Seagate tashiba and more if that's not enough

00:13:00.079 --> 00:13:06.279
peace of mind their customer service is all in-house and reachable via email

00:13:04.000 --> 00:13:10.639
live chat and phone so don't wait head over to server part deals.com LTT today

00:13:09.480 --> 00:13:18.120
and you can get your new drives delivered straight to your door with free 2-day us shipping and guess what

00:13:14.800 --> 00:13:20.600
you can save even more with code lt5 off

00:13:18.120 --> 00:13:24.360
to get $5 off any order we'll have all that information down below if you're

00:13:22.760 --> 00:13:30.199
still on the fence about R tracing you should probably watch the video where we have people blindly test RTX on and off

00:13:29.120 --> 00:13:36.000
to see if they can even tell the difference the results may surprise you