WEBVTT

00:00:01.280 --> 00:00:07.520
bad news everyone the rtx real-time ray

00:00:04.640 --> 00:00:11.200
tracing beta for minecraft bedrock is finally here and it looks absolutely

00:00:09.760 --> 00:00:16.640
amazing and i'm not in office to benchmark it

00:00:13.679 --> 00:00:22.160
for you and tell you all about it fear not though for Jake is back at the

00:00:19.359 --> 00:00:27.119
office and he has done the benchmarking for me and i'm gonna tell you guys all

00:00:24.480 --> 00:00:32.480
about it but first there's some really cool changes that have taken place under

00:00:29.359 --> 00:00:34.480
the hood to get rtx properly implemented

00:00:32.480 --> 00:00:38.559
in minecraft oh and also this message from our

00:00:36.000 --> 00:00:41.760
sponsor cablemod cablemod offers quality cables and modding accessories that are

00:00:40.000 --> 00:00:45.360
trusted by system builders everywhere head over to cablemod at the link below

00:00:43.360 --> 00:00:53.800
and enter coupon code Linus to get 10 percent off

00:00:57.039 --> 00:01:04.000
wow i should have turned rtx on a long time ago all right guys in normal

00:01:01.760 --> 00:01:09.920
bedrock edition minecraft there are two maps for every texture in the game the

00:01:06.880 --> 00:01:12.000
base color as well as the opacity these

00:01:09.920 --> 00:01:17.759
maps contribute the colors as well as the transparency or how see-through

00:01:14.799 --> 00:01:21.600
every block is however when they moved to implement ray-traced lighting there

00:01:19.680 --> 00:01:27.759
was a pretty apparent problem regular minecraft doesn't calculate light

00:01:24.080 --> 00:01:31.040
bouncing instead light just spreads

00:01:27.759 --> 00:01:33.040
across any nearby surface evenly now

00:01:31.040 --> 00:01:37.280
they could have just made every type of block bounce light in the same way

00:01:35.439 --> 00:01:43.280
problem is that wouldn't have been true to the real world behavior of materials

00:01:40.560 --> 00:01:48.320
and light for instance if you shine a flashlight at a mirror the majority of

00:01:46.240 --> 00:01:51.119
that light is going to bounce right off and illuminate the surface that it

00:01:49.680 --> 00:01:55.119
bounces to but if you were to shine a light at your

00:01:52.720 --> 00:01:59.360
carpet chances are that most of that light will end up illuminating the

00:01:56.640 --> 00:02:03.520
carpet itself without much bouncing to other surfaces this is because your

00:02:01.360 --> 00:02:09.200
carpet is not very metallic or reflective and because it's very rough

00:02:06.640 --> 00:02:14.239
relative to the smoothness of a mirror problem is in the existing version of

00:02:11.599 --> 00:02:20.160
minecraft there is no way to define a block or a texture as reflective or

00:02:17.840 --> 00:02:26.000
rough so for light to be able to properly bounce the developers actually

00:02:22.480 --> 00:02:28.640
had to add four new mappings to every

00:02:26.000 --> 00:02:33.200
texture in the game metalness or reflectiveness

00:02:30.000 --> 00:02:36.480
emissivity or how much it should glow

00:02:33.200 --> 00:02:38.239
roughness so how rough it is as well as

00:02:36.480 --> 00:02:42.959
a height map where you could add artificial depth to parts of a texture

00:02:40.640 --> 00:02:46.640
in the game with this added data ray traced lighting can be a lot more

00:02:44.800 --> 00:02:50.720
accurate for example in the demo you're looking at right now we can see the

00:02:48.720 --> 00:02:54.879
hardwood flooring is very smooth and reflective whereas the carpeting is

00:02:52.720 --> 00:02:59.440
rough and doesn't reflect much light what this means is that rtx support in

00:02:57.120 --> 00:03:04.800
the game comes with some caveats primarily that ray tracing is not going

00:03:02.239 --> 00:03:07.680
to work on a non-rtx card even though NVIDIA has allowed this at times in the

00:03:06.800 --> 00:03:13.519
past and it also won't work on just any old

00:03:11.200 --> 00:03:18.400
minecraft save game right out of the box you're going to need to select an rtx

00:03:16.000 --> 00:03:22.640
compatible resource pack to enable ray traced lighting it's not a huge deal it

00:03:20.959 --> 00:03:26.959
just means that for the moment you're stuck to the sample texture packs that

00:03:24.480 --> 00:03:31.519
NVIDIA and mojang have provided on the plus side it does make it super easy to

00:03:29.360 --> 00:03:36.480
use rtx on maps that are ported over from the java version of the game which

00:03:33.920 --> 00:03:39.799
actually looks pretty sweet if we port over the lobby of our upcoming java

