7 ms·
I wish the term "game engine" would be better defined. Somehow this now means "the whole package", an integrated product like Unity, UE or Godot which includes
by flohofwoe 4y ago
I wish the term "game engine" would be better defined. Somehow this now means "the whole package", an integrated product like Unity, UE or Godot which includes all tooling required to create and publish games. This isn't an engine, it's a whole "Gamedev IDE", in spirit much closer to Photoshop than ImageMagick. Or as car analogy: nobody calls a whole car an "engine", even though every car has one.
The original meaning of "game engine" which made much more sense was: "the actual code which enables the game to run", e.g. just the runtime parts, the tiny piece of code that's dangling off the end of the asset pipeline ("tiny" relative to the work that needs to go into authoring tools and asset pipeline).
> Let's begin with something controversial: a stack made for a single game is not a game engine.
...controversial indeed :D
- ratww 4y agoIMO this coupling happens mostly on purpose. It's just vertical integration, Apple style. It seems to be in the interest of "engine" makers to make people think that a smaller engine without an editor can't succeed, and that there's no possibility of having a standalone editor. They want control of the whole stack. Game development in general has been plagued by those things. Everything uses proprietary formats, little interoperability, lots of custom stuff. All the parts that aren't proprietary came from the outside (eg: audio/video/image formats) or was leaked by generous developers (Quake MD? and BSP formats being used in newer games/libraries). I would personally love to see more people working on editors that can be used by multiple engines, so that we can see more focused engines grow too, without having to create a whole editor ecosystem. And also editors would grow themselves, and editor-makers would make one without having to make a full engine. I really think it's possible. > ...controversial indeed :D I think the article writer is flat out wrong on this one. The Doom and Quake engines are definitely... well, engines, even though they were only reused later. Sure you can have a more spaghetti "game without engine", but I'd draw the line whether it's reusable/logically separated or not.
- flohofwoe 4y ago100% agree. A popular "bring your own engine" editor would be awesome and would make a lot of sense (just not a lot of 'business sense'). The Unity editor is actually quite hackable and can be used like that, but that's very likely a 'licensing grey area'.
- ratww 4y agoI think the open source community can definitely do something cool like this. Although good UX has been historically the Achilles Heel of open source, I believe the focus would help a lot in this regard. No need to worry about the engine part itself. Godot's editor for example is already quite good, and it's only a portion of the engine. Imagine what a team with more focus could achieve. It would also help tremendously in standardising file formats and other conventions. We've kinda settled on either ECS or Node-Based architectures, so there's an obvious starting point, concept-wise. Just have each engine provide a configuration file telling which components (or node types) are available, and how they can be configured. Or provide a language-server-like API so it's extensible. There's no need to worry about high-fidelity, physics, sounds, or scripting during the editing (only during debugging), so some editor that just knows the 3D formats is enough. If debugging is needed there should be an optional way, like with code editors. I've been looking for a big project to tackle, maybe that's something I can try to start myself :)
- bob1029 4y ago> I've been looking for a big project to tackle, maybe that's something I can try to start myself :) I had a similar thought. I was thinking maybe this could even be some web-based system where you could have multiple editors talking to the same engine session, or vice versa. > Although good UX has been historically the Achilles Heel of open source Completely agree. Perhaps the best way to go about a project like this would be to establish a few mock use cases up front (i.e. actually try to build a dummy game with your own tools). The magic of UX doesn't appear until you have actually used a thing and start tweaking stuff like animation delays, font sizes, tab order, modal positions, et. al.
- 4y ago
- Jare 4y ago> It seems to be in the interest of "engine" makers to make people think that a smaller engine without an editor can't succeed Phaser for a long time was a runtime engine without an editor, and many people missed that type of capability. Same with Cocos2D. > and that there's no possibility of having a standalone editor. Tiled (for 2d maps) or Spine (for 2d animations) are 2 examples of well known standalone editors. There's no chance to "make people think" that such things can't exist. > It seems to be in the interest of "engine" makers to make people think There's no hidden agenda going on, it's that integrated tools are often much more effective when building things out of multiple different pieces. Wouldn't it be cool to place animated objects in Tiled and see their animation states to properly gauge how they interact with the rest of the scenery in different states? Or use Spine to animate a tilemap going through an earthquake? Custom file formats exist because features differ, and even for similar features, the semantics differ.
- vvanders 4y agoYep, it's been a while since I've been in the industry but with med-large teams your the composition of staff is such that Art/TechArt/Design are where the majority of the time/effort is going to be spent. Last team I was on of ~60, we had 9-10 devs, if I could build tools that made our design or art team more effective that was a better use of my time(within reason of course). Integrated engines just reflect that composition.
- ratww 4y ago> Tiled (for 2d maps) or Spine (for 2d animations) are 2 examples of well known standalone editors. Those are a 2D map editor and a 2D animation editor. Apples and Oranges compared to what the editors in Unity/Unreal/Godot do. > There's no chance to "make people think" that such things can't exist. A lot of people in this very thread seem to be under this impression. > it's that integrated tools are often much more effective when building things out of multiple different pieces Integration can happen in different ways. Complete integration (aka being made by the same team and tightly coupled) is not necessary for a great experience. For programming itself we’re already free to choose our editor of choice, and they often integrate quite well. People used to say the same about Visual Studio and C#. > Custom file formats exist because features differ, and even for similar features, the semantics differ. There is a lot of common functionality in modern engines. Not to mention that formats can be extended to contain additional metadata coming from customised parts of the editor. And editors can be extended to allow new formats too. Starting with the automatic assumption that there cannot be a common format is incorrect.
- bob1029 4y agoDecoupling the user interface from the actual engine seems like an excellent idea on the surface. Aside from your post here, has anyone even proposed an "engine agnostic" IDE experience for game dev? I can kinda see how it would be possible to do this - code your engine against some common editor API rather than the other way around. The idea of being able to swap to an entirely different engine but keep all my content, tools, etc is pretty fantastical, but I don't see why it would be impossible.
- vanviegen 4y ago> but I don't see why it would be impossible. Different engines have different ways of handling the same (or similar things). Either your IDE would need to provide an abstraction on to of all the engines (making it sort of an engine by itself), or the game makers would need to specify a lot of attributes for each game object in multiple ways, often one for each supported engine.
- ratww 4y ago> Different engines have different ways of handling the same (or similar things). There is already a lot of common ground, and this is what I'm after. It can even be just component-based, like Unity, which is a great abstraction understood by a lot of people. Engines that are too different from don't have to be supported by such an editor, or would require some extension. > Either your IDE would need to provide an abstraction on to of all the engines Why? I don't care if engine X uses this editor or not. I can't force them. I probably wouldn't be able to legally make this work with something like Unity, that uses proprietary file formats. What I want is a generic editor that can provide enough functionality to be used by future engines, not a Unity/Unreal/Godot replacement. Engines have to do heavy lifting too if they want to support the editor. If they don't, it's their choice. It's like bob1029 said above: "code your engine against some common editor API rather than the other way around". > or the game makers would need to specify a lot of attributes for each game object in multiple ways, often one for each supported engine. This is trivial to do with computers: just do what Unity does with Reflection. Just provide metadata for the types of components, containing the list of attributes. It can be a JSON file or something like that. Or provide something similar to VSCode Language Server where properties can be queried with an API. Your mistake here is assuming that such a tool would be complete from the get go and replace all competition, without needing to talk to other software. I'm not a venture capitalist, I'm a software engineer. I'm fine with limitations in my tools.
- ohgodplsno 4y agoIt's not just vertical integration for the sake of it. There are many, many, many things that are simply made easier by having every component able to talk to eachother. UE5's particle system can talk to the sound system back and forth, which can trigger gameplay events and send data to the renderer, etc. This leads to extremely complex interactions being rather easy to do, and that is exactly what large games want nowadays. You don't want to painstakingly time your cutscene to begin exactly 2m15s after the beginning of the level because you know that's where the song will begin but shit wait the intro can loop, no, you just have a gameplay event that starts the sound, the sound regularly says "hey, if you're ready, please trigger the cutscene now" and everything works together. Getting this with a bunch of libs glued together is simply impossible. This is a design that was thought of for years before it happened properly.
- ratww 4y agoThe components are a concern of the engine and the game code, not of the editor. There is nothing preventing components from talking to each other when a generic editor is used. Have you ever played with Unity? Their modular design is generic enough to allow different components to be connected to each other. Not to mention that interconnection between components is often also achieved via code inside each component (example: gameObject.GetComponent() in Unity), which is not really the concern of the editor, but rather of the engine and the game code. > Getting this with a bunch of libs glued together is simply impossible. I really don't see what "bunch of libs glued together" has to do with my comments at all. Are you sure you answered to the right person? Are you answering to the article in general?
- oneoff786 4y agoWhile true: updategame() Renderframe()
- pjmlp 4y agoI have books that already refer to game engine as integrated experience that date back to MS-DOS days.
- mysterydip 4y agoCare to list some of them? I love collecting DOS-era game development books.
- pjmlp 4y agoThey are stacked at my folks place, can't remember the names. One is about doing a return to castle of wolfstein clone, including network code for Novell networks, the other a 3D engine in C++ for a space shooter.
- pizza234 4y ago> One is about doing a return to castle of wolfstein clone Is it "Tricks of the Game-Programming Gurus" (https://www.amazon.com/Tricks-Game-Programming-Gurus-Andre-Lamothe/dp/0672305070 https://www.amazon.com/Tricks-Game-Programming-Gurus-Andre-L...)? > a 3D engine in C++ for a space shooter The other seems to be "Building a 3D Game Engine in C++" (https://www.amazon.co.uk/Building-3D-Game-Engine-C/dp/0471123269 https://www.amazon.co.uk/Building-3D-Game-Engine-C/dp/047112...). It's amazing to see old gamedev books :)
- pjmlp 4y agoYep those are the ones, I recognise the covers, thanks for tracking them.
- mysterydip 4y agoI have most of LaMothe's books, but the other one was new to me. Thanks!
- k__ 4y agoBit like with frontend frameworks.
- stonewareslord 4y agoI agree with your assessment. > a stack made for a single game is not a game engine. For a concrete example: the newest Lego game, Star Wars the Complete Saga, had a complete engine rewrite ("NTT") and the new game is the only one that runs it. I wonder what term the author would use to describe NTT, which isn't designed to run a single game or have a community.
- ohgodplsno 4y agoWhat does a complete engine rewrite mean ? Is it just a new renderer with deferred shading ? Is it a bunch of new gameplay tools ? Is it a start-from-scratch thing ? (Which would be absolutely stupid). Game engines are more of an ecosystem. Yes, the community is a thing because the devs seem to be a small indie group that uses Godot so they can ask for assistance, but Frostbite does not have such a thing (well, maybe internally at EA), and yet noone would say it's not an engine. As long as, through an upgrade, your engine keeps the same way of working and you're familiar with it, it is an engine as a whole. UE and Unity are two different engines because the workflows are different. But UE4.0 to UE5.0 is still the same engine, you won't take that much longer to get back in the groove.
- ratww 4y ago> Game engines are more of an ecosystem Not really. In the case of Unreal/Unity/Godot (and perhaps things like Quake and Source before it), sure. But there is definitely more to engines than this, which is the argument being made. We probably need a better term to differentiate traditional engines from the big ones that come with an integrated editor. But until we do, there are many sizes of engines. > As long as, through an upgrade, your engine keeps the same way of working and you're familiar with it, it is an engine as a whole Again, this is the controversial part. Engines are traditionally not about editors and workflows and whatnot. Sure the term has changed recently and a lot of people now have this impression, but until there's new terms, engines come in different sizes.
- ohgodplsno 4y agoYou can still find rotary engines in cars, that doesn't mean that the first thing that comes to literally everyone's mind when you mention engines is the classic combustion engine with cylinders. Lots of big claims about engines traditionally not being about editors, but nothing to back that up. Engines have always referred to the whole package, and to something somewhat reusable. Saying "recently" and mentioning the Quake Engine before makes me question your definition of recent. Thirty years old in an industry that's barely 50 if you count the first popular games like Oregon Trail? Where do you fit Monkey Island, using the SCUMM Engine in 1990 ? You don't see anyone talking about the Celeste Engine, or the A Link to the Past Engine, because they're bespoke, single purpose implementations. So, no, engines have pretty much always been about reusable tools, that may or may not bake certain gameplay elements in, but are overall just a tool.
- otikik 4y agoI always picture it like this: The shotgun is a library. The motorbike is a framework. The (unskinned, inactive) T-100 is a game engine. The Arnold-skinned Terminator shooting at the T-1000 with the shotgun while riding away in the motorbike is a video game.
- charcircuit 4y agoI think you are confused. Editors are not part of the game engine. Unity editor is separate from Unity the game engine. When you ship your Unity game it doesn't bundle the engine with it.
- ratww 4y ago> When you ship your Unity game it doesn't bundle the engine with it. Sounds like you're confused yourself :) You probably mean "it doesn't bundle the _editor_ with it". The part uncontroversially accepted as being the "engine" is definitely bundled.
- flohofwoe 4y agoWell that's how I see it too, but for most people "Unity" and "Unity engine" is the same thing.
- nineteen999 4y ago>The original meaning of "game engine" which made much more sense was: "the actual code which enables the game to run", e.g. just the runtime parts, the tiny piece of code that's dangling off the end of the asset pipeline ("tiny" relative to the work that needs to go into authoring tools and asset pipeline). It still means that. When you hit the "Build" button in the Unreal IDE, you get your assets and custom code packaged together with the engine code. It doesn't bundle the IDE. I haven't used Unity in years, but from what I remember it works the same. The IDE is only there (at least in Unreal's case) to give artists and programmers an easy workflow to develop the finished product, after which it's cast adrift. You need an integrated IDE these days because the number of features that are included in the engine is insane. If you're doing shaders and you're not writing them in raw GLSL, then the Unreal materials interface in the IDE is indispensable. If you're doing visual scripting (eg. Blueprint) the same applies.
- giancarlostoro 4y agoTo me a game engine is anything that doesn't include a full blown IDE but still allows you to make games using any IDE, closer to a library. I agree with you, I don't know what could fix this to make a subtle distinction between the fully integrated game development environment maybe IGDE? Not sure, but it is more helpful to know how much they hold your hand. I'm okay with a very small library that doesn't provide all tooling as long as its in a language with good tooling, or they provide SOME tooling.
- bitwize 4y agoYeah, back when I was growing up and Carmack was everyone's hero, "game engine" basically meant the game's main loop, and everything that supported that main loop. The code that makes the game actually work. These days "game engine" basically means Microsoft Access for gamedev. And if you don't use one you're basically leaving money on the table, so it makes no sense to try and be a Carmack in today's scene.
- seba_dos1 4y agoMy own engine used to be a single-game stack. Now there are more than 40 games written with it out there (and only one of them with its code written by someone else than me). It's not an IDE at all, just a bunch of (often intentionally leaky) abstractions on top of existing libraries. It comes with a tiny external editor written in PyQt that produces animations that can be consumed by the engine (which is optional, as they can be created by hand too), plus a bunch of scripts that use Docker containers to effortlessly cross-build it to several platforms. I really don't care about other people using this engine. It's not for them, even though it's public and FLOSS. It's a tool for me (and people I work with) to make it easier for me to write my games the way I want to write them. I wonder what the article's author would call it ;]