Book · 2018
Game Engine Architecture
by Jason Gregory
A former Naughty Dog engineer walks the full stack of a shipped 3D engine, memory allocator to renderer to gameplay systems, in one very long textbook.
What does Reddit think of Game Engine Architecture?
r/gamedev drives almost all of this one, and the endorsements get specific rather than generic. One recommendation calls out the chapter on platform-dependent layers by name, noting it goes into detail on how compilation and asset requirements differ across platforms, the exact kind of thing a tutorial site skips. Another comment credits Jason Gregory by name as the author and calls it a great book, dropped into a stack answer alongside C++ for engine core, C# for tooling, and shader languages for the GPU side, positioning it as the engine-core reference in that list rather than the scripting or tooling one. A third reader, mid-way through it, calls it awesome for its design hints and its overview of the field, still reading being its own kind of endorsement. It shows up again grouped with Game Programming Gems, in company with practical industry texts rather than academic computer-science ones.
Evidence, not a rating
Recommendation receipt
A compact, source-linked answer derived from the same Reddit sample and editorial synthesis as this page.
Editorial summary
r/gamedev drives almost all of this one, and the endorsements get specific rather than generic. One recommendation calls out the chapter on platform-dependent layers by name, noting it goes into detail on how compilation and asset requirements differ across platforms, the exact kind of thing a tutorial site skips.
Read if
Already comfortable with C++ and want the systems-level picture past a single tutorial? r/gamedev keeps reaching for this one specifically for the platform-dependent-layers material a generic OpenGL tutorial won't cover. Building your own stack and unsure where the engine-core layer fits next to C# tooling and shader work? One r/gamedev answer places this book exactly there. Want war stories over reference material?
Skip or borrow first if
Every displayed excerpt here recommends it in passing, inside a larger list or stack answer, so nothing in this sample argues with the book directly or flags a weak chapter.
Strongest published evidence
“Data structures, algorithms, linear algebra and vector operations, rotations, collision detection testing, game engine architecture, how caches work, memory manager types, spatial partitioning algorithms like quad/octree and BVH and BSP, for AAA studios everything above and C++ knowledge like forwar…”r/gamedev source · score 358 ↗
Dissent & strongest caveat
Every displayed excerpt here recommends it in passing, inside a larger list or stack answer, so nothing in this sample argues with the book directly or flags a weak chapter.
Community feedback & reader fit
Themes
- · Platform-dependent layers as a specifically praised chapter
- · Positioned as the engine-core reference, distinct from tooling or scripting books
- · Grouped with practical industry texts like Game Programming Gems
- · Attributed directly to author Jason Gregory rather than treated as anonymous canon
Common praise
- + One r/gamedev commenter singles out the platform-dependent-layers material specifically, saying it explains why compilation and asset requirements diverge across platforms.
- + A reader still partway through it calls it awesome for its design hints and its overview of engine-level systems.
- + A commenter names Jason Gregory as the author directly and calls it a great book while placing it as the engine-core layer in a broader recommended stack.
Common criticism
- − Every displayed excerpt here recommends it in passing, inside a larger list or stack answer, so nothing in this sample argues with the book directly or flags a weak chapter.
- − One prerequisite list files game engine architecture among a long set of AAA-studio expectations, which reads more like gatekeeping about hiring bars than a review of this book.
Who it's for
Already comfortable with C++ and want the systems-level picture past a single tutorial? r/gamedev keeps reaching for this one specifically for the platform-dependent-layers material a generic OpenGL tutorial won't cover. Building your own stack and unsure where the engine-core layer fits next to C# tooling and shader work? One r/gamedev answer places this book exactly there. Want war stories over reference material? This isn't that; the praise here is about design hints and platform detail, not narrative, and it shows up next to Game Programming Gems, not next to a memoir.
Mentions over time
Top subreddits
Which Reddit comments matter for Game Engine Architecture?
The most relevant excerpts across the subreddits where this book is mentioned — opinionated, argued takes first, then top-upvoted mentions. Click through to read the full thread.
“Data structures, algorithms, linear algebra and vector operations, rotations, collision detection testing, game engine architecture, how caches work, memory manager types, spatial partitioning algorithms like quad/octree and BVH and BSP, for AAA studios everything above and C++ knowledge like forwar…
“1. There's a fantastic book on game engine architecture that goes in to detail on platform dependent layers. TL;DR is that each platform has a different way to compile and has requirements for assets that are drastically different. 2. Compression only goes so far…
“If you want a thorough foundation in C++ I highly suggest you read a book on it rather than youtube videos. You can learn the basics through youtube but C++ is a bit more complicated than other languages and you would be better prepared if you took some time to read a book and follow along writing y…
“The way I specialized was to tell the engine lead that I wanted to help and he told me to start working on the 3D model exporter. Then, I kept at it for a couple decades.:p As for what I use: C++, Python, basic 3D math and linear algebra, an understanding of [CPU](
“I’m probably not a good example to follow, but here’s my story. I narrowly avoided success in my 20s. A couple of engineering contractors at my first job out of college had just started their own company and wanted to hire me as their first employee. But they ran into legal issues with poaching m…
“Gamedev here, in the 90% of the cases is: C/C++ for engine core functionality C# for the tools LUA or Python or Scheme or custom language for scripting HLSL or GLSL for GPU programming (shaders). Jason Gregory wrote a great book about game engine architecture:
“learnopengl & opengl-tutorial websites - opengl tutorials Game Engine Architecture book (still reading) - awesome book with lots of design hints, overview of…
“"game engine architecture" will give you a very solid foundation for understanding engine design and implementation.
“There is a sub Reddit for this. r/gameenginedevs. As for how to get started, Game Engine Architecture by Jason Gregory is a fantastic book. Jason is someone who worked on Naughty Dog's engine throughout the early uncharted games and The Last of Us. So he is quite knowledgeable. Also check out TheChe…
“My goto book when it comes to game engine creation is Game Engine Architecture by Jason Gregory. It's a huge book that details all the parts of a game engine (memory management, rendering, audio,...). As mentionned by others, on YouTube, the channel TheCherno is pretty good. Nowadays, lots of gam…
“i heard "Game Engine Architecture" by jason gregory is good but i did not read it myself yet.
“For programmers I recommend "Game Programming Patterns" and "Game Engine Architecture".
“there’s a great book called game engine architecture
“If you're just interested in game dev -- and actually making something. I wouldn't start with an engine. They're so complex. You'll learn a lot but you really need a starting point. The **"Game Engine Architecture"** by Jason Gregory and the **"Foundations of Game Engine Development"** books are g…
“Jason Gregory's book about game engine architecture It may help
Convinced? Pick up Game Engine Architecture
What else does r/gamedev read?
Other books mentioned in the same sub, ranked. Shared-sub overlap with this title breaks ties.
Game Engine Architecture — frequently asked
Who wrote Game Engine Architecture and is it worth reading per Reddit?+
Jason Gregory wrote it, and a r/gamedev commenter names him directly while calling it a great book, recommending it as the engine-core reference alongside C++ for core systems, C# for tooling, and shader languages for GPU work. A separate reader still partway through calls it awesome for its design hints and overview.
What does Game Engine Architecture cover that a tutorial site doesn't?+
Per one specific r/gamedev recommendation, its chapter on platform-dependent layers goes into detail on how compilation differs by platform and how asset requirements diverge accordingly, exactly the kind of cross-platform detail that free tutorial sites like learnopengl tend to skip entirely in favor of a single target setup.
Is Game Engine Architecture aimed at beginners or working engine developers?+
The displayed context leans toward developers already past the basics. It gets positioned as the engine-core reference in a stack that assumes C++ fluency, sitting alongside Game Programming Gems in one r/gamedev list rather than beginner C++ guides, and gets flagged for platform-specific detail a newcomer likely wouldn't need yet.