How Quake's software renderer ELIMINATES overdraw [⚠️ flashing images]
A description of the techniques used by Quake to render a fully 3D game on original Pentium hardware. Support: https://www.buymeacoffee.com/mattsram... Mastodon: https://mastodon.cloud/@mattsramblings/ 00:00 Intro 00:35 Polygons in BSP trees 01:14 Frustum culling 02:05 PVS culling 02:55 Back-face culling 03:42 Spans 04:58 Active edge list 05:51 Active polygon list 07:09 Black book
▶︎
How 1999 Quake 3 Teaches Elite Software Engineering
▶︎
Uncovering Quake's unseen collision hulls
▶︎
Unreal Engine 5 | Stop Casting Learn Interfaces | How to use Blueprint Interfaces | Latest Tutorial
▶︎
Quake changed video games forever | John Carmack and Lex Fridman
▶︎
Coding Adventure: Software Rasterizer
▶︎
How Ray Tracing (Modern CGI) Works And How To Do It 600x Faster
▶︎
I added portals into software Quake
▶︎
REVEALED: Quake III's SECRET Algorithm!
▶︎
So I Reviewed the DOOM 3 Source Code..
▶︎
How Quake Failed their way to Success
▶︎
Commodore VIC 20 in an Alternate Universe
▶︎
3D Rendering with Binary Space Partitions
▶︎
We let AI buy a robot and a car, it does exactly what experts warned.
▶︎
14 Best RTS Games That are Still Worth Playing
▶︎
How Rockstar fit an entire city into PlayStation 2 memory
▶︎
BSP Trees: The Magic Behind Collision Detection in Quake
▶︎
Let's Program Doom - Part 1
▶︎
Remember 3D games with software render?
▶︎
I Gave ChatGPT a Body
▶︎