6 ms·
>A game engine consists of three smaller engines: >Math Engine >Rendering Engine >Physics Engine Why do people keep repeating this? A game engine is a monstro
by DeathArrow 5y ago
>A game engine consists of three smaller engines:
>Math Engine
>Rendering Engine
>Physics Engine
Why do people keep repeating this? A game engine is a monstrous piece of software from which the renderer or the physics is just a tiny part.
Ogre is not a game engine. Unreal, Unity, CryEngine, Frosbite are game engines.
Even implementing a quality renderer is quite an undertaking. Knowing some OpenGL and some basic math is far from being enough. You have to know the graphic pipeline, the GPUs, the CPUs by heart. And be up to date with new techniques employed in graphics, where new things are being discovered daily. You have to read last papers published by Nvidia, AMD and Intel.
I saw many people dabbling with graphics that "built" game engines, when in reality they implemented some toy renderers.
I would be cautious about someone who hardly knows OpenGL teaching others about game engines.
It is like someone learns a few Javascript keywords and starts teaching others compilers.
- chuckSu 5y agoHater alert!
- deleted 5y ago[deleted]
- jedimastert 5y agoI think you're ignoring how small the definition of "game" truly is. For example, you need exactly none of the things you just described you make Flappy Birds. Hell, insisting that a game engine isn't a "real" engine unless it can render 3D graphics on a GPU ignores such a huge swatch of games it's hard to know where to even start.
- mysterydip 5y agoIt doesn't have to be monstrous. One of the first 3D FPS game engines is idtech1, from DOOM. It's less than 400KB zipped. I don't think anyone would argue that it's not a game engine, considered state of the art at one time and ported to every system under the sun. I agree with your points on a renderer is not an engine, though.
- DeathArrow 5y agoIf we are using 1993 standards, you are right. 400KB is enough. But I'm afraid the public is using 2021 standards. Even a texture is more than 400KB. Maybe you can fit a sound into 400KB.
- mysterydip 5y agoIon Fury was released in 2019 and used a variant of the Build engine, originally released in 1995. My point is a game engine doesn't have to be large.
- _448 5y ago>Math Engine >Rendering Engine >Physics Engine And the AI(algorithms) is also a considerable part of the engine? Or does each game develops everything related to the AI from scratch?
- Mikeb85 5y agoMost engines include basic AI, pathfinding is a type of AI, etc... For more complex AI most still code their own.
- deleted 5y ago[deleted]
- Danieru 5y agoIndeed, game engines are one of the prime destinations for game devs near the end of their career. Game engine companies are more relaxed and on average better paying than studio work since they are not tied to game releases and the related crunch. Yet there also exists a sea of inexperienced programmers jumping straight into "engine dev". They have none of the critical production experience which drives quality engines. This flood of enthusistic yet unprepared engineers causes a bipartite population. With the majority of public articles or YouTube presentations coming from those least prepared to speak with knowledge. If you want to become a game engine dev your first step should be joining a studio as a gameplay programmer. No one wants to use an engine written by someone who does not know how to make games.
- meheleventyone 5y ago> If you want to become a game engine dev your first step should be joining a studio as a gameplay programmer. No one wants to use an engine written by someone who does not know how to make games. Plenty of engine companies and studios will hire juniors and mid-level engineers into engine teams. And it’s been that way for a long time. And whilst the engine will preferably be made whilst developing actual games using it you don’t need everyone on the team to have been a gameplay programmer. There’s almost too much specialisation required these days and a lot of engine engineers aren’t interested in or good enough at game design to do gameplay roles. What it does need is active feedback from game teams building serious projects. I’d agree though if you want stability and much less chance of crunch pick a company with a stable income. Engine companies are good for this but there are plenty of others.
- Animats 5y agoThe next frontier is "metaverse engines". A metaverse engine client is partly like an MMO game engine, and partly like a web browser. You've got a flood of incoming events and content to deal with, no idea what it all means until it arrives, and have to present the illusion of a coherent world to the user while the data is coming in. A big difference from MMOs is that worlds with user-created content don't get all the pre-computation and optimization that happens in, say, Unreal Engine's level building tools. It's the 3D equivalent of rendering un-optimized web pages. A metaverse engine server (probably a whole farm of services) is somewhat like a MMO game server, except that it may have to deal with other similar servers. Possibly untrusted servers run by others, if you allow portals or teleporting or adjacent regions run by different grids. Hard problem. Improbable tried to build such a thing, as Spatial OS, but the end result was really expensive to run and all the games that used it went broke. Both Tim Sweeney and John Carmack see many unsolved problems in this area. If this "metaverse" stuff survives the hype and the scams and turns out to be important, there's plenty of hard work ahead in this area.
- hutzlibu 5y ago"Why do people keep repeating this? A game engine is a monstrous piece of software from which the renderer or the physics is just a tiny part." Maybe it is also worth noting, that there is a difference between a AAA monstrous game engine - and a simple one for casual browser games and the like? So there might be even value in an article from a beginner covering only the basics? (but I do agree, that the teaching was in a style overly confident not warranted)
- DominikD 5y agoAt the very least a bespoke engine will deal with state management, data loading and saving, audio, gameplay systems and probably AI. I'd even argue that these are more of a focus in indie games than rendering is.
- hutzlibu 5y agoI would argue it very much depends on the type of game you make. You do not always need a sophisticated assets loading mechanism nor AI modules. Or you need them in a different way, than what the engine provides (mostly my experience). My point is, "game engine" is not a static universal concept. Not every game needs a physic engine, for example, nor even assets(I think there are engines for text only rpgs) (A point where the article is indeed poor)
- xg15 5y agoOk, but by that logic, you can call a REPL a game engine if you only want to write text adventures. The term becomes a bit meaningless then. Many a better approach would be to ask whether every game needs a game engine?
- jayjader 5y agoSure, if you're making a text adventure in the command line, then the REPL is basically your default game engine. That's where your i/o, computation, control flow, asset management, etc is implemented/centralized. "Game engine" outside of the context of making a game is just a runtime (and/or environment), and I agree it becomes a bit meaningless (as a prescriptive thing). It's like saying a CPU needs to have vectorized operations, or even a hardware multiply, to be called a CPU. It's true that in many, if not most, cases those are essential components. However, I find it more useful to define "game engine" as "whatever takes care of the game, physics, and display logic implementation for a particular game". > Many a better approach would be to ask whether every game needs a game engine? So, by my definition every game _has_ a game engine. I think a more interesting question would be, "when does a game engine need to be considered as its own logical layer or compartment?"
- dmitriid 5y ago> Why do people keep repeating this? A game engine is a monstrous piece of software from which the renderer or the physics is just a tiny part Even playing sounds and music at the right time will likely trip most people up
- skohan 5y agoReally? The audio component I use for interactive projects fits in a single C file.
- throwaway17_17 5y agoI think your comment, coupled with parent’s, perfectly summarizes the problem most of this thread hints at. There is such a wide range of use cases in each particular facet of the engine and those use cases are going to be handled differently depending on time/expertise/budget/etc. For your purpose audio is handled well by a single file’s worth of C code, but there are games whose runtime audio components are almost a DAWs worth of processing and procedural sound generation and then coupled with an in game modifiable equalizer/quantizer/localizer/etc. Both your option and the more complex one are doing the job they need to do, but they are specified according to the ‘games’ need, not some overarching ‘here-is-what-a-game-engine-has-to-do-for-audio’ general advice about game engines. Articles about game engine design and the comments they elicit always seem to devolve into a very narrow perspective about individual implementations of some component for a specific target. Hell, I don’t even know if there is a way to broadly discuss the concept of a game engine without first talking about the species of engine your discussing, there is just too much space to be specific about things if you don’t narrow your discussion surface from the outset.
- pjmlp 5y agoIndeed, and the main reason why proprietary APIs are a non-issue on production engines, they are packed on the respective backend plugin and that is all.
- ensiferum 5y agoThat seems like an overly narrow stance on the subject. Not all games are AAA level and not all game engines need to be competing in the same category with UE4/5/CryEngine/Unity etc. trying to reach maximal "realism". Not all engines are 3D, not all engines need/want to have realistic physics models or state of the art graphics and rendering. Is Box2D not a "real" physics engine but a toy physics engine because it's not simulating physics in 3 dimensions? Games are games and there are a multitude of categories and multiple different dimensions how to judge any particular game or its engine. Saying that something is not a real game engine because it doesn't meet some random narrowly defined criteria is pointless.
- flohofwoe 5y ago> Ogre is not a game engine. Unreal, Unity, CryEngine, Frosbite are game engines. Including the editor tools and asset pipeline into the term "game engine" has only really become fashionable after Unity became so incredible popular, from that moment on, Unity and 'game engine' became synomymous and everybody else (including Unreal) copied the Unity workflow model. Most of the team works in the integrated editor tool in Unity most of the time, thus the editor tool has become synonymous with "engine" but it is actually the "factory line". But this integrated game development model isn't the only possible model just because it has become so popular. It's just as well possible to create a mainly "programmer driven" game engine where tools are only used to provide the asset data, but the actual game is fully built in code (IMHO it would be much less confusing if the term 'engine' would only be used for the runtime parts that actually 'drive' the game).
- Svoka 5y agoHonestly Unity is now mainstream, but I hate it. It is not the game engine, it is a game engine. One of many ways of doing thingи, and very from what I find ideal for my workflows.
- skohan 5y agoIn many ways game development seems decades behind other types of software development in terms of workflows. Virtually every other discipline in CS has moved towards loosely-coupled, composable components, but game development is still mostly happening against proprietary monoliths.
- DeathArrow 5y ago>game development is still mostly happening against proprietary monoliths. Running as a monolith is the most performant way and utilizes hardware to its fullest, which is what you want to do when you run games. Users don't have farms of Pcs and consoles, they don't need to scale.
- skohan 5y ago
- alfiedotwtf 5y agoWhat would be some good books to get started building these peices, assuming you already knew general programming, maths and physics?
- throwaway17_17 5y agoOne of more frequently recommended books is Jason Gregory’s ‘Game Engine Architecture’. Neither version I have is too deep in code specifics, but for standard AAA game development (Gregory was/is at Naughty Dog on their engine team) it is a pretty detailed look at the structure and options of game engines. For a more code centric resource I would say you could check out the YouTube videos by The Cherno (former EA engine dev).
- alfiedotwtf 5y agoCool, thanks for that!
- skohan 5y agoAt its core a game engine is a render loop and a game logic loop. If you're using a 3rd party renderer, your "engine code" might fit in a single source file if you're making a game like asteroids or tic tac toe for example. What you're talking about is a particular type of game engine: a tool with integrated editor, AAA 3D renderer, and which is general-puropose enough to support many different types of games built on top of it. That's a very very narrow way to define game engines, and imo it creates the wrong impression that games are this infinitely complex medium which it takes hundreds of people to work on at the most basic level. I think the author's definition is also too narrow, but it's perfectly valid to get into game engine development through small toy engines which are built from the ground up by one person.
- mattbee 5y agoSurely a game engine = code that supported writing & publishing a single game. Nothing more than that. If an indie author finishes a game on their own steam, without using a popular decades-old engine, I want to hear how they've focused their perspective to make it work. (this is the engine the author made: https://github.com/untoldengine/UntoldEngine https://github.com/untoldengine/UntoldEngine)