00:03:38.400 --> 00:03:45.200
edition server mc.LTT.g by the way there are also a

00:03:42.400 --> 00:03:49.360
couple of rtx tailored maps but behind the scenes these are just regular maps

00:03:46.799 --> 00:03:54.000
with rtx resource packs specific to them bundled in to see what it takes to run

00:03:51.200 --> 00:03:59.760
them we grabbed three different tiers of graphics cards we used the same CPU

00:03:56.400 --> 00:04:01.439
across the board because spoiler alert

00:03:59.760 --> 00:04:06.400
it will make little to no difference due to how GPU bottlenecked we're expecting

00:04:04.000 --> 00:04:11.439
to be now we tried both an experiential test just running around breaking blocks

00:04:09.280 --> 00:04:15.760
and killing mobs to get a sense of how playable the game felt on each of our

00:04:13.680 --> 00:04:20.479
graphics cards and then we also ran benchmarks on the NVIDIA supplied

00:04:17.759 --> 00:04:25.040
imagination island sample map riding around one of the in-game trains on a

00:04:22.639 --> 00:04:28.800
predefined loop we settled on a render distance of 16 chunks since it's the

00:04:27.120 --> 00:04:34.000
only option that's supported with both rtx on and off and ended up being less

00:04:32.000 --> 00:04:38.720
than a 10 performance hit compared to using the lowest eight render distance

00:04:36.320 --> 00:04:44.320
with rtx on every other visual setting we left turned on beginning with the

00:04:41.280 --> 00:04:46.960
lowest end rtx supported option an rtx

00:04:44.320 --> 00:04:51.840
2060 ko from evga after loading an imagination island with

00:04:49.040 --> 00:04:57.520
rtx off in 1080p we were greeted with the expected crisp clean 180 plus FPS

00:04:55.520 --> 00:05:01.680
experience no stutters then we turned rtx on and uh

00:05:00.240 --> 00:05:07.840
woof we were both shocked and a bit relieved

00:05:04.880 --> 00:05:12.479
experientially the game actually feels a bit less responsive to movements but

00:05:10.320 --> 00:05:17.840
it was playable with no noticeable stuttering and an average FPS of 53

00:05:16.160 --> 00:05:22.240
although that is less than a third of what we had with rtx off we also noticed

00:05:20.800 --> 00:05:27.039
that when interacting with the environment like playing or breaking

00:05:24.639 --> 00:05:32.320
blocks or opening doors we could see the shadows being processed which made it

00:05:29.520 --> 00:05:36.720
feel a little disingenuous to call it real time ray tracing

00:05:34.320 --> 00:05:41.039
it's honestly kind of a bit jarring this is where another newly introduced

00:05:38.479 --> 00:05:47.360
technology comes into play though dlss 2.0 allows the game to be rendered at a

00:05:44.160 --> 00:05:49.120
lower than native resolution and then ai

00:05:47.360 --> 00:05:54.080
upscaled with the help of the tensor cores on rtx gpus it actually works

00:05:52.160 --> 00:05:59.120
really well and we didn't notice a visual difference with it enabled versus

00:05:56.400 --> 00:06:04.800
disabled the only problem is that 50-ish FPS number that we mentioned

00:06:01.600 --> 00:06:06.880
earlier that was with dlss turned on

00:06:04.800 --> 00:06:13.360
already and if we switch it off we're actually looking at closer to 30 FPS on

00:06:09.600 --> 00:06:15.280
average or about a sixth of our rtx off

00:06:13.360 --> 00:06:20.560
performance moving up to an rtx 2070 super is where

00:06:18.479 --> 00:06:24.880
the experience starts to feel a lot smoother with an average of 72 frames

00:06:22.560 --> 00:06:29.520
per second the sluggishness we felt with the 2060 ko is completely gone and i

00:06:27.840 --> 00:06:35.440
think it's safe to say that this is definitely the sweet spot for 1080p rtx

00:06:32.800 --> 00:06:40.240
on minecraft at the moment and now that it's running decently we can actually

00:06:37.280 --> 00:06:44.400
take a second to appreciate this i think in some of the example maps the colors

00:06:42.639 --> 00:06:48.160
in direct sunlight are probably a bit over saturated and some textures like

00:06:46.800 --> 00:06:51.919
water could stand to have their reflectiveness toned down like it kind

00:06:50.479 --> 00:06:56.080
of makes the game feel like one of those cheap minecraft clones

00:06:53.759 --> 00:07:01.919
however when you get into a map with some interior lighting and some Windows

00:06:58.560 --> 00:07:04.080
the god rays are insane or in something

00:07:01.919 --> 00:07:08.880
like this cave area the way the light bounces around is just

