CompuServe Messages

Actually, Swivel is a real bear of a format. It's inane. At the lowest levels, it still bears traces of its origin in Forth, such as storing X, Y, and Z in one place, and Z, Y, X in another. Since all of the Swivel data is in the resource fork, we have already developing a library of portable subroutines for reading them, so I'm not afraid of handing the resource fork side of MacroModel. As for the 3DWorks animation format, please, if you ever get a spare moment, "easily inspect" the files and tell me what everything means. 🙂 With that, we'll be able to read and write entire scenes, instead of just 3DGF. We did use that MacroModel source code from Rix as a starting point, of course. But that code is another example of the sorts of program-specific 3D data that makes a least-common-denominator standard difficult… few programs have those same concepts. There's a landscape-like data grid object type in there too, isn't there?