Bare bones "fly-through" mod to show engine speed ?
phoenixbbs
Join Date: 2003-02-10 Member: 13379Members, Constellation, NS2 Playtester, Subnautica Playtester
in Modding
There are still many users complaining that the game doesn't run as well as the Source engine, but as we all know, the engine itself is very good.
Does anyone know how hard it would be to produce a "mod" that will load the maps, and allow the user to do a "fly-through", without any game code dragging the performance down ?
I know the existing "spectate" mode is generally a lot quicker at moving than playing "in-game", but the Insight mod added a lot more code that might slow the performance overall.
I suppose as an "add-on" to that, a map that has a series of linked rooms that could show incremental levels of detail and effects would give an idea of just how well the engine performs across the range of features.
Does anyone know how hard it would be to produce a "mod" that will load the maps, and allow the user to do a "fly-through", without any game code dragging the performance down ?
I know the existing "spectate" mode is generally a lot quicker at moving than playing "in-game", but the Insight mod added a lot more code that might slow the performance overall.
I suppose as an "add-on" to that, a map that has a series of linked rooms that could show incremental levels of detail and effects would give an idea of just how well the engine performs across the range of features.
Comments
But this mod would probably be pointless. If you have more fps then , you know what we already know: mostly the LUA side of the game limits performance.
If you don't have more fps then, it gets complicated with so many pc configurations, settings, and what not.
Not sure exactly what this mod should accomplish.
Sadly, I know sweet nothing about modding, so couldn't do it myself :-(
Isn't that kind of a semantics argument though?
By making the distinction between the rendering engine and the rendering engine plus the game code, you're kind of removing a big chunk of the actual game part of the game engine.
It's not really a game engine if you can't play any games in it, it's a realtime geometry rendering engine. AKA what spark was before they built a game on it.
When people blame the engine, what they mean is 'the game runs badly out of the box, not due to unreasonably poor hardware or unreasonably high player counts'.
Which is true, the game runs badly oftentimes, saying 'if you stripped out all the game code and just rendered the levels it would run fine' is not really very helpful. The rendering engine is designed to have its game code written in Lua, so that Lua is part of the game's engine.
Saying the C++ bits are fine so we should all be happy doesn't make a lot of sense.