WEBVTT
Kind: captions
Language: en

00:00:11.370 --> 00:00:14.669 align:start position:0%
 
[Music]

00:00:14.669 --> 00:00:14.679 align:start position:0%
 
 

00:00:14.679 --> 00:00:16.590 align:start position:0%
 
I<00:00:14.759><c> am</c><00:00:14.960><c> very</c><00:00:15.200><c> happy</c><00:00:15.440><c> to</c><00:00:15.679><c> say</c><00:00:16.119><c> that</c><00:00:16.279><c> thanks</c><00:00:16.440><c> to</c>

00:00:16.590 --> 00:00:16.600 align:start position:0%
I am very happy to say that thanks to
 

00:00:16.600 --> 00:00:19.070 align:start position:0%
I am very happy to say that thanks to
the<00:00:16.720><c> hard</c><00:00:16.920><c> work</c><00:00:17.160><c> of</c><00:00:17.400><c> IMS</c><00:00:18.039><c> null</c><00:00:18.520><c> and</c><00:00:18.720><c> several</c>

00:00:19.070 --> 00:00:19.080 align:start position:0%
the hard work of IMS null and several
 

00:00:19.080 --> 00:00:21.230 align:start position:0%
the hard work of IMS null and several
other<00:00:19.400><c> Iris</c><00:00:19.680><c> Shader</c><00:00:20.080><c> devs</c><00:00:20.760><c> our</c><00:00:20.960><c> most</c>

00:00:21.230 --> 00:00:21.240 align:start position:0%
other Iris Shader devs our most
 

00:00:21.240 --> 00:00:22.870 align:start position:0%
other Iris Shader devs our most
requested<00:00:21.680><c> feature</c><00:00:22.039><c> is</c><00:00:22.199><c> now</c><00:00:22.400><c> finally</c>

00:00:22.870 --> 00:00:22.880 align:start position:0%
requested feature is now finally
 

00:00:22.880 --> 00:00:26.349 align:start position:0%
requested feature is now finally
available<00:00:23.880><c> as</c><00:00:24.039><c> of</c><00:00:24.240><c> Iris</c><00:00:24.599><c> 1.7</c><00:00:25.560><c> Iris</c><00:00:25.960><c> now</c><00:00:26.160><c> has</c>

00:00:26.349 --> 00:00:26.359 align:start position:0%
available as of Iris 1.7 Iris now has
 

00:00:26.359 --> 00:00:29.230 align:start position:0%
available as of Iris 1.7 Iris now has
full<00:00:26.640><c> DH</c><00:00:27.240><c> support</c><00:00:28.240><c> this</c><00:00:28.359><c> means</c><00:00:28.640><c> that</c><00:00:28.800><c> shaders</c>

00:00:29.230 --> 00:00:29.240 align:start position:0%
full DH support this means that shaders
 

00:00:29.240 --> 00:00:31.550 align:start position:0%
full DH support this means that shaders
designed<00:00:29.560><c> with</c><00:00:29.720><c> DH</c><00:00:30.160><c> in</c><00:00:30.279><c> mind</c><00:00:30.599><c> will</c><00:00:30.759><c> render</c><00:00:31.080><c> LOD</c>

00:00:31.550 --> 00:00:31.560 align:start position:0%
designed with DH in mind will render LOD
 

00:00:31.560 --> 00:00:33.510 align:start position:0%
designed with DH in mind will render LOD
seamlessly<00:00:32.079><c> with</c><00:00:32.239><c> vanilla</c>

00:00:33.510 --> 00:00:33.520 align:start position:0%
seamlessly with vanilla
 

00:00:33.520 --> 00:00:36.069 align:start position:0%
seamlessly with vanilla
chunks<00:00:34.520><c> in</c><00:00:34.640><c> order</c><00:00:34.840><c> for</c><00:00:35.040><c> Iris</c><00:00:35.360><c> to</c><00:00:35.520><c> add</c><00:00:35.680><c> DH</c>

00:00:36.069 --> 00:00:36.079 align:start position:0%
chunks in order for Iris to add DH
 

00:00:36.079 --> 00:00:38.510 align:start position:0%
chunks in order for Iris to add DH
support<00:00:36.600><c> the</c><00:00:36.760><c> DH</c><00:00:37.239><c> API</c><00:00:37.680><c> has</c><00:00:37.800><c> been</c><00:00:38.000><c> updated</c><00:00:38.360><c> with</c>

00:00:38.510 --> 00:00:38.520 align:start position:0%
support the DH API has been updated with
 

00:00:38.520 --> 00:00:41.150 align:start position:0%
support the DH API has been updated with
several<00:00:38.800><c> new</c><00:00:38.920><c> methods</c><00:00:39.239><c> and</c><00:00:39.719><c> objects</c><00:00:40.719><c> however</c>

