varient_weighted_mesh file structure

[Porphyr]

As far as I know, no one was able to identify the tool(s) used to create the ETW models.
The purpose of this thread is to identify the file characteristics of the varient_weighted_mesh files. I really hope this helps to come up with the correct idea.

The first four bytes are always 78 56 34 12 [xV4.], which is the little endian version of 12345678. I don't know a comparable file type starting like that
The next eight bytes are always 01 00 00 00 and 0D 00 00 00.
The next 464 bytes contain some generic information on "light_scale", "bumpfactor", etc.
464 is equivalent to 0x1D0; the eigth bytes from before could indicate the length of that section.

Obviously, some of the units have their own models (e.g. Windbüchse Jäger), while others rather use parts from other units (e.g. European Line Infantery).

Ideas or suggestions on this or the rest of the files?

[erasmus777]

As far as I know, no one was able to identify the tool(s) used to create the ETW models.
The purpose of this thread is to identify the file characteristics of the varient_weighted_mesh files. I really hope this helps to come up with the correct idea.

The first four bytes are always 78 56 34 12 [xV4.], which is the little endian version of 12345678. I don't know a comparable file type starting like that
The next eight bytes are always 01 00 00 00 and 0D 00 00 00.
The next 464 bytes contain some generic information on "light_scale", "bumpfactor", etc.
464 is equivalent to 0x1D0; the eigth bytes from before could indicate the length of that section.

Obviously, some of the units have their own models (e.g. Windbüchse Jäger), while others rather use parts from other units (e.g. European Line Infantery).

Ideas or suggestions on this or the rest of the files?

95% of this has already been done. If you can do the last 5% ...

http://www.twcenter.net/forums/showt...56#post5105656