Tim Sweeney on Unreal Engine, Fortnite and Gaming

Sweeney recalls learning BASIC on his brother’s IBM PC, then making games, databases, a compiler and bulletin board software. He describes the first game he wrote and the many hours he spent programming before releasing a commercial product.

Sweeney says projects and experimentation built skills he later used for Unreal Engine. He connects engineering mathematics to 3D programming and advises aspiring programmers and artists to keep learning and making work.

Sweeney distinguishes learning from collecting grades or credentials and describes the value of having time to explore. He recalls the freedom of childhood, building things with neighbors and pursuing projects.

Sweeney describes playing *Adventure* and the text adventure *Zork*, and how games inspired him to program movement, editors and game systems. He says he studied later games such as *Wolfenstein* and *Doom* to understand their techniques.

Sweeney explains how he turned a text editor into a game and built ZZT’s levels and objects. After testing it with neighbors, he distributed it through bulletin boards and sold sequels by mail. He reflects on the reach of software distributed digitally.

The discussion turns to ZZT’s editor and scripting language, which let players create their own boards. Sweeney says Epic’s approach has been to make entertainment and tools, and describes sharing services and technology with developers.

Sweeney describes dial-up bulletin boards, their small communities and slow modems, then the public opening of the internet. He recounts the shift from shareware to boxed games and later to convenient digital distribution, including Steam.

Sweeney recommends making distinctive games, reducing the friction of trying them and serving an audience rather than confronting established publishers head-on. He describes ZZT’s editor as part of its appeal and argues that success can come from building and improving over multiple steps.

Sweeney recalls neighbors enjoying the game and letters from players, which made the work feel connected to an audience. He says the business required little capital at first and that incoming orders persuaded him to commit to it.

Sweeney recounts Epic’s early shareware team and its response to *Wolfenstein 3D* and *Doom*. He describes how real-time 3D made players feel present in a game world and changed Epic’s view of what games could become.

After initially feeling unable to match *Doom*, Sweeney and other Epic developers began experimenting with 3D graphics. He describes assembling a team for *Unreal*, the extended development and financial strain, and techniques including dynamic lights and volumetric fog.

Sweeney describes the collaboration of artists, programmers and designers, and the daily cycle of building, testing and improving the game. He recounts his late working hours and the division between his technical role and Mark Rein’s business responsibilities.

Sweeney traces the project’s move from Pascal to C and then C++, alongside its transition from 16-bit to 32-bit systems. He explains why C++ helped simplify the code and remained suited to performance-focused work.

Sweeney recalls upgrading his workstation and optimizing software rendering for the hardware of the time. He contrasts hands-on CPU optimization with modern performance work and explains how Nanite was engineered to render detailed geometry efficiently on GPUs.

Sweeney explains the challenge of rendering scenes containing vast amounts of geometry, and how detail needs to vary with the image and the viewer’s distance. He discusses pixel-scale rendering and avoiding visible changes in detail as objects move.

Sweeney describes Unreal Engine as a toolkit for real-time 3D applications, used in games and other industries. He explains how requests to license the technology provided revenue during Unreal’s development and helped establish Epic’s dual focus on developers and players.

Sweeney explains how Unreal’s editor let artists add and subtract geometry to build shapes, describing the long coding session behind the feature. He discusses binary space partitioning, polygon cases and why the final portion of a correct implementation can be especially difficult.

Sweeney explains why real-time graphics use approximations of physical light, including light maps, colored lighting and shadows. He describes exposing lighting features to artists and how they combined them in ways the engineers had not anticipated.

Sweeney recounts seeing a foggy GPU demonstration and working out how to implement volumetric fog in Unreal. He describes using an integral to model accumulated light through fog, then finding that the demonstration that inspired him had been rendered rather than calculated in real time.

Sweeney praises Carmack’s willingness to discard and rewrite code in pursuit of better results. They discuss continued challenges in real-time rendering and the long development of Unreal Engine.

Sweeney reviews major changes in the engine, from software rendering and early GPUs to programmable shaders, Unreal Engine 3 and 4, and UE5’s Nanite and Lumen. He also identifies older networking and single-threaded simulation systems as limitations for future work.

Using a scene from a presentation about *Marvel 1943*, Sweeney discusses how lighting, material layers, reflections and shadows combine to render snow and dirt in real time. He also explains the particle systems, lighting and artistry behind a smoke demonstration.

Sweeney explains why people notice errors in faces and outlines MetaHuman’s capture, face-building and animation tools. The discussion covers facial movement, skin and hair rendering, and the difficulty of making expressions convincing.

Sweeney describes Lumen as a system for approximating how light bounces across a scene at different scales. They discuss indirect lighting, reflections and the subtle lighting cues that affect how a scene appears.

The conversation turns to real-time 3D graphics beyond games. Sweeney describes LED walls used in film production and how they can provide actors with scene lighting and a view of the environment they are meant to inhabit.

Sweeney says AI-generated video has consistency and scene-understanding challenges, but sees AI as a potential aid to human creators. They discuss using scanned assets and connecting AI systems to structured scene graphs so content can be directed more precisely.