00:00:41.150 --> 00:00:41.160 align:start position:0%
several new methods and objects however
 

00:00:41.160 --> 00:00:43.830 align:start position:0%
several new methods and objects however
there<00:00:41.280><c> were</c><00:00:41.559><c> also</c><00:00:41.960><c> several</c><00:00:42.320><c> breaking</c><00:00:42.840><c> changes</c>

00:00:43.830 --> 00:00:43.840 align:start position:0%
there were also several breaking changes
 

00:00:43.840 --> 00:00:45.590 align:start position:0%
there were also several breaking changes
most<00:00:44.079><c> of</c><00:00:44.280><c> which</c><00:00:44.399><c> were</c><00:00:44.559><c> due</c><00:00:44.760><c> to</c><00:00:44.879><c> mistakes</c><00:00:45.200><c> on</c><00:00:45.399><c> my</c>

00:00:45.590 --> 00:00:45.600 align:start position:0%
most of which were due to mistakes on my
 

00:00:45.600 --> 00:00:48.630 align:start position:0%
most of which were due to mistakes on my
end<00:00:46.079><c> due</c><00:00:46.239><c> to</c><00:00:46.399><c> misnaming</c><00:00:46.879><c> a</c><00:00:47.000><c> bunch</c><00:00:47.160><c> of</c><00:00:47.640><c> objects</c>

00:00:48.630 --> 00:00:48.640 align:start position:0%
end due to misnaming a bunch of objects
 

00:00:48.640 --> 00:00:51.310 align:start position:0%
end due to misnaming a bunch of objects
sorry<00:00:48.960><c> about</c><00:00:49.280><c> that</c><00:00:50.280><c> the</c><00:00:50.399><c> full</c><00:00:50.640><c> list</c><00:00:50.800><c> of</c><00:00:50.960><c> API</c>

00:00:51.310 --> 00:00:51.320 align:start position:0%
sorry about that the full list of API
 

00:00:51.320 --> 00:00:53.430 align:start position:0%
sorry about that the full list of API
changes<00:00:51.640><c> are</c><00:00:51.800><c> linked</c><00:00:52.039><c> in</c><00:00:52.160><c> the</c><00:00:52.280><c> description</c>

00:00:53.430 --> 00:00:53.440 align:start position:0%
changes are linked in the description
 

00:00:53.440 --> 00:00:55.990 align:start position:0%
changes are linked in the description
below<00:00:54.440><c> along</c><00:00:54.680><c> with</c><00:00:54.879><c> those</c><00:00:55.039><c> two</c><00:00:55.239><c> major</c><00:00:55.520><c> changes</c>

00:00:55.990 --> 00:00:56.000 align:start position:0%
below along with those two major changes
 

00:00:56.000 --> 00:00:59.389 align:start position:0%
below along with those two major changes
DH<00:00:56.520><c> now</c><00:00:56.680><c> supports</c><00:00:57.079><c> Minecraft</c><00:00:57.520><c> versions</c><00:00:58.399><c> 1.2.2</c>

00:00:59.389 --> 00:00:59.399 align:start position:0%
DH now supports Minecraft versions 1.2.2
 

00:00:59.399 --> 00:01:03.590 align:start position:0%
DH now supports Minecraft versions 1.2.2
1<00:01:00.000><c> 20.4</c><00:01:00.760><c> and</c><00:01:00.960><c> 1</c><00:01:01.640><c> 1206</c><00:01:02.640><c> bringing</c><00:01:02.960><c> the</c><00:01:03.199><c> supported</c>

00:01:03.590 --> 00:01:03.600 align:start position:0%
1 20.4 and 1 1206 bringing the supported
 

00:01:03.600 --> 00:01:05.789 align:start position:0%
1 20.4 and 1 1206 bringing the supported
version<00:01:03.960><c> count</c><00:01:04.239><c> up</c><00:01:04.360><c> to</c>

00:01:05.789 --> 00:01:05.799 align:start position:0%
version count up to
 

00:01:05.799 --> 00:01:08.670 align:start position:0%
version count up to
9<00:01:06.799><c> moving</c><00:01:07.119><c> along</c><00:01:07.759><c> there</c><00:01:07.960><c> were</c><00:01:08.240><c> several</c>

00:01:08.670 --> 00:01:08.680 align:start position:0%
9 moving along there were several
 

00:01:08.680 --> 00:01:10.670 align:start position:0%
9 moving along there were several
graphical<00:01:09.119><c> improvements</c><00:01:09.640><c> for</c><00:01:09.840><c> your</c><00:01:10.119><c> viewing</c>

00:01:10.670 --> 00:01:10.680 align:start position:0%
graphical improvements for your viewing
 

00:01:10.680 --> 00:01:13.109 align:start position:0%
graphical improvements for your viewing
pleasure<00:01:11.680><c> first</c><00:01:11.920><c> and</c><00:01:12.080><c> foremost</c><00:01:12.759><c> Hollow</c>

