A start on the .MESH file format

[KnightErrant]

Not boring me.
I was wondering how much the 3dsmax modders
are tied to things like that. If they really wanted grouping
for changing helmuts etc. would they find it hard if that
information got lost. I was probably down on the fbx
format because I made a binary to ASCII converter and
an ASCII to binary converter using their SDK and lost the
bone info. But it did tell me I was converting a 1.6.0 file
to a 1.6.1 format when I went from binary to ASCII in the
first place. (Milkshape uses the 1.6.0 format.) Wasn't eager
to try the experiment again with an older format because
the first SDK chewed up over a GIG of harddrive space.
(I've got plenty of space, just didn't know if this was
going anywhere.)

Strategy for meshes: CA probably did a very thorough
job on western units. (Marketing, no offense Caliban.)
I'll try to work on eastern European units and Byzantines
as well as Middle East units. lod0 through lod4 as a check
here and there but otherwise lod0 on a selection of units.

[GrumpyOldMan]

Hi @KE

I posted about his working on 1.7.11 and then going on to working
on 2.0 again but I don't know what 2.0 is supposed to add.

As fasr as I can see from the forums, there doesn't seem to be much going on with 2.0. He has stated that he is working on it and the only clue I've found is this:-

Q. Will you be able to model soley in the 3D view if you want to?

Yes, you can maximize one of the viewports and do anything from any projection. That's the goal.

Whoa-oa, a gig for an SDK, it would have to be a really good SDK .

Thanks for looking at the converted meshes, as well as any that don't convert, I'd really appreciate you looking at patterns of groups, ie does it matter if groups are mixed up - Attachments within body group clusters, group sequences out of order, etc.

Cheers

GrumpyOldMan