Compression ideas?

Does anyone have any ideas for compressing MDXs other than the zeroing of some bytes as the squisher already does?

Switching interpolation from hermite/bezier to linear? Might impact a little on quality, but it'll fair shave the bacon off.

That is a good idea. Another thing would be blanking out the names of objects.

A trickier idea would be using primitives other than triangles, but that seems to be problematic. If I go to triangle strips, it draws the whole model when I am placing the model, but then only the first strip once it's placed. Here's the model I've been working with if you want to see if you can fiddle around with it to get it to show all the strips.

I'm not so sure about totally blanking object names; I heard somewhere a long time ago that particle emitters need to have unique names. But perhaps re-name everything to have one or two characters? Don't think it'd chop much, though.

But... What the hell is a TriangleStrip? And how on earth did you work out that Warcraft can handle it?

A triangle strip is a way of defining a strip of triangles. Vertices that you add are connected to the last two vertices you added. I just guessed that Warcraft could handle them. The number that is used in MDXs for marking a section as "Triangles {" is the same as OpenGL's constant for starting up triangles, which was kind of a hint.

Interesting...

But if it's not showing properly, I'd suspect it's another feature of Warcraft that they just didn't get round to implementing; though it could be this sort of thing is involved in ribbon emitters?

Clever, maybe that's it. They wouldn't need any more than one triangle strip for those ribbons.

If you try to even look at rotation keys in Magos', it eats them up.