00:01:13.109 --> 00:01:13.119 align:start position:0%
pleasure first and foremost Hollow
 

00:01:13.119 --> 00:01:14.630 align:start position:0%
pleasure first and foremost Hollow
structures<00:01:13.560><c> will</c><00:01:13.759><c> no</c><00:01:13.920><c> longer</c><00:01:14.200><c> turn</c><00:01:14.400><c> into</c>

00:01:14.630 --> 00:01:14.640 align:start position:0%
structures will no longer turn into
 

00:01:14.640 --> 00:01:17.950 align:start position:0%
structures will no longer turn into
swiss<00:01:15.000><c> cheese</c><00:01:15.400><c> at</c><00:01:15.560><c> lower</c><00:01:15.840><c> detail</c>

00:01:17.950 --> 00:01:17.960 align:start position:0%
swiss cheese at lower detail
 

00:01:17.960 --> 00:01:20.190 align:start position:0%
swiss cheese at lower detail
levels<00:01:18.960><c> in</c><00:01:19.040><c> order</c><00:01:19.280><c> to</c><00:01:19.439><c> help</c><00:01:19.680><c> smooth</c><00:01:20.040><c> the</c>

00:01:20.190 --> 00:01:20.200 align:start position:0%
levels in order to help smooth the
 

00:01:20.200 --> 00:01:22.149 align:start position:0%
levels in order to help smooth the
transition<00:01:20.799><c> between</c><00:01:21.159><c> vanilla</c><00:01:21.600><c> and</c><00:01:21.720><c> LOD</c>

00:01:22.149 --> 00:01:22.159 align:start position:0%
transition between vanilla and LOD
 

00:01:22.159 --> 00:01:26.030 align:start position:0%
transition between vanilla and LOD
chunks<00:01:22.880><c> grass</c><00:01:23.159><c> will</c><00:01:23.360><c> now</c><00:01:23.520><c> fade</c><00:01:23.799><c> from</c><00:01:24.079><c> green</c><00:01:24.360><c> to</c>

00:01:26.030 --> 00:01:26.040 align:start position:0%
chunks grass will now fade from green to
 

00:01:26.040 --> 00:01:28.510 align:start position:0%
chunks grass will now fade from green to
Brown<00:01:27.040><c> well</c><00:01:27.200><c> I</c><00:01:27.320><c> don't</c><00:01:27.560><c> recommend</c><00:01:28.040><c> using</c><00:01:28.360><c> this</c>

00:01:28.510 --> 00:01:28.520 align:start position:0%
Brown well I don't recommend using this
 

00:01:28.520 --> 00:01:29.950 align:start position:0%
Brown well I don't recommend using this
setting<00:01:28.840><c> unless</c><00:01:29.119><c> you</c><00:01:29.240><c> want</c><00:01:29.360><c> to</c><00:01:29.479><c> stretch</c><00:01:29.759><c> your</c>

00:01:29.950 --> 00:01:29.960 align:start position:0%
setting unless you want to stretch your
 

00:01:29.960 --> 00:01:32.469 align:start position:0%
setting unless you want to stretch your
your<00:01:30.079><c> GPU</c><00:01:30.439><c> to</c><00:01:30.600><c> the</c><00:01:30.759><c> max</c><00:01:31.479><c> you</c><00:01:31.640><c> can</c><00:01:31.880><c> now</c><00:01:32.040><c> render</c>

00:01:32.469 --> 00:01:32.479 align:start position:0%
your GPU to the max you can now render
 

00:01:32.479 --> 00:01:34.310 align:start position:0%
your GPU to the max you can now render
vertical<00:01:32.960><c> structures</c><00:01:33.439><c> like</c><00:01:33.640><c> pixelart</c><00:01:34.159><c> with</c>

00:01:34.310 --> 00:01:34.320 align:start position:0%
vertical structures like pixelart with
 

00:01:34.320 --> 00:01:38.429 align:start position:0%
vertical structures like pixelart with
almost<00:01:34.680><c> no</c><00:01:34.920><c> quality</c>

00:01:38.429 --> 00:01:38.439 align:start position:0%
 
 

00:01:38.439 --> 00:01:40.990 align:start position:0%
 
loss<00:01:39.439><c> along</c><00:01:39.759><c> with</c><00:01:39.920><c> all</c><00:01:40.200><c> those</c><00:01:40.399><c> new</c><00:01:40.640><c> visual</c>

00:01:40.990 --> 00:01:41.000 align:start position:0%
loss along with all those new visual
 

00:01:41.000 --> 00:01:43.230 align:start position:0%
loss along with all those new visual
changes<00:01:41.640><c> there</c><00:01:41.759><c> were</c><00:01:42.040><c> several</c><00:01:42.479><c> large</c><00:01:42.840><c> backend</c>

