CompuServe Thread

Hello Mr. Cyberdreams?, (Do cybers dream of rendered sheep?) Mr. Munkeby does indeed agree!! As anyone who has messed with the '57 Chevy project is no doubt aware. This method uses huge amounts of resources. THERFORE, I planned an AXP version. As mentioned in the documentation, I intend to ship this to anyone who sends in the $$$. I have not actually used "SMARTSKIN". (If you would care to donate an SGI. . .) Anyway, an AXP version would generate the mesh at render time. This would take much less disk space, and might even make up for the execution time by reducing swapping. I also thought I would mention some thoughts on the topic of AXP vs. Morph Targets (If you are getting bored, feel free to tune out the rest.): AXP: Faster (probably), Smaller (definatly), won't motion blur (AXP's just don't), you can't see where the stuff is in the keyframer. (Yes, you can see the bones, but it's just not the same.) Morph Targets: Easier to use (maybe), motion blurs (we sometimes care), I didn't think the resource drain would be so bad (oops!) Just different: Morph targets sometimes change shape as parts turn, AXP's follow the bones better. (Usually, not critical.) So which should we have to do our work? Everybody votes for . . . BOTH. Ok, no problem. P.S. If you really did not like it, I will cheerfully refund the purchase price. . . <g> Thanks for the excellent comments. If you would care to send me details of "SMARTSKIN" style enhancements that you would like I will see what I can do. No promises. I love coding, but occasionally I need to sleep. Joe