Business

Sweeney recalls learning BASIC on his brother’s computer and building games, compilers and bulletin-board software.

Early Epic

Sweeney connects hobby projects and engineering mathematics with the skills he later used to build Unreal.

Early Epic

Sweeney discusses learning mathematics, programming through practice and valuing knowledge over credentials.

Early Epic

Sweeney recalls unstructured childhood projects and explains how early games made him want to build development tools.

Early Epic

Sweeney describes turning a text editor into ZZT and testing its levels with neighbours before release.

Early Epic

Sweeney recalls international shareware orders and explains why he shipped ZZT’s editor to players.

Early Epic

Research note: The original ZZT package already invited players to build →

Sweeney describes games and development tools supporting each other, then discusses sharing online services with developers.

Early Epic

Sweeney recalls local bulletin boards and the transition through retail boxes to digital game distribution.

Early Epic

Sweeney recommends distinctive games, low entry friction and creator tools as ways for small developers to find an audience.

Early Epic

Sweeney describes encouragement from early players and the limited capital needed for his first games.

Early Epic

Sweeney recalls assembling remote development teams and the impact of Wolfenstein and Doom on Epic’s plans.

Early Epic

Sweeney describes learning 3D graphics from Michael Abrash and bringing Epic’s developers together for Unreal.

Early Epic

Sweeney recalls Unreal’s prolonged development, financial strain and experiments with lighting and fog.

Early Epic

Sweeney explains how inexperienced artists and programmers learned to work together through frequent playable builds.

Early Epic

Sweeney discusses Unreal’s move to C++ and the computers he bought to improve development productivity.

Early Epic

Sweeney describes optimising software rendering before hardware graphics became a practical target.

Graphics

Sweeney explains Nanite’s approach to geometric detail and the problem of visible changes as objects move.

Graphics

Research note: Nanite is a geometry system, not a promise of free rendering →

Sweeney describes Unreal Engine’s uses and recalls outside developers licensing its tools before the game shipped.

Graphics

Research note: Free access and royalty-free use are different offers →

Sweeney explains constructive solid geometry and recalls making additive and subtractive editing available to artists.

Graphics

Sweeney recalls a long coding session and describes the geometric edge cases he needed to handle.

Graphics

Sweeney explains light maps, precomputed shadows and practical compromises for dynamic lighting in early Unreal.

Graphics

Sweeney recalls deriving a fog approximation after seeing an image he thought had been rendered in real time.

Graphics

Sweeney praises Carmack’s willingness to rewrite code and describes successive generations of Unreal’s renderer.

Graphics

Sweeney contrasts advances in graphics with older networking and simulation systems he wants to redesign.

Graphics

Sweeney and Fridman examine how lighting and technical art produce detailed dirt and snow in a demonstration.

Graphics

Sweeney discusses shadow and reflection approximations and the specialist artistic work needed to build the scene.

Graphics

Sweeney explains layered snow materials and particle systems for fire and smoke in the demonstration.

Graphics

Sweeney discusses the difficulties of rendering human faces and capturing their range of motion.

Digital humans

Fridman and Sweeney discuss facial subtlety, skin lighting and why imperfect digital humans can feel wrong.

Digital humans

Sweeney distinguishes MetaHuman’s face-creation and performance-transfer tools and describes their remaining limitations.

Digital humans

Research note: MetaHuman transfers a performance onto a digital face →