00:01:43.230 --> 00:01:43.240 align:start position:0%
changes there were several large backend
 

00:01:43.240 --> 00:01:45.590 align:start position:0%
changes there were several large backend
changes<00:01:43.640><c> as</c><00:01:43.799><c> well</c><00:01:44.520><c> the</c><00:01:44.680><c> largest</c><00:01:45.040><c> of</c><00:01:45.240><c> which</c><00:01:45.439><c> was</c>

00:01:45.590 --> 00:01:45.600 align:start position:0%
changes as well the largest of which was
 

00:01:45.600 --> 00:01:48.190 align:start position:0%
changes as well the largest of which was
the<00:01:45.880><c> change</c><00:01:46.159><c> to</c><00:01:46.360><c> dh's</c><00:01:47.040><c> database</c><00:01:47.520><c> format</c><00:01:48.040><c> to</c>

00:01:48.190 --> 00:01:48.200 align:start position:0%
the change to dh's database format to
 

00:01:48.200 --> 00:01:50.990 align:start position:0%
the change to dh's database format to
address<00:01:48.560><c> two</c><00:01:48.799><c> major</c><00:01:49.159><c> issues</c><00:01:50.159><c> but</c><00:01:50.320><c> don't</c><00:01:50.520><c> worry</c>

00:01:50.990 --> 00:01:51.000 align:start position:0%
address two major issues but don't worry
 

00:01:51.000 --> 00:01:52.830 align:start position:0%
address two major issues but don't worry
you<00:01:51.079><c> won't</c><00:01:51.320><c> have</c><00:01:51.439><c> to</c><00:01:51.560><c> regenerate</c><00:01:52.119><c> anything</c>

00:01:52.830 --> 00:01:52.840 align:start position:0%
you won't have to regenerate anything
 

00:01:52.840 --> 00:01:54.429 align:start position:0%
you won't have to regenerate anything
just<00:01:53.000><c> launch</c><00:01:53.280><c> your</c><00:01:53.439><c> world</c><00:01:53.719><c> and</c><00:01:53.920><c> DH</c><00:01:54.280><c> will</c>

00:01:54.429 --> 00:01:54.439 align:start position:0%
just launch your world and DH will
 

00:01:54.439 --> 00:01:57.069 align:start position:0%
just launch your world and DH will
automatically<00:01:55.000><c> migrate</c><00:01:55.320><c> to</c><00:01:55.439><c> the</c><00:01:55.560><c> new</c><00:01:56.079><c> version</c>

00:01:57.069 --> 00:01:57.079 align:start position:0%
automatically migrate to the new version
 

00:01:57.079 --> 00:01:58.910 align:start position:0%
automatically migrate to the new version
just<00:01:57.360><c> be</c><00:01:57.520><c> aware</c><00:01:57.799><c> that</c><00:01:57.920><c> it</c><00:01:58.039><c> will</c><00:01:58.280><c> take</c><00:01:58.439><c> a</c><00:01:58.600><c> while</c>

00:01:58.910 --> 00:01:58.920 align:start position:0%
just be aware that it will take a while
 

00:01:58.920 --> 00:02:00.749 align:start position:0%
just be aware that it will take a while
if<00:01:59.000><c> you</c><00:01:59.119><c> generated</c><00:01:59.560><c> a</c><00:01:59.600><c> lot</c><00:01:59.719><c> of</c><00:02:00.000><c> lods</c><00:02:00.439><c> and</c><00:02:00.600><c> have</c>

00:02:00.749 --> 00:02:00.759 align:start position:0%
if you generated a lot of lods and have
 

00:02:00.759 --> 00:02:02.950 align:start position:0%
if you generated a lot of lods and have
a<00:02:00.920><c> large</c>

00:02:02.950 --> 00:02:02.960 align:start position:0%
a large
 

00:02:02.960 --> 00:02:05.550 align:start position:0%
a large
database<00:02:03.960><c> one</c><00:02:04.119><c> of</c><00:02:04.360><c> those</c><00:02:04.600><c> issues</c><00:02:05.200><c> was</c><00:02:05.399><c> with</c>

00:02:05.550 --> 00:02:05.560 align:start position:0%
database one of those issues was with
 

00:02:05.560 --> 00:02:07.709 align:start position:0%
database one of those issues was with
World<00:02:05.840><c> gen</c><00:02:06.520><c> the</c><00:02:06.640><c> old</c><00:02:06.880><c> format</c><00:02:07.280><c> had</c><00:02:07.399><c> trouble</c>

00:02:07.709 --> 00:02:07.719 align:start position:0%
World gen the old format had trouble
 

00:02:07.719 --> 00:02:09.790 align:start position:0%
World gen the old format had trouble
determining<00:02:08.319><c> which</c><00:02:08.479><c> lods</c><00:02:09.039><c> were</c><00:02:09.319><c> or</c><00:02:09.479><c> weren't</c>

