I got bored...

[General BlackDragon]

So far we've done the apc, artl, cnst, haul, figh, hraz, ltnk, tank, turr,

[Apollo]

Could make a texture override pack for the models if Ken added code similar to what Tug and I did in BzE.

In the odf i override the models default skin with these:
baseName = "avfigh"

TextureLod1 = "bvraz00.map" //Lod1 = Main object skin
TextureLod2 = "avcpit01.map" //Lod2 = Cockpit texture
TextureLod3 = "bvraz00.map" //Lod3 usually same as Lod1 skin

[Nielk1]

I guess that is doable due to how BZ1 uses 1 texture for an object.

It would probably also allow you to reduce the number of model assets.

[Apollo]

Quite a bit yes.

[Ultraken]

What would really reduce the clutter is a model format that combined the VDF/SDF and GEO files into one file...
(I always found the separate GEO thing baffling. Why would anyone ever do that?)

[General BlackDragon]

I vote .XSI

[Apollo]

If it would still blow apart like it does now.

Some ascii format used in 3D studio max or Maya would be good.

If you did that i would like to be able to use long names although the 3DE exporter can't use them, we would need a better exporter.

[Nielk1]

Older ASCII X and XSI formats are pretty simple, though a bit dated.

[Ultraken]

I can see the appeal of loading raw model assets, though their structure usually fits for the needs of the modeling package better than the needs of the rendering engine.

[Nielk1]

The to memory model conversion would best be cached, in an... MSH of sorts.

Best find an existing game ready format out in the net instead of bringing that mess back.

[Apollo]

While games like Battlefield export from the modeling app. to a binary format for the engine, this doesn't allow the artist to make manual edits before conversion, which reduce turn around time when trying to fix problems.

Besides, the model format can be used in other ways like promotional material.

[Red Spot]

I've always appreciated the system that Rome Total War uses.
One model, with loads of different skins, unit names, and potentially different characteristics.

(1 File basicly creates the unit entry with a model and skin assigned.
Copy paste with different unitnames to create different sets.
An other file allows you to set up the actual units, linking to the previous file, like the odf's allow in BZ2, but with Rome its one file for all units.
If you want to create 1 unit with 16 different skins its very easy to do.)

[Ultraken]

I can certainly appreciate the "cut out the middle man" approach that Battlezone 2 used. What might work would be a cooked binary format for speed and a raw binary or ascii format for ease of content creation. Raw and especially raw ascii formats are somewhat slower to load, especially if they have to do any load-time data processing, but they would be a good choice for rapid iteration.

[Nielk1]

@RS
1 for for all units, you mean like Dark Reign? The single most annoying to mod game I have ever modded, where to add one unit you had to edit the entire unit definition list? Darn glad BZ is modular.

[Red Spot]

Apparently not then if DR works that way.
Just slap in an extra model and unit in the respective files, easy as can be. I could teach an 8 year old with no PC-experience to do this
Just dont forget to add the unit string to the correct file.

You do need to remember the files you need to edit as failing to create an entry there may cause errors/anomolies, but seeing as the devs didnt even complete the lists its notaceable ingame that the file system is somewhat forgiving. (if you have rome, select the barbarian units and check their units stats and see how the devs forgat to incoperate unit-pictures)