CompuServe Messages

No problem. If you need any details on the format (or .FLX format) just let me know. Oh yea, one more detail about SS2 compression. Autodesk defines operation bytes in each compressed packet. They define a opcode of < 0 to mean copy WORDS and > 0 to mean replicate a WORD (I might have these backwards). However '0' is undefined in the spec. This don't make sense since if you have to skip over more pixels than fit in one packet you will need another packet to encode the pixel skip. This is a good place to use a '0' opcode in your encoder, and it seems thats what '0' is used for. However an opcode of 0 will break some (most?) players on the PC (even some versions of aaplay). If you use a '0' opcode for this reason, try breaking the skips up instead. Really they should fix the broken players out there, but at least this can help avoid the problem. In other words, don't create packets that contain nothing but a pixel skip even though it seems legal. Try loading a FLX file into AutoDesk Animator Pro someday and watch it crash! Also, I'm sure your aware of the 4,000 frame limit in FLI and FLC files 🙂 And FLI, if you create them, must be 320 * 200, unlike FLC.