00:02:09.790 --> 00:02:09.800 align:start position:0%
determining which lods were or weren't
 

00:02:09.800 --> 00:02:11.949 align:start position:0%
determining which lods were or weren't
generated<00:02:10.679><c> which</c><00:02:10.920><c> caused</c><00:02:11.319><c> problems</c><00:02:11.680><c> like</c>

00:02:11.949 --> 00:02:11.959 align:start position:0%
generated which caused problems like
 

00:02:11.959 --> 00:02:15.589 align:start position:0%
generated which caused problems like
this<00:02:12.800><c> or</c><00:02:13.120><c> generating</c><00:02:13.560><c> areas</c><00:02:14.120><c> twice</c><00:02:15.120><c> luckily</c>

00:02:15.589 --> 00:02:15.599 align:start position:0%
this or generating areas twice luckily
 

00:02:15.599 --> 00:02:17.110 align:start position:0%
this or generating areas twice luckily
those<00:02:15.879><c> problems</c><00:02:16.120><c> are</c><00:02:16.319><c> both</c><00:02:16.519><c> solved</c><00:02:16.879><c> with</c><00:02:17.000><c> the</c>

00:02:17.110 --> 00:02:17.120 align:start position:0%
those problems are both solved with the
 

00:02:17.120 --> 00:02:19.790 align:start position:0%
those problems are both solved with the
new<00:02:17.319><c> system</c><00:02:18.280><c> and</c><00:02:18.440><c> as</c><00:02:18.560><c> a</c><00:02:18.720><c> nice</c><00:02:18.920><c> bonus</c><00:02:19.400><c> the</c><00:02:19.480><c> world</c>

00:02:19.790 --> 00:02:19.800 align:start position:0%
new system and as a nice bonus the world
 

00:02:19.800 --> 00:02:21.470 align:start position:0%
new system and as a nice bonus the world
generator<00:02:20.239><c> now</c><00:02:20.440><c> handles</c><00:02:20.800><c> extreme</c><00:02:21.120><c> render</c>

00:02:21.470 --> 00:02:21.480 align:start position:0%
generator now handles extreme render
 

00:02:21.480 --> 00:02:24.110 align:start position:0%
generator now handles extreme render
distances<00:02:22.120><c> much</c><00:02:22.360><c> better</c><00:02:23.360><c> so</c><00:02:23.599><c> if</c><00:02:23.720><c> you</c><00:02:23.879><c> want</c><00:02:24.000><c> to</c>

00:02:24.110 --> 00:02:24.120 align:start position:0%
distances much better so if you want to
 

00:02:24.120 --> 00:02:25.830 align:start position:0%
distances much better so if you want to
wait<00:02:24.319><c> the</c><00:02:24.440><c> 30</c><00:02:24.760><c> hours</c><00:02:25.080><c> to</c><00:02:25.239><c> generate</c><00:02:25.599><c> all</c><00:02:25.760><c> the</c>

00:02:25.830 --> 00:02:25.840 align:start position:0%
wait the 30 hours to generate all the
 

00:02:25.840 --> 00:02:28.710 align:start position:0%
wait the 30 hours to generate all the
way<00:02:25.959><c> out</c><00:02:26.080><c> to</c><00:02:26.239><c> 1024</c><00:02:26.840><c> render</c><00:02:27.200><c> distance</c><00:02:28.040><c> DH</c><00:02:28.519><c> will</c>

00:02:28.710 --> 00:02:28.720 align:start position:0%
way out to 1024 render distance DH will
 

00:02:28.720 --> 00:02:31.990 align:start position:0%
way out to 1024 render distance DH will
work<00:02:29.120><c> much</c><00:02:29.400><c> better</c>

00:02:31.990 --> 00:02:32.000 align:start position:0%
 
 

00:02:32.000 --> 00:02:33.790 align:start position:0%
 
along<00:02:32.239><c> with</c><00:02:32.360><c> the</c><00:02:32.480><c> new</c><00:02:32.640><c> world</c><00:02:32.879><c> gen</c><00:02:33.160><c> handling</c><00:02:33.640><c> we</c>

00:02:33.790 --> 00:02:33.800 align:start position:0%
along with the new world gen handling we
 

00:02:33.800 --> 00:02:35.710 align:start position:0%
along with the new world gen handling we
have<00:02:33.959><c> new</c><00:02:34.200><c> lossy</c><00:02:34.760><c> and</c><00:02:34.959><c> lossless</c><00:02:35.480><c> data</c>

00:02:35.710 --> 00:02:35.720 align:start position:0%
have new lossy and lossless data
 

