Where I download it?

20 years i ve waited for this video

How do you avoid the portal clipping the near plane as you pass through it? Also doesn't Quake use PVS, so are you doing PVS lookup for the viewpoint transformed into the portal destination space (which might be behind a wall) or from the portal itself somehow?

Does the pre-calculated expanded collision hulls mean that everything that moves has to be either a point, player sized, or ogre sized? I mean... you can do tricks like calculating as a point and then backing off a bit to handle stuff like grenades landing on floors, but the vore and shambler don't seem so easy.

this animation/teaching is 50 years ahead of university course

"Purpose"? Where we're going, we don't need purpose!

Great breakdown, thank you. Having done my own reading of the Black Book, and other of Abrash's articles (which seem to be the most time capsule-y articles available on the Quake engine development) I'm struck by how pragmatic many of the choices made in building the engine were. For example, the PVS doesn't eliminate overdraw by itself, but it greatly reduces it. Carmack knew it was stupid to try to get the PVS perfect (in fact, fine-grained PVS is still an open problem today). PVS as implemented in quake gets the set of polygons low enough that span buffers can be used -- span buffers being even for the time a slightly outdated algorithm, that was designed in a time when writing a pixel was very, very slow, to completely eliminate the remaining overdraw. Overdraw in drawing the world was very expensive because every pixel had to be textured and lit, and world polygons tend to be large. But then at model drawing time, Carmack just said fuck it, the polys are small enough that we'll just the z-buffer.

Do you have any videos of your/a 'humanized' bot completing a Defrag map? I've seen a non-humanized one during a Defrag tournament, but I have wanted to see one performing something that could potentially be done by a human (not cyborg.)

It is actually not hidden.

Yes. I had no idea how that TAS thing worked, I assumed it switches back and forth too fast to see, but that didn't sound right, rendering would show the flicker, there is no smoothing in Quake. But if it directly controls wishdir, then yeah, that explains it.

I'm sorry but what does quantizing mean

This is excellent

i know exactly 0% about codes and scripts, and yet i 100% understood this! i've always been curious as to how wallrunning specifically works super well done ♥

How would you calculate the optimal wishdir values given the player’s velocity? The table you showed in the video looks great, what is the formula for that?

Could you explain how the objects are rendered?

I really hope this gets more views. You skilled visual explanation are amazing.

Are you sure about if is the Minkowski difference used in Quake? Why is it that they never mention this in Michael Abrash's black book? I mean... I understand that Bruce Naylor went to id Software in 1994 to explain to Carmack how to take advantage of BSP Tree for Collision Detection (Doom doesn't use that approach), but I don't know if he explained to him that he could use the Minkowski difference (as what we now know as GJK). It would make me very happy to know where you got the idea that they used Minkowski Difference in Quake, or if it was just an approach you came up with for the video. Thank you so much and great video!

I wonder if ericw tools can be made to to work in goldsrc, or mabye ACTUAL quake

What is your education?

Excellent video! I’ve been playing for 10 years and ironically the day after I finished my grad school linear algebra final project I see this video! Loved it.

Carmack you're a genius

Watching this almost 20 years after I discovered Defrag is pretty nostalgic :>

The Black Book is one of my favorite things from childhood. It was always just out of reach but I still learned things that helped me in my career. Good stuff.

Love your videos! Can I request a video discussing how Quake stores the actual polygon data used for drawing? Not so much the bsp, but moreso the surfaces / triangles / verts / polygons used for drawing the walls of a map, etc, and how does this differ from other full 3d engines of the time? (ie System Shock, Unreal, etc)

Just ran through RTCW at 144 (matching monitor). Started a new playthrough and remembered capping at 333 FPS from W:ET. The difference is so huge in game that I had to look it up. Interesting video!

Hello Mike, would you briefly explain why holding forward while in the air in Quake causes you to lose speed when attempting to bunny hop? It's one of the difficult transitions for me is going from Quake 2 or Quake 3 asd having to let go of forward while in the air because you want to keep holding forward in Q2/Q3. I always wondered what it is that causes the speed loss in Quake 1 when holding forward.

Great video.

Its amazing how much game programming boils down to the simple dot product ie: backface culling check. You can do SOOO much with it its insane.

Awesome! Implementation as in Duke Nukem 3D ))) There where lot of custom levels in use with non-euclidean geometry, the most fun experience for multiplayer setups.

Love your videos and style, Matt! Right now, I'm learning about shaders and have no idea how I would even approach making a video like this. The arrows and the grid look gorgeous and flow really well with the graph. Do you use a program, or did you make the shaders yourself? I see you put in a lot of effort into this, and it'd be very interesting to know how you did it

Amazing video

An amazingly detailed, yet still easy to follow. You've explained it exceptionally well, thank you for this video!

This video is a pearl. Awesome. Although I didn't get some of the concepts, I gotta say the animations are perfect and explanation very clear. Question: how did the compiler find a good portal? And how did carmack arrive to all those ideas?

Really thanks for this ultra very well done video. I'm almost 40 now, but when I tried to study this stuff in the 2000s it was very difficult. Can't even believe you can find this kind of videos today, showing the unmatchable brilliance of Carmack. I didn't even know there were more thatn one BPS tree, made just for collision detection. When I was writing my own 3D engine back in 2000s, I had the very same problem, solved by expanding the geometry (an idea I had along with a friend of mine), but the final result was not stable. How could Carmack come up with this idea? thanks!

you don't deserves a coffee, you deserves a hole building with a cafeteria inside.

I don't understand why you chose green as the solid color and gray as the empty color it's so counter-intuitive

Honestly I'd love to see you look at the overlaps with wheel modifier like dirt and ice on entering tarmac. I assume it's a value averageing the two surfaces it involves but still would be nice to have it confirmed.

What a bug!

someone tell me why accelerate is not clipped to zero? why they can be negative number??( ・・？）

It's great to see a visual example of what BSP splitting looks like using 3D volumes instead of just 2D areas

So beautiful to see how neat and tidy this system is.

The animation is amazing! How did you make them? I mean splitting the level in chunks.

I seem to remember that the original Unreal engine had support for portals like this?

You assume that we know what an iteration is 🎉😂😂❤

isnt easier to use instead goldsrc

Did you try using this technique to make reflective surfaces? I think this is how duke nukem and Unreal did mirrors, IIRC

Small correction at 2:54 : affine is not a linear transformation, as it includes shifting the origin

the fan maps on the same level as the source maps where youll go "wait thats [engine]?"

Look who's back!

One video you could try and do is explain why you could have only 5 or so enemies in one screen.