To find out if your games uses this engine, search the executable for /NgEngine. The NgEngine by Z-Axis games has very little information written about it just a few references to its name littlered throughout the main game executables. These engines were sold to developers as a product as opposed to ‘in-house’ engines that were only used by one company. If you would like to add a game to the list please make sure to check the executable for a trace of the code, sometimes developers aim to use a library but it never ends up in the final build. The games listed below each engine or middleware have been confirmed to use those engines by searching for common strings within the xbox executable themselves. In future console generations developers would move towards the full game engines, leaving some of the flexability behind. Most developers still wanted full control over their game engine but it was too costly to write a custom physics, audio or video engine for each game. However the xbox generation was the first to really take 3rd party game engines seriously.įull Commercial off-the-shelf game engines became much more popular such as Unreal Engine or GameBryo.īut the real winners were the more specific middleware libraries such as the Havok Physics engine, Bink Video Playback engine and the Renderware Graphics engine. These game engines were normally just distributed to developers in the same company and never released to other development studios therefore these are called ‘in-house’ game engines.
Game engines have always been used to a certain extent within the games industry for re-using code from one game to another. When the Xbox came out in 2001 most game developers were still getting used to the new layer of abstractions and code re-use provided by the superior hardware of consoles compared to the previous generations.
Original Xbox Game Engines Edit on Github
0 kommentar(er)