00:02:35.720 --> 00:02:37.670 align:start position:0%
have new lossy and lossless data
compression<00:02:36.560><c> which</c><00:02:36.800><c> combined</c><00:02:37.239><c> can</c><00:02:37.360><c> reduce</c>

00:02:37.670 --> 00:02:37.680 align:start position:0%
compression which combined can reduce
 

00:02:37.680 --> 00:02:40.670 align:start position:0%
compression which combined can reduce
file<00:02:38.080><c> sizes</c><00:02:38.440><c> to</c><00:02:38.680><c> onethird</c><00:02:39.400><c> the</c><00:02:39.599><c> size</c><00:02:39.920><c> of</c>

00:02:40.670 --> 00:02:40.680 align:start position:0%
file sizes to onethird the size of
 

00:02:40.680 --> 00:02:42.949 align:start position:0%
file sizes to onethird the size of
dh2<00:02:41.680><c> just</c><00:02:41.840><c> be</c><00:02:41.959><c> aware</c><00:02:42.239><c> that</c><00:02:42.400><c> this</c><00:02:42.519><c> reduction</c>

00:02:42.949 --> 00:02:42.959 align:start position:0%
dh2 just be aware that this reduction
 

00:02:42.959 --> 00:02:44.990 align:start position:0%
dh2 just be aware that this reduction
won't<00:02:43.200><c> be</c><00:02:43.319><c> seen</c><00:02:43.560><c> for</c><00:02:43.760><c> old</c><00:02:44.000><c> migrated</c><00:02:44.480><c> worlds</c>

00:02:44.990 --> 00:02:45.000 align:start position:0%
won't be seen for old migrated worlds
 

00:02:45.000 --> 00:02:46.630 align:start position:0%
won't be seen for old migrated worlds
because<00:02:45.239><c> the</c><00:02:45.360><c> process</c><00:02:45.680><c> to</c><00:02:45.920><c> vacuum</c><00:02:46.239><c> a</c><00:02:46.360><c> large</c>

00:02:46.630 --> 00:02:46.640 align:start position:0%
because the process to vacuum a large
 

00:02:46.640 --> 00:02:49.030 align:start position:0%
because the process to vacuum a large
database<00:02:47.040><c> can</c><00:02:47.200><c> take</c><00:02:47.480><c> tens</c><00:02:47.760><c> of</c><00:02:47.959><c> minutes</c><00:02:48.800><c> and</c><00:02:48.920><c> we</c>

00:02:49.030 --> 00:02:49.040 align:start position:0%
database can take tens of minutes and we
 

00:02:49.040 --> 00:02:50.550 align:start position:0%
database can take tens of minutes and we
don't<00:02:49.200><c> want</c><00:02:49.280><c> to</c><00:02:49.440><c> make</c><00:02:49.599><c> you</c><00:02:49.800><c> wait</c><00:02:50.080><c> that</c><00:02:50.239><c> long</c><00:02:50.440><c> to</c>

00:02:50.550 --> 00:02:50.560 align:start position:0%
don't want to make you wait that long to
 

00:02:50.560 --> 00:02:52.110 align:start position:0%
don't want to make you wait that long to
load<00:02:50.800><c> into</c><00:02:51.000><c> a</c>

00:02:52.110 --> 00:02:52.120 align:start position:0%
load into a
 

00:02:52.120 --> 00:02:54.270 align:start position:0%
load into a
world<00:02:53.120><c> continuing</c><00:02:53.640><c> with</c><00:02:53.760><c> the</c><00:02:53.920><c> backend</c>

00:02:54.270 --> 00:02:54.280 align:start position:0%
world continuing with the backend
 

00:02:54.280 --> 00:02:55.910 align:start position:0%
world continuing with the backend
changes<00:02:54.920><c> we</c><00:02:55.040><c> have</c><00:02:55.159><c> a</c><00:02:55.280><c> few</c><00:02:55.519><c> performance</c>

00:02:55.910 --> 00:02:55.920 align:start position:0%
changes we have a few performance
 

00:02:55.920 --> 00:02:57.309 align:start position:0%
changes we have a few performance
improvements<00:02:56.360><c> y'all</c><00:02:56.560><c> will</c><00:02:56.680><c> be</c><00:02:56.840><c> very</c><00:02:57.000><c> excited</c>

00:02:57.309 --> 00:02:57.319 align:start position:0%
improvements y'all will be very excited
 

00:02:57.319 --> 00:03:00.070 align:start position:0%
improvements y'all will be very excited
to<00:02:57.440><c> hear</c><00:02:57.599><c> about</c><00:02:58.599><c> DH</c><00:02:59.040><c> is</c><00:02:59.200><c> now</c><00:02:59.360><c> significant</c><00:03:00.000><c> L</c>

00:03:00.070 --> 00:03:00.080 align:start position:0%
to hear about DH is now significant L
 

