News for hackers. Stuff that matters.
Re:How does a game engine work? an overview (2016) by DeathArrow on Sunday November 07, 2021 @10:06AM (#29140003)
>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.

Re:How does a game engine work? an overview (2016) by skohan on Sunday November 07, 2021 @10:14AM (#29140092)
What about a monolith ensures better performance optimization?

And won't general-purpose engines pay a penalty relative to single-purpose engines since they have to optimize for the "average case" game rather than exactly one target?

Re:How does a game engine work? an overview (2016) by Mikeb85 on Sunday November 07, 2021 @11:24AM (#29140768)
> And won't general-purpose engines pay a penalty relative to single-purpose engines since they have to optimize for the "average case" game rather than exactly one target?

Theoretically, yes. However so many man hours have been put into optimizing engines like Unreal that in reality the answer is no.

Re:How does a game engine work? an overview (2016) by skohan on Monday November 08, 2021 @03:16AM (#29147095)
I don't agree with this. I mean, UE renderer is the subject of countless hours of effort and optimization. But for instance the startup time (or build time for that matter) of a UE game is quite long and it is fairly easy to beat in a bespoke engine.

That's one of the reasons looser coupling would be great. I would love to be able to use the UE renderer in the context of a different engine.