Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!tektronix!reed!percival!baer From: baer@percival.UUCP (Ken Baer) Newsgroups: comp.sys.amiga Subject: Re: New ANIM specs Message-ID: <1241@percival.UUCP> Date: 6 May 88 00:06:46 GMT References: <1237@percival.UUCP> <6743@swan.ulowell.edu> Reply-To: baer@percival.UUCP (Ken Baer) Organization: Funkytown Software International Lines: 27 Summary: Interchange converts objects, not ANIM files In article <6743@swan.ulowell.edu> page@swan.ulowell.edu (Bob Page) writes: >baer@percival.UUCP (Ken Baer) wrote: >>If you want to read or write Byte-by-Byte (Scupt/Animate 3D) >>files, you're out of luck. > >Isn't this what the Interchange program does? > >..Bob No. This seems to be a very common misconception. Interchange will convert 3D objects between Videoscape, Sculpt/Animate3D, Forms-in-Flight (and Animation:Apprentice soon, I hope :-). It does not deal with the final ANIM files in any way. Byte-by-Byte won't tell anyone what their format is, so there's no way for anyone else to do anything with all of the great animations people are doing with Sculpt/Animate3D. What if you want to use a ray traced animation with the Director. Not only will the Director not play that anim, but there's no way convert it over since nobody knows the format. There's a whole slew of animation products on the way that will work with the new ANIM format, and won't work with Byte-by-Byte animations. If BbB isn't going to use the ANIM format, they should at least release their format. It'd be to their advantage. -- -Ken Baer. // Hash Enterprises: When the Going gets Weird, the Weird go Professional \X/ USENET - ...tektronix!reed!percival!baer OR baer@percival.UUCP, BIX - kbaer, "while (AINTGOTNOSATISFACTION) { do stuff }" - RJ Mical