Hacker News Reader

Comment by scrollaway | Hacker News Reader

There's a history of reinventing the wheel in game development just for the sake of doing so.

Until Unity became popular, everybody was doing their own game engine for their own game. All those game engines have their own image formats, sound formats, archive packing format, etc. None of this is ever open source, of course...

And before you think "in the name of performance", it's usually actually in the name of premature optimization and ends up being a bad idea. Reinventing the wheel indeed.

Edit: I've been in the games industry (specifically, in reverse engineering and dealing with these exact issues) for a decade and this is all true, and from experience. I see I'm still being downvoted, without any reasonable explanations though. If someone here disagrees, I'd like to hear it.

View on HN

> Until Unity became popular, everybody was doing their own game engine for their own game.

The very first Half-Life was already using one of the Quake engines. As was Hexen.

The first Deus Ex was using the Unreal engine.

That was all probably ten years before Unity.

Yes, I'm aware of the AAA exceptions. Source, CryEngine and Unreal Engine were around since long before Unity. They represent an extreme minority of games. Obviously the concept of game engines is older than Unity, I didn't think I needed to explain that here...

And even then, CryEngine, Unreal and Source are all engines centered on a very specific kind of game (fps style). There was no serious general-purpose game engine before that, that devs actually used.

Together with your grandparent post, this paints a fuller picture. Thanks!

I've been part of a community of hobbyist/indy gamedev since 2002. At that that time, there were very few engines usable by hobbyists due to price constraints: - Quake 3 Engine for FPS-like. Other FPS engine were moddable, but as the source code was not available it limited the possibilities. - RPG Maker for old school JRPG - Adventure Game Studio and GameMaker for Sierra/LucasArts adventure games. I could probably include ScummVM. - Mugen (and another one I forgot the name) for VS fighting games. I certainly forget some others.

These engines being tailored-made for a specific type of game, people wanting to do something else had to create their own engine, often in C++, sometimes in Python or Lua, reinventing the wheel most of the time. The barrier for entry being so high, game designers had to team with coders, but their end-goal not being always aligned (creating the game vs learning how game engines are coded) this lead to the demise of many projects.

With Unity, a general purpose game engine became available for a very low price (in particular compared to Flash). Many game designers saw it as a way to work on prototype without needing to recruit a team of coders. And for many coders, it was a way to try their hand at game design, while being able to push the engine further using C#.

Crystal space and Ogre3d were pretty active back then.

https://en.wikipedia.org/wiki/Crystal_Space

https://en.wikipedia.org/wiki/OGRE

Not that it alters your point in any way whatsoever (except to date third party engine-reuse even further), but Hexen used a variant Doom engine, not quake. Hexen 2 was the one that used the Quake Engine.

Thanks!

Reply on news.ycombinator.com