Game Development: Contested Questions, Currency, Canon, and Quick Reference¶
Part 5 of 5 of the Video Game Development reference (plugin
video-game-development), covering §16–§20. Sibling skills:game-engines-loop-and-architecture(§0–§3),game-rendering-physics-animation-and-audio(§4–§7),game-ai-networking-and-tools(§8–§10),game-performance-feel-and-shipping(§11–§15). Section numbers are shared across the set; a reference written as §N →skillpoints into that sibling skill.Currency: Verified August 2026. See §17 below for the currency snapshot and what goes stale first.
How to read this. Reference, not tutorial. Sections are independent. Three markers: - [DURABLE] — real-time systems reality, human perception, or a lesson the industry has relearned every console generation. Does not expire. - [VERSIONED] — specific to an engine version, API, platform, or market condition. Verify before relying on it. - [CONTESTED] — practitioners genuinely disagree, usually because the right answer depends on team size and genre.
⚠️ GOTCHA boxes mark the mistakes that ship broken games, blow the frame budget, or destroy a studio's schedule.
The three framings that organize everything below: 1. A game is a soft-real-time simulation with a hard deadline, 60 times a second. 16.67 ms at 60 fps, 8.33 ms at 120. Everything — rendering, physics, AI, audio, networking, streaming, GC — shares that budget. Consistency beats peak framerate; a stable 30 feels better than a 60 that stutters. 2. Games are content pipelines with a game attached. On any team above about five people, the tools, build system, and iteration loop determine your output more than your engine code does. Ten-minute iteration times will cost you the game. 3. Scope is the thing that kills projects, not technology. The overwhelming majority of unfinished games died of ambition, not of a hard technical problem. §14 →
game-performance-feel-and-shippingis the section most people need and skip.
§16. Contested Questions¶
16.1 ECS vs. object-oriented. §3.2 → game-engines-loop-and-architecture. The strongest version of each case, and the hybrid
synthesis most shipped games actually use.
16.2 Unity vs. Unreal vs. Godot. §1 → game-engines-loop-and-architecture. Genuinely depends on genre, platform, team
experience, and licence-risk tolerance. The 2026 rough consensus: Unreal for
high-fidelity 3D, Unity for mobile and cross-platform breadth, Godot for 2D and
licence-sensitive teams — but every one of those has strong counterexamples.
16.3 Are the explicit graphics APIs still right? §4.2 → game-rendering-physics-animation-and-audio — Aaltonen's argument that DX12
and Vulkan are ten-year-old designs targeting thirteen-year-old hardware, and that a new
abstraction layer has quietly grown back underneath.
16.4 Root motion vs. in-place animation. §6 → game-rendering-physics-animation-and-audio.
16.5 Custom engine vs. commercial. For custom: total control, no royalties, no licence risk, and a genuine competitive advantage if your game needs something engines don't do. Against: years of work on solved problems, no asset ecosystem, harder hiring, and you now maintain a renderer forever. ~14% of developers report using an in-house engine, and most of those are at studios with the scale to justify it.
16.6 Generative AI in game development. §15.2 → game-performance-feel-and-shipping. The industry is split against itself —
36% use it, 52% think it's harming the industry. The disagreement is genuine and runs along
discipline lines, and the legal position on generated-asset ownership is unsettled.
16.7 How much accessibility, and who pays for it. There is no serious argument against accessibility; the disagreement is about cost and priority on small teams. [DURABLE] The high-value, low-cost items are well-established: remappable controls, subtitle size and background options, colourblind-safe palettes (never colour alone as a signal), a screen shake toggle, difficulty options, hold-vs-toggle for held inputs, and reduced-motion settings. The Game Accessibility Guidelines and the Xbox Accessibility Guidelines are the practical references, and both are organized by implementation cost. Late retrofitting is what's actually expensive.
§17. Currency Snapshot — verified August 2026¶
| Thing | Status as of Aug 2026 | Decay risk |
|---|---|---|
| Unreal Engine | 5.7 current; free to $1M lifetime gross, then 5%. 5.7 added tooling aimed at small teams. Unreal Engine 6 announced at State of Unreal 2026, early access window reported as 2027 | Medium |
| Unity | 6.x line (6.3 LTS with day-one Switch 2 support; 6.4 shipped March 2026). Seat-based: Personal free under $200K/yr, Pro ~$2,040–2,310/yr, Enterprise above $25M. ⚠️ Runtime fee cancelled September 2024; prices have since risen again. Unity 7 beta expected December 2026 | Medium |
| Godot | 4.7 (June 2026 — HDR, area lights, drawable textures). 4.6 (26 Jan 2026) made Jolt the default physics engine and added Android device mirroring, Google Play Billing/Games Services, and Apple StoreKit 2. MIT, no royalties, no revenue threshold, nonprofit foundation | Low |
| Engine market share | Unreal out-earned Unity on Steam for the first time since 2018 (31% vs 26% of 2024 revenue, Video Game Insights); Unity still ships the most games (51% of 2024 Steam releases); Unreal leads mindshare 42% vs 30% (GDC 2026); Godot Steam releases 618 → 2,864 in two years (~4.6×); Unity ~70% of top-grossing mobile | Medium |
| Industry conditions | ⚠️ 28% of GDC 2026 respondents laid off in two years (33% in the US); two-thirds of AAA respondents' companies had layoffs; 48% of laid-off respondents still unemployed; 74% of students concerned about prospects. Ongoing memory-supply constraints affecting hardware | High |
| Generative AI | 36% use AI tools; 52% believe it's harming the industry (up from 30%) vs 7% positive; opposition highest among artists (64%), designers (63%), programmers (59%). Steam requires AI disclosure; Apple and Google Play require AI labels. ⚠️ Steam clarified in January 2026 that internal workflow tools are exempt — disclosure covers shipped content. Thousands of Steam titles now disclose, concentrated among small teams | High |
| Vulkan | Current spec 1.4. Vulkan Roadmap 2026 requires Vulkan 1.4, targeting mid-to-high-end hardware shipping in 2026 or shortly after, adding baseline requirements including hostImageCopy and robustness features |
Medium |
| Direct3D 12 | DX12 Ultimate feature set: DXR, VRS, mesh shaders, sampler feedback. DirectStorage for fast asset loading. Work graphs shipping | Medium |
| Work graphs | In D3D12; in Vulkan via VK_AMDX_shader_enqueue (experimental) with mesh nodes and HLSL syntax support via DXC→SPIR-V. ⚠️ Not yet standardized across hardware vendors |
High |
| Steam Deck | Fourth-most-developed-for platform (28% of GDC 2026 respondents) — newly added to the survey and immediately significant | Medium |
Goes stale fastest: industry employment conditions; AI adoption, sentiment, and
disclosure rules; engine version numbers and pricing; work-graph standardization.
Essentially never stale: §2 → game-engines-loop-and-architecture (game loop), §3.1 → game-engines-loop-and-architecture (composition), §5.1 → game-rendering-physics-animation-and-audio (kinematic
controllers), §8.3 → game-ai-networking-and-tools (AI legibility), §9.2 → game-ai-networking-and-tools (netcode fundamentals), §11 → game-performance-feel-and-shipping (performance
principles), §12 → game-performance-feel-and-shipping (game feel), §14 → game-performance-feel-and-shipping (scope).
§18. The Canon¶
18.1 Books¶
| Author | Work | Why |
|---|---|---|
| Robert Nystrom | Game Programming Patterns (free at gameprogrammingpatterns.com) | Start here. The best-written book on game code architecture, and free |
| Jason Gregory | Game Engine Architecture | The comprehensive reference for how engines are actually built. Naughty Dog lead |
| Steve Swink | Game Feel | The canonical treatment of §12 → game-performance-feel-and-shipping |
| Jesse Schell | The Art of Game Design: A Book of Lenses | The best design book; 100+ perspectives on your game |
| Tynan Sylvester | Designing Games | Systems-first design, by RimWorld's creator |
| Raph Koster | A Theory of Fun for Game Design | Short, deep, about why games work at all |
| Richard Fabian | Data-Oriented Design (free online) | The theory beneath ECS and §11.3 → game-performance-feel-and-shipping |
| Christer Ericson | Real-Time Collision Detection | The reference for §5 → game-rendering-physics-animation-and-audio |
| Akenine-Möller, Haines, Hoffman | Real-Time Rendering (4th ed.) | The graphics bible |
| Matt Pharr et al. | Physically Based Rendering (free online) | Offline-focused, but the theory underpins everything |
| Ian Millington | AI for Games; Game Physics Engine Development | Comprehensive references for §8 → game-ai-networking-and-tools and §5 → game-rendering-physics-animation-and-audio |
| Mat Buckland | Programming Game AI by Example | The friendliest AI introduction |
| Fletcher Dunn & Ian Parberry | 3D Math Primer for Graphics and Game Development | The math you actually need |
| Rémi Arnaud et al. / various | Game Engine Gems, GPU Gems, GPU Zen, Game AI Pro | Practitioner article collections; Game AI Pro is free online |
| Jason Schreier | Blood, Sweat, and Pixels; Press Reset | Production reality, and the best answer to "why is §14 → game-performance-feel-and-shipping like that" |
| Amy Hennig / various | — | For narrative, see the GDC vault rather than a single book |
18.2 Talks, sites, people¶
The GDC Vault is the field's real library — much of it free. "The Art of
Screenshake" (Jan Willem Nijman, Vlambeer) is the best 30 minutes on game feel ever
recorded. Glenn Fiedler's Gaffer On Games — "Fix Your Timestep!" and the networked
physics series — is the canonical networking and simulation reference. Casey Muratori
(Handmade Hero — an entire game engine built from scratch on video), Mike Acton
(data-oriented design; his CppCon talk is the definitive statement), Sebastian Aaltonen
(modern GPU rendering, §4.2 → game-rendering-physics-animation-and-audio), Fabian Giesen (ryg), Inigo Quilez (iquilezles.org
— shaders and SDFs), Freya Holmér (math and curves, exceptionally well taught),
Catlike Coding (Unity tutorials of unusual depth), The Book of Shaders, Shadertoy,
LearnOpenGL and vulkan-tutorial.com, and Red Blob Games (Amit Patel —
the reference for A*, hex grids, and pathfinding, and the best interactive
explanations on the internet).
Communities: r/gamedev, the Godot/Unity/Unreal forums and Discords, Handmade
Network, and GDC itself (now the GDC Festival of Gaming).
Accessibility: gameaccessibilityguidelines.com and the Xbox Accessibility Guidelines, both organized by implementation cost.
§19. Quick Reference¶
19.1 Numbers¶
- 60 fps = 16.67 ms; 120 fps = 8.33 ms; 30 fps = 33.3 ms.
- Motion-to-photon: <30 ms crisp, 50–100 ms typical, >150 ms broken.
- Entity interpolation delay: ~100 ms behind server time.
- Rollback re-simulation budget: 7–10 frames within one frame.
- Localization text expansion: German ≈ +30% over English.
- Console cert: budget weeks; expect a rejection.
- Scope rule: estimate honestly, then cut half.
- The last 10% of the game is 50% of the work.
19.2 Project start checklist¶
- [ ] Engine chosen for platform, genre, team experience, and licence risk — terms read and archived
- [ ] Fixed timestep with accumulator and a max-step clamp, from day one
- [ ] Determinism decided (needed for rollback, replays, lockstep, regression tests)
- [ ] Multiplayer architecture decided now, if there will ever be multiplayer
- [ ] Version control appropriate to your asset sizes (Perforce vs. Git LFS)
- [ ] CI building every target platform per commit
- [ ] Iteration loop measured in seconds, not minutes
- [ ] In-game debug console and state visualizers scaffolded early
- [ ] Console cert requirements read (suspend/resume and save integrity especially)
- [ ] Accessibility baseline planned: remapping, subtitles, colourblind-safe, screen-shake toggle
- [ ] Platform AI-disclosure obligations understood if using generative tools
- [ ] Steam page up early; wishlists accumulating
- [ ] Vertical slice scoped as the first milestone
19.3 "It runs badly" triage¶
| Symptom | First look |
|---|---|
| Low average framerate | Profile CPU vs GPU first — you're optimizing the wrong one otherwise |
| Periodic hitches | Allocation/GC, shader compilation, asset streaming, or level loading |
| Stutter only on first play of an area | Shader/PSO compilation (§4.3 → game-rendering-physics-animation-and-audio) |
| Fine on your machine, bad for players | You profiled on the wrong hardware |
| GPU-bound | Overdraw, resolution, shader complexity, bandwidth |
| CPU-bound on the render thread | Draw calls and submission — batch and instance |
| CPU-bound in gameplay | Cache misses, per-frame allocation, O(n²) queries, unbudgeted pathfinding |
| Physics spikes | Too many active bodies, CCD everywhere, timestep too small |
| Memory growth over a session | Leak, or pool that never returns — soak test |
§20. Sources and Method¶
Method. Narrative (not systematic) review. The durable material — §2 → game-engines-loop-and-architecture (game loop),
§3 → game-engines-loop-and-architecture (architecture), §5–§9 → game-rendering-physics-animation-and-audio, game-ai-networking-and-tools fundamentals, §10 → game-ai-networking-and-tools (tooling), §11 → game-performance-feel-and-shipping (performance principles),
§12 → game-performance-feel-and-shipping (game feel), §13.2 → game-performance-feel-and-shipping–13.3, §14 → game-performance-feel-and-shipping (production) — is synthesized from the standard
references in §18, GDC practitioner talks, and consistently-reported industry practice.
Every time-sensitive claim (engine versions and pricing, market share, industry
conditions, AI adoption and disclosure rules, graphics API status) was verified against a
primary or near-primary source in August 2026 and is flagged in §17 with a decay-risk
rating. Where practitioners genuinely disagree, §16 presents both cases.
Search log (August 2026): Unreal/Unity/Godot versions, licensing, and 2026 market share · Steam AI disclosure policy and GDC State of the Game Industry 2026 · Vulkan 1.4, DirectX 12, work graphs and mesh shaders.
Primary and near-primary sources consulted (selected):
- GDC / GDC Festival of Gaming — 2026 State of the Game Industry report and its
official summary (layoffs, AI adoption and sentiment, engine mindshare, Steam Deck),
via gdconf.com, BusinessWire, and secondary coverage
- Video Game Insights, The Big Game Engines Report — Steam revenue and release share
- Godot Engine growth statistics and release notes (4.6, 4.7); SteamDB-derived counts
- Khronos Vulkan specification and Vulkan Roadmap 2026 requirements;
AMD GPUOpen on work graphs and VK_AMDX_shader_enqueue mesh nodes
- Sebastian Aaltonen, "No Graphics API" — the explicit-API critique in §4.2 → game-rendering-physics-animation-and-audio
- Legal and licensing analysis of the Unity TOS timeline (the 2019 SpatialOS change, the
April 2023 removal of the protective clause, the September 2023 runtime fee, the 2024
cancellation), plus 2026 pricing comparisons from multiple independent write-ups
- Reporting on Steam's January 2026 AI-disclosure clarification (GamesIndustry.biz and
GameMeca, as cited by secondary coverage) and on disclosure volumes
Confidence statement. High confidence in §2–§14 → game-engines-loop-and-architecture, game-performance-feel-and-shipping's durable technical and production
content — this rests on the standard references, decades of consistent practitioner
reporting, and material that has been stable across console generations. High
confidence in the GDC 2026 survey figures (§15.1 → game-performance-feel-and-shipping–15.2, §17), which come from a named,
methodologically-described annual survey of 2,300+ professionals and were corroborated
across multiple independent reports of the same release. Moderate confidence in the
engine market-share numbers: they come from commercial research (Video Game Insights) and
platform-derived counts, they measure different things (Steam revenue vs. Steam releases
vs. self-reported mindshare vs. mobile grossing), and the mobile figures in particular
circulate widely without a consistently-attributable primary source — I have presented the
framing rather than a single number. Moderate confidence in the engine version and
pricing details in §17: several 2026 sources disagree on which Unity and Unreal versions
are current at any given moment (one cited UE 5.6 as current, others 5.7) and on exact
Unity price points, which is a normal consequence of rapid release cadences and regional
pricing — verify current pricing on the vendor's own page before making a financial
decision. The Unreal Engine 6 timeline is an announcement, not a shipped product.