Discussions: 2026-W43 — page 9
Discussions added each week. These are publication dates here; the original episodes may be older.
- 1:28:25–1:32:21
Sweeney and Fridman examine how lighting and technical art produce detailed dirt and snow in a demonstration.
- 1:24:55–1:28:25
Sweeney contrasts advances in graphics with older networking and simulation systems he wants to redesign.
- 1:20:43–1:24:55
Sweeney praises Carmack’s willingness to rewrite code and describes successive generations of Unreal’s renderer.
- 1:17:05–1:20:43
Sweeney recalls deriving a fog approximation after seeing an image he thought had been rendered in real time.
- 1:12:35–1:17:05
Sweeney explains light maps, precomputed shadows and practical compromises for dynamic lighting in early Unreal.
- 1:09:44–1:12:35
Sweeney recalls a long coding session and describes the geometric edge cases he needed to handle.
- 1:06:36–1:09:44
Sweeney explains constructive solid geometry and recalls making additive and subtractive editing available to artists.
- 1:01:45–1:06:36
Sweeney describes Unreal Engine’s uses and recalls outside developers licensing its tools before the game shipped.
- 56:49–1:01:45
Sweeney explains Nanite’s approach to geometric detail and the problem of visible changes as objects move.
- 52:37–56:49
Sweeney describes optimising software rendering before hardware graphics became a practical target.
- 48:27–52:37
Sweeney discusses Unreal’s move to C++ and the computers he bought to improve development productivity.
- 45:04–48:27
Sweeney explains how inexperienced artists and programmers learned to work together through frequent playable builds.
- 42:38–45:04
Sweeney recalls Unreal’s prolonged development, financial strain and experiments with lighting and fog.
- 39:35–42:38
Sweeney describes learning 3D graphics from Michael Abrash and bringing Epic’s developers together for Unreal.
- 36:11–39:35
Sweeney recalls assembling remote development teams and the impact of Wolfenstein and Doom on Epic’s plans.
- 34:29–36:11
Sweeney describes encouragement from early players and the limited capital needed for his first games.
- 30:31–34:29
Sweeney recommends distinctive games, low entry friction and creator tools as ways for small developers to find an audience.
- 26:16–30:31
Sweeney recalls local bulletin boards and the transition through retail boxes to digital game distribution.
- 24:11–26:16
Sweeney describes games and development tools supporting each other, then discusses sharing online services with developers.
- 20:43–24:11
Sweeney recalls international shareware orders and explains why he shipped ZZT’s editor to players.
- 17:36–20:43
Sweeney describes turning a text editor into ZZT and testing its levels with neighbours before release.
- 13:25–17:36
Sweeney recalls unstructured childhood projects and explains how early games made him want to build development tools.
- 10:10–13:25
Sweeney discusses learning mathematics, programming through practice and valuing knowledge over credentials.
- 7:12–10:10
Sweeney connects hobby projects and engineering mathematics with the skills he later used to build Unreal.