Sweeney compares current anxieties about AI with earlier concerns about digital tools, and says AI could become part of an artist’s toolkit. He discusses job changes, coding assistants, their limits on difficult tasks and the value of reusable software modules.

Sweeney considers how close graphics might come to reality and says human appearance, dialogue and intent remain harder to simulate than environments. They discuss how generative text systems could contribute to increasingly convincing human simulations.

Sweeney discusses whether reality might be a simulation and what could count as a base reality. The conversation considers mathematical laws, consciousness, quantum mechanics and questions that neither speaker presents as resolved.

Sweeney says Epic aims to make fun games rather than replace reality, while acknowledging that increasingly realistic simulations raise difficult questions. The speakers consider limits on immersive worlds and on creating simulated people who could suffer.

Sweeney defines the metaverse in terms of social multiplayer experiences where people meet and play together. He describes Fortnite’s cross-platform play and creator tools as part of that direction, while noting that the field remains at an early stage.

Sweeney recounts how a company game-making exercise produced the initial idea for Fortnite: building forts by day and defending them from zombies at night. He describes its changing art style and modes, then how a small team built Battle Royale in four weeks.

Sweeney describes the online systems Epic had built before Battle Royale and the work needed to scale them. He explains how microservices and cloud hosting supported large numbers of concurrent players.

Sweeney discusses Fortnite’s importance to Epic’s business, the company’s spending and layoffs, and its investment in real-time 3D technology. He describes Epic’s willingness to fund projects years before they produce revenue.

Sweeney describes the separation between game accounts, friends and items, and argues for connecting social systems and some cosmetic economies across games. He explains how Fortnite links player engagement to creator revenue sharing.

The discussion considers standards for portable game items and how shared economies might work. Sweeney distinguishes the metaverse from VR or cryptocurrency and says interoperability could be built through standards and other existing technologies.

Sweeney discusses existing formats for exchanging 2D and 3D data, then identifies programming as a missing foundation for a world built by many creators. He describes the prospect of large, connected environments maintained by different people.

Sweeney introduces Verse as a language intended for large simulations and code that can be combined across creators’ work. He discusses the possibility of many players sharing a scene and the technical challenges of making that possible.

Sweeney explains the design principle of achieving power through features that work together, and describes how Verse expressions can succeed, fail or produce multiple values. He compares this approach with familiar conditionals, loops and queries.

Sweeney discusses backwards compatibility and how type systems can express properties a program must satisfy. He explains formal proofs and their potential role in catching errors at compile time, including in code generated with AI.

Sweeney describes the difficulty of writing concurrent programs and the limits of Unreal’s single-threaded gameplay simulation. He explains how transactional memory could allow ordinary gameplay code to run concurrently while checking for conflicts.

Sweeney says Verse is being introduced gradually through Unreal Editor for Fortnite, with features added and tested with creators. He describes Unreal Engine 6 as the point where different development paths are intended to come together, without giving an exact release date.

The speakers discuss solo development and visual scripting. Sweeney says productive tools, reusable assets and content marketplaces can help small teams focus on their distinctive work and finish games.

Sweeney argues that developers and users should be able to distribute and install software without a platform owner’s permission. He criticizes app-store fees and restrictions, and says they can affect prices and the kinds of games that succeed.

Sweeney explains why Epic challenged Apple and discusses Apple’s control over app distribution, payments and web capabilities. He says Epic’s position allowed it to risk losing iOS access, and argues for greater competition and platform openness.

Sweeney discusses the Epic Games Store’s 12% revenue share, acknowledges complaints about its interface and explains that Epic does not aim to copy every Steam feature. He describes Epic Online Services as a way to support cross-platform friends and play.

The speakers discuss platform silos and cross-platform play. Sweeney recounts Epic’s dispute with Sony over cross-play and says the companies later worked together on games, technology and other partnerships.

Sweeney distinguishes voluntary exclusive deals from platform restrictions and explains Epic’s use of exclusives to attract games to its store. They discuss the drawbacks of exclusivity, the store’s competition with Steam, and Sweeney’s claims about app-store operating costs.

Sweeney argues that games need to deliver fun and says playing with real-world friends is an increasingly important part of gaming. He contrasts large multiplayer games with smaller and single-player releases and discusses how investment and audiences are shifting.

Sweeney says he values games that feel like living worlds and mentions *The Legend of Zelda: Breath of the Wild*, *Skyrim* and *Red Dead Redemption*. He reflects on the care and design choices that give games distinct qualities and shape player interactions.

Discussing *Grand Theft Auto*, Sweeney explains that raising quality can reveal further problems and make schedules hard to predict. He describes the pressure of finishing Fortnite updates and learning from live releases.

Sweeney contrasts hostile online exchanges with the connections he has experienced while playing with strangers. He says shared activity can encourage empathy and social bonds, before the conversation closes.

Lex Fridman thanks listeners, shares a line attributed to Benjamin Franklin and signs off.