00:07:06.240 --> 00:07:13.759
stunning like it really goes to show how much better rtx can look than a

00:07:11.520 --> 00:07:18.240
traditional java edition shader pack that is at least until sonic ether

00:07:15.599 --> 00:07:23.680
releases his software path trace shaders but dang for now the rtx 2070 super is

00:07:21.759 --> 00:07:29.280
for sure the way to go if you're looking to buy a GPU for your spoiled af kids so

00:07:26.639 --> 00:07:34.319
they can play minecraft with real-time rtx

00:07:30.560 --> 00:07:35.360
at 1080p then there's the rtx 2080 super

00:07:34.319 --> 00:07:40.240
the last reasonable option in the rtx GPU lineup

00:07:38.240 --> 00:07:45.199
the improvements moving up to this card actually were surprisingly unimpressive

00:07:42.960 --> 00:07:51.120
with an average FPS of 80 compared to the 72 average on the 2070 super now

00:07:48.240 --> 00:07:56.479
that is technically an upgrade but i would say it's probably not worth the

00:07:53.199 --> 00:07:59.199
money for this specific use case

00:07:56.479 --> 00:08:04.000
at least at 1080p but hey since we've got a bit of headroom how about 1440p

00:08:02.639 --> 00:08:11.280
or even 4k yeah

00:08:07.360 --> 00:08:14.080
good luck with that 1440p with dlss on

00:08:11.280 --> 00:08:18.639
brings our 2080 super right down to 61 FPS

00:08:15.120 --> 00:08:19.520
so that's usable and as for 4k

00:08:18.639 --> 00:08:25.360
well it's approaching what i would consider

00:08:21.840 --> 00:08:27.199
to be playable at around 41 FPS average

00:08:25.360 --> 00:08:33.279
but the thing is that's not the kind of experience anyone spending 750 us

00:08:30.240 --> 00:08:36.080
dollars on a graphics card wants to have

00:08:33.279 --> 00:08:39.519
with all of that in mind was it worth the wait

00:08:37.519 --> 00:08:43.760
well it's not something we're gonna switch development of our LTT servers to

00:08:41.760 --> 00:08:50.560
bedrock for by the way you can check out the beta at mc.lt.g but it does look

00:08:47.760 --> 00:08:56.000
legitimately next-gen in a way that i never thought i'd hear myself say about

00:08:53.120 --> 00:09:01.519
minecraft as for the performance the beta is a bit of a poop demonstration i

00:08:58.399 --> 00:09:04.800
mean even on a 750 us dollar graphics

00:09:01.519 --> 00:09:07.360
card it's really only playable at 1440p

00:09:04.800 --> 00:09:12.000
max and then forget about getting the most out of your high refresh rate

00:09:08.880 --> 00:09:14.320
gaming display and while rtx has a long

00:09:12.000 --> 00:09:19.279
and proud history of massive performance penalties normally we're talking like 30

00:09:16.640 --> 00:09:24.080
to 50 massive not more than that massive so what we're

00:09:21.920 --> 00:09:28.320
hoping is that with some optimizations they can get it to be a little bit more

00:09:26.000 --> 00:09:34.080
performant and if they do honestly i am pretty stoked to see what

00:09:31.519 --> 00:09:38.560
the community can do to make even better and more unique builds and really cool

00:09:36.640 --> 00:09:42.560
looking experiences with the extra flexibility that rtx and minecraft can

00:09:41.680 --> 00:09:46.480
offer speaking of flexible i'm real flexible

00:09:44.880 --> 00:09:52.720
about the way i work these segways in drop.com is featuring the

00:09:50.160 --> 00:09:57.680
sennheiser hd6xx headphones these are one of their all-time best sellers with

00:09:54.800 --> 00:10:01.760
over 90 000 units sold they've got an unchanged driver and sound structure

00:09:59.360 --> 00:10:05.600
compared to the hd650 so you can expect nice balanced mid-range and natural

00:10:03.839 --> 00:10:09.120
sounding bass they've got a detachable six foot cable with an eighth inch plug

00:10:07.120 --> 00:10:12.240
that's versatile for everyday use and a quarter inch adapter if you need one of

00:10:10.560 --> 00:10:15.839
those and it comes with sennheiser's long-term support they're super comfy

00:10:14.160 --> 00:10:19.920
basically they're great headphones and you can buy them today at the link in

00:10:18.160 --> 00:10:23.040
the video description if you guys enjoyed this video you might

00:10:21.440 --> 00:10:27.760
also enjoy the one where we made our own minecraft server we actually didn't end

00:10:25.360 --> 00:10:32.160
up leaving that one deployed um it's like hosted in a proper data center now

00:10:30.000 --> 00:10:37.289
and all that good stuff but what the hey it was a fun experiment