Tri-Strip Madness

Actually, to be more precise, I suppose this should be called “Vertex Shape LOD Data Madness”. The data flowchart spec for it has an if branch label “If TopoMesh Compressed Rep Data V1”. What does that mean?! It’s not something controlled by the prior two fields, as far as I can see. The TopoMesh Compressed LOD Data does have a version number field which can select for “TopoMesh Compressed Rep Data V1”, but the “TopoMesh Compressed LOD Data” is the alternative not selected by the “If TopoMesh Compressed Rep Data V1” branch. The ISO 14306 standard isn’t any help, it just repeats the same maddening chart.

The good news is, I think I have the Int32 Compressed Data Packet mk 2 more or less implemented now. (It hasn’t been tested yet; I need to figure out the above nonsense to get to a point where it can be.) I started up a completely parallel set of classes for mk 2, only to realize that mk 2 was mostly just mk 1 without the context-shifting stuff. So mostly handling mk 2 just meant initializing the next context field to 0.

This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s