Game Engine Gems 2 & 3

Source metadata

• Type: Combined anthology summary
• Editor: Eric Lengyel
• Years: 2011 (Game Engine Gems 2), 2016 (Game Engine Gems 3)
• Publisher: A K Peters / CRC Press
• Scope: Broad engine-programming collections spanning rendering, engine design, networking, physics, general C++ programming, and selected AI/character-control topics

Key takeaways

• The most reusable conceptual chapter for this vault is Noel Llopis’ data-oriented design chapter: memory layout, contiguous processing, and performance-conscious architecture.
• The anthologies also contain strong production-facing engine topics: game tuning infrastructure, placeholder assets in pipelines, and rendering/workflow architecture.
• Game Engine Gems 3 is especially valuable for modern C++ utility material: fast delegates, compile-time string hashing, static reflection with tuples, and ISPC integration patterns.
• The AI/character-control material is narrower than the dedicated AI anthologies but still useful: vision-based local collision avoidance, autonomous NPC frameworks, and behaviour-oriented programming for NPCs in large open worlds.
• These books are best treated as engine craft references rather than as one coherent theory text. Their value lies in selected chapters that illuminate implementation patterns.

Notable claims

• Data layout and iteration strategy are performance features in their own right, not just micro-optimisation details.
• Engine tooling such as live tuning and placeholders is part of production quality, not merely editor convenience.
• Useful C++ engine techniques often sit at the boundary between language knowledge and engine-architecture knowledge.

Relevance

Most directly informs:

• data-oriented-design — Llopis’ chapter is the clearest current grounding
• cpp-templates and cpp-classes-and-oop — compile-time techniques and reflection-adjacent C++ patterns
• 3d-production-pipeline — texture atlasing and convex decomposition as downstream pipeline concerns
• steering-behaviours and npc-perception-systems — selected AI/character-control chapters

Potential future extraction:

• tuning infrastructure
• texture atlasing
• compile-time hashing
• static reflection in C++
• open-world behaviour objects

Open questions raised

• Which of these engine-programming topics should become standalone pages versus remaining pointers from a combined source summary?
• Should texture atlasing live under game art, tools, or programming in this vault?
• How far should the vault go into low-level C++ engine craft before it stops being useful for the main student audience?

Links

data-oriented-design · cpp-templates · cpp-classes-and-oop · 3d-production-pipeline · steering-behaviours · npc-perception-systems