Jaguar wrote:To create a map editing tool that can create terrain using heightmaps, fractals, or bezier patches/surfaces. It can then save the vertex/triangle data as a binary file for the engine to load.
Perhaps split that up.
Have the map editor create text source files and then have a "map compiler" that creates the binary files.
Carmack's earlier engines (and Half-life too because it used a modified Quake 1 engine but with some improved compiling tools) tend to take that approach.
Maps are actually text files (can be hand-edited in Notepad, even) which are then compiled by a map compiler into a binary file (at this point, they can be used directly but lack lighting and lack optimising). Then there are other programs which calculated the precalculated lighting (I doubt this is necessary with the new DOOM 3 engine, though, as all lighting I presume is now real-time and none of it precalculated as it used to be) and an "optimiser" program which re-arranged the binary file - made splits in the BSP trees at more optimal spots, balanced the trees better and the like - to make it as optimal as possible.
The arrangement - as most programmers are familiar with from their programming command line compiles and liinkers and the like - allows more flexibility. Skipping the "lighting" and "optimising" steps, say, when you just want a quick test. Hand tweaking map text files and easier exchange between map modders (who can see how other maps do particular tricks when they are text file rather than binary).
In fact, with Half-life, a guy called "Zoner" put together improved "lighting" and "optimising" tools, which gave better visual results than the original Quake ones that Half-life originally used. Because the tool chain was modular, it was real easy for this "Zoner" to write an improved tool and then just swap it for the original tool.
It's your basic modulisation and modding and extensibility approach.
As the various engines out there show, it's a real good idea to encourage modding with an engine because entire communities and new games spring up everywhere (have you seen how many Half-life mods exist? It's staggering. But that was the wisdom of Valve putting their map editor onto the Half-life CD and making the whole thing open for modding. It extends the game and, you know, even if people don't like your game then they might still buy it to have the engine to access all the other mods and games that use the engine). Also, don't forget that if you've got a really good engine and it's flexible to be modded and used for other games then there's selling potential in the engine itself, quite separate from the game. As noted, Half-life uses a modified Quake 1 engine. Valve bought the engine's source code off Carmack and tweaked it to add in hardware acceleration and cool AI.
Plus, as noted, 3D engines can be big projects. It probably makes total sense to approach it in a highly modular fashion for your own benefit of keeping it organised and easy to modify. The fact that this approach could also make it potentially sellable in its own right as a base engine for other game companies and modding communities (if it's good enough, of course) is a nice bonus on top of that.
As noted before, those who just want to create 3D games tend to grab someone else's engine and work from that rather than start their own engines from scratch (iD are the exception because, generally, that's who everyone is mostly buying their 3D engine from!

). So, you know, if you're doing all this work and the results are good then it seems fair compensation for all that hard work to potentially sell it to a few people, if you make it real good

"Words ought to be a little wild - for they are assaults of thought on the unthinking."
- John Maynard Keynes