Engines has been (And is to a large extent) bad business because unless you really do something _really special_ it's way expensive for little gains (especially if you're targeting realistic games since there is so much to focus on before even considering portability).
And I say this as someone who started out working on custom engines (but am out of the business outside of hobby stuff).
I read a lot of opinions on whether it is a good idea and it all boiled down to ‘my god, no, don’t write your engine. That said, I did and I am sure glad I did invest 3 years on a framework I know like the back of my hands’ and that told me exactly what I wanted to hear.
It’s like the whole AI debacle, really. If your goal is to ship a product, go with a premade engine. If your goal is to enjoy the craft and learn how stuff works, and you got that itch to do it the difficult way, then roll your sleeves and dive in. It’s always a pleasure to play a game with a completely unique feel.
Also, like what do you mean by engine? Minecraft was made with LWJGL.
If your goal is to sell a game in 3 months, sure, but not even Unreal Engine will magically turn a rushed game into a good product.
90% of the development time is making a fun game in the first place, and you’re on your own there.
That is exactly how I perceived the game industry to be before I worked in it. Now I know that there are many objectively excellent or even innovative or influential games that do not sell, or also do not sell well enough to support their development costs.
So I’m looking for an “objectively” (figuratively) excellent game, that has not sold many copies at all. A game on steam that should be popular but isn’t. Do you have any examples?
This entire saga of XBOX fka Microsoft Gaming is proof to the contrary
I loved the old STALKER games, and the wackiness of their engines was a lot of the charm. I ended up buying the new one out of nostalgic dedication and it's probably the worst example of "Unreal slop" I've experienced, having not bought many newer games. I'm sure the butchers running Xbox have run the numbers and think they'll make even more money throwing armies of contractors with allegedly fungible skills at the next Doom games, but I'll leave others to bankroll that while I enjoy games I don't need frame generation for.
Where they actually messed up was not licensing it more aggressively to other companies like Epic has been with Unreal.
- Huge tax write-off
- Commoditizes their complement
- If it succeeds, ultimately lowers the cost of triple-A game dev
Doom was absurd in the capability of squeezing terrible machines for high framerates and great visuals.
I also remember seeing a bunch of cool explanations of their rendering pipeline
There are very few games where the engine is what made all the difference. Maybe something like Half Life 2 with the source engine is the exception, but ultimately, what makes a game good are traits that can be universally applicable to any engine.
Truth is, it’s not that 90s anymore. Hardware has advanced to the point that you can have general purpose game engines that can be molded to any type of game. You do not need purpose built engines anymore.
And someday, if you can imagine, we’ll just have AI churning out visual representation of game state, turning game development purely into a declarative data driven exercise.
I disagree, I think there's an over-emphasis on generating high quality individual frames and a expectation of what it is you should be able to do in games.
You can have a game that is photorealistic but you turn around and have your gun barrel poke into the wall and disappear. How many games can you throw enough junk into a river and make it change course eroding a new path for itself as it goes?
Some games rely on clear specific rules of an engine for the player to know because the rules are an integral part of the game, and any inconsistency in implementation creates a feeling of being cheated. Often you can implement such things in standard engines, but you are working against them the entire way.
You could have a game where a player sees a pylon and knows that because it is made of metal you could melt one of the legs and make it fall over. but to do that the entire construction of the game rules are integrated into the world. Most games teach the player that things like pylons are static objects unless they need to be destroyed for a plot point in which case just this one is different. Perhaps the player just has to learn that pylons are one of the class of destroyable things. Making emergent properties goes engine deep.
>And someday, if you can imagine, we’ll just have AI churning out visual representation of game state, turning game development purely into a declarative data driven exercise.
And therein lies the problem. A game engine is game state. You can make it pretty any number of ways, The engine will still be the thing deciding what you can do, and it is the things you can do that makes it play.
Maybe if you ignore the entirety of the retro gaming scene where people are using old engines and modified old engines because they bring along a lot of the feel and expected behavior.
The average modern Unreal and Unity game feels like shit, but some dev's can pull off making new engines behave like old ones we love. It requires a lot of work. Just look at New Bloods catalog of games that pulled it off. DUSK (unity), Amid Evil (UE4), Ultrakill (Unity). Each one of those games had a lot of passion behind them driving for gameplay perfection in the style of a retro game and/or engine.
Yeah, no. Perhaps on the mobile slop world as vehicle to sell ads, but I wouldn’t even count those as games.
I have the ability to make the engine I’m making on my own, but trying out AI for the experience. It really sucks in ways that make it good for what an engine needs. A good engine needs to plan pretty far ahead and plan well at high architecture level. AI is actually awful at that despite it being okay at making plans at implementing said plan.