00:03:00.080 --> 00:03:02.670 align:start position:0%
to hear about DH is now significant L
more<00:03:00.200><c> memory</c><00:03:00.519><c> efficient</c><00:03:01.440><c> you</c><00:03:01.560><c> can</c><00:03:01.720><c> run</c><00:03:02.040><c> 512</c>

00:03:02.670 --> 00:03:02.680 align:start position:0%
more memory efficient you can run 512
 

00:03:02.680 --> 00:03:04.390 align:start position:0%
more memory efficient you can run 512
render<00:03:03.000><c> distance</c><00:03:03.760><c> assuming</c><00:03:04.080><c> you've</c><00:03:04.239><c> already</c>

00:03:04.390 --> 00:03:04.400 align:start position:0%
render distance assuming you've already
 

00:03:04.400 --> 00:03:05.949 align:start position:0%
render distance assuming you've already
waited<00:03:04.640><c> the</c><00:03:04.720><c> 8</c><00:03:04.920><c> hours</c><00:03:05.159><c> needed</c><00:03:05.400><c> to</c><00:03:05.480><c> generate</c><00:03:05.799><c> it</c>

00:03:05.949 --> 00:03:05.959 align:start position:0%
waited the 8 hours needed to generate it
 

00:03:05.959 --> 00:03:09.350 align:start position:0%
waited the 8 hours needed to generate it
all<00:03:06.599><c> with</c><00:03:06.720><c> only</c><00:03:06.920><c> 2</c><00:03:07.159><c> GB</c><00:03:07.519><c> of</c><00:03:07.920><c> memory</c><00:03:08.920><c> although</c>

00:03:09.350 --> 00:03:09.360 align:start position:0%
all with only 2 GB of memory although
 

00:03:09.360 --> 00:03:11.390 align:start position:0%
all with only 2 GB of memory although
I'd<00:03:09.560><c> still</c><00:03:09.840><c> recommend</c><00:03:10.239><c> four</c><00:03:10.519><c> or</c><00:03:10.760><c> more</c>

00:03:11.390 --> 00:03:11.400 align:start position:0%
I'd still recommend four or more
 

00:03:11.400 --> 00:03:12.750 align:start position:0%
I'd still recommend four or more
especially<00:03:11.799><c> if</c><00:03:11.879><c> you</c><00:03:12.000><c> want</c><00:03:12.120><c> to</c><00:03:12.239><c> run</c><00:03:12.400><c> the</c><00:03:12.519><c> world</c>

00:03:12.750 --> 00:03:12.760 align:start position:0%
especially if you want to run the world
 

00:03:12.760 --> 00:03:14.710 align:start position:0%
especially if you want to run the world
generator<00:03:13.560><c> since</c><00:03:13.840><c> that</c><00:03:14.000><c> uses</c><00:03:14.319><c> Minecraft</c>

00:03:14.710 --> 00:03:14.720 align:start position:0%
generator since that uses Minecraft
 

00:03:14.720 --> 00:03:16.630 align:start position:0%
generator since that uses Minecraft
world<00:03:14.959><c> gen</c><00:03:15.200><c> code</c><00:03:15.640><c> which</c><00:03:15.799><c> is</c><00:03:16.000><c> still</c><00:03:16.360><c> pretty</c>

00:03:16.630 --> 00:03:16.640 align:start position:0%
world gen code which is still pretty
 

00:03:16.640 --> 00:03:19.509 align:start position:0%
world gen code which is still pretty
memory

00:03:19.509 --> 00:03:19.519 align:start position:0%
 
 

00:03:19.519 --> 00:03:22.350 align:start position:0%
 
hungry<00:03:20.519><c> lastly</c><00:03:21.040><c> but</c><00:03:21.159><c> certainly</c><00:03:21.519><c> not</c><00:03:21.760><c> least</c>

00:03:22.350 --> 00:03:22.360 align:start position:0%
hungry lastly but certainly not least
 

00:03:22.360 --> 00:03:24.149 align:start position:0%
hungry lastly but certainly not least
thanks<00:03:22.560><c> to</c><00:03:22.720><c> null's</c><00:03:23.159><c> hard</c><00:03:23.360><c> work</c><00:03:23.680><c> we</c><00:03:23.879><c> now</c><00:03:24.040><c> have</c>

00:03:24.149 --> 00:03:24.159 align:start position:0%
thanks to null's hard work we now have
 

00:03:24.159 --> 00:03:25.990 align:start position:0%
thanks to null's hard work we now have
frustum<00:03:24.599><c> calling</c><00:03:25.319><c> which</c><00:03:25.480><c> means</c><00:03:25.680><c> you</c><00:03:25.799><c> can</c>

00:03:25.990 --> 00:03:26.000 align:start position:0%
frustum calling which means you can
 

00:03:26.000 --> 00:03:29.010 align:start position:0%
frustum calling which means you can
expect<00:03:26.280><c> a</c><00:03:26.519><c> significant</c><00:03:27.120><c> FPS</c><00:03:27.560><c> Improvement</c>

00:03:29.010 --> 00:03:29.020 align:start position:0%
expect a significant FPS Improvement
 

00:03:29.020 --> 00:03:30.750 align:start position:0%
expect a significant FPS Improvement
[Music]

00:03:30.750 --> 00:03:30.760 align:start position:0%
[Music]
 

00:03:30.760 --> 00:03:32.270 align:start position:0%
[Music]
apologies<00:03:31.200><c> for</c><00:03:31.360><c> the</c><00:03:31.480><c> long</c><00:03:31.720><c> time</c><00:03:31.959><c> between</c>

00:03:32.270 --> 00:03:32.280 align:start position:0%
apologies for the long time between
 

00:03:32.280 --> 00:03:34.270 align:start position:0%
apologies for the long time between
updates<00:03:33.000><c> I</c><00:03:33.080><c> was</c><00:03:33.239><c> hoping</c><00:03:33.480><c> to</c><00:03:33.599><c> have</c><00:03:33.720><c> a</c><00:03:33.879><c> smaller</c>

00:03:34.270 --> 00:03:34.280 align:start position:0%
updates I was hoping to have a smaller
 

00:03:34.280 --> 00:03:36.710 align:start position:0%
updates I was hoping to have a smaller
update<00:03:34.599><c> out</c><00:03:34.799><c> much</c><00:03:35.000><c> sooner</c><00:03:35.840><c> but</c><00:03:36.080><c> the</c><00:03:36.159><c> world</c><00:03:36.439><c> gen</c>

00:03:36.710 --> 00:03:36.720 align:start position:0%
update out much sooner but the world gen
 

00:03:36.720 --> 00:03:38.309 align:start position:0%
update out much sooner but the world gen
and<00:03:36.879><c> file</c><00:03:37.159><c> size</c><00:03:37.400><c> issues</c><00:03:37.760><c> ended</c><00:03:37.959><c> up</c><00:03:38.080><c> being</c>

00:03:38.309 --> 00:03:38.319 align:start position:0%
and file size issues ended up being
 

00:03:38.319 --> 00:03:40.070 align:start position:0%
and file size issues ended up being
something<00:03:38.599><c> I</c><00:03:38.720><c> couldn't</c><00:03:39.040><c> ignore</c><00:03:39.599><c> which</c><00:03:39.840><c> both</c>

00:03:40.070 --> 00:03:40.080 align:start position:0%
something I couldn't ignore which both
 

00:03:40.080 --> 00:03:41.949 align:start position:0%
something I couldn't ignore which both
required<00:03:40.599><c> major</c><00:03:40.959><c> changes</c><00:03:41.360><c> that</c><00:03:41.480><c> took</c><00:03:41.680><c> months</c>

00:03:41.949 --> 00:03:41.959 align:start position:0%
required major changes that took months
 

00:03:41.959 --> 00:03:44.550 align:start position:0%
required major changes that took months
to<00:03:42.280><c> finish</c><00:03:43.280><c> it</c><00:03:43.400><c> would</c><00:03:43.519><c> have</c><00:03:43.640><c> been</c><00:03:43.840><c> much</c><00:03:44.120><c> faster</c>

00:03:44.550 --> 00:03:44.560 align:start position:0%
to finish it would have been much faster
 

00:03:44.560 --> 00:03:46.229 align:start position:0%
to finish it would have been much faster
if<00:03:44.680><c> I</c><00:03:44.760><c> could</c><00:03:44.920><c> do</c><00:03:45.040><c> this</c>

00:03:46.229 --> 00:03:46.239 align:start position:0%
if I could do this
 

00:03:46.239 --> 00:03:48.070 align:start position:0%
if I could do this
full-time

00:03:48.070 --> 00:03:48.080 align:start position:0%
full-time
 

00:03:48.080 --> 00:03:54.830 align:start position:0%
full-time
H<00:03:49.080><c> hey</c><00:03:49.319><c> Mojang</c><00:03:50.319><c> are</c><00:03:50.439><c> you</c><00:03:50.640><c> hiring</c>

00:03:54.830 --> 00:03:54.840 align:start position:0%
 
 

00:03:54.840 --> 00:04:25.870 align:start position:0%
 
[Music]

00:04:25.870 --> 00:04:25.880 align:start position:0%
[Music]
 

00:04:25.880 --> 00:04:28.189 align:start position:0%
[Music]
I'm<00:04:26.880><c> call</c><00:04:27.199><c> me</c>

00:04:28.189 --> 00:04:28.199 align:start position:0%
I'm call me
 

00:04:28.199 --> 00:04:32.880 align:start position:0%
I'm call me
down<00:04:29.199><c> so</c><00:04:29.880><c> more</c>