very good points people-
hey HLPBB admins, perhaps we should get a forum up for this with the kind of traffic I forsee being generated.
As for a new file type to replace pof - i agree that is a viable option, but we really need Eternal One, because I don't quite grok BSP splits - i figured out how to generate adquetally compliant data for the POF BSP/IDTA but I really need to grok that kind of information... this project is going to require me to learn
a lot about 3d programming. As for the alternative file types - that is a great idea,

my idea for that is
All supported data types can go in the data tree or vps for the engine, the engine then auotmatically compile those models each time they're changed [UTIME compaired against the compiled version] and places them in a temp dir.
Mods can be switched on-the-fly on a mission-by-mission basis - by the data tables only be loaded into memory in the pre-mission loading, instead of at engine startup like volition does, with the origional engine. This will allow there to be multiplayer mods that automatically switch, you can have multiple data structures at a time - ie the directories are "data" for the main data, "babylon5" for the babylon 5 mod, "Derelict" for derelict, and so on. The mods can also have vps - the data tree and the associated vps are listed in "mod data files" in the main directory - and the default vps can be loaded, or completely overwritten - or you can load one vp with the customizations, then load the normal vp with all the other data [the first VP loaded owns the file, occurances in later vps are ignored]
I would like to raise the polys that can be in a scene, and even make missions where you skim terrain [that will require some huge terrain models], with fog, etc, other atmospheric effects
I naturally want new effects, new weapon types, etc.
With the documentation you could design an entirely new game, will all fresh data. We're just writing a new engine, with knew capabilities - just because it groks Volitions VP and POF files doesn't make it illegal, groking MVE would though - because Volition doesn't care about the VP and POF types, but Intergay [Titus now is it?] cares about MVE - some anonymous programmer could make a 'contraband' converter from MVE to like DivX mpeg for the cutscenes and make it a 'add-in module' for the engine, not official endorsed by the developement team.... aren't loopholes lovely