CompuServe Thread

Double save

4 messages in this thread
#179812From: Mark BoydJul 13, 1995 1:56 AM
Hi, all; I just started using AAS this week & experienced something very odd today. I created a simple 60 frame animation at 752×480. I saved it as a sequence of .TGAs. The odd thing is that it saved the entire sequence twice! I could tell something was amiss when a DIR listing show 58 files & the progress bar was at 49% completion. It started all over at frame 0 & saved all 60 frames again. Did I set some switch somewhere that would cause this? One other question: Does/will AAS have field render capability? Sure could use it. TIA Mark Boyd Emerald Productions
#180780From: dave aguilarJul 18, 1995 8:27 PM
>> I just started using AAS this week & experienced something very odd today. I created a simple 60 frame animation at 752×480. I saved it as a sequence of .TGAs. The odd thing is that it saved the entire sequence twice! << hi Mark. didn't know if you received a response on this. is this still occuring, and does this occur when you save out to an alternative file format such as GIF? >> One other question: Does/will AAS have field render capability? Sure could use it. << maybe future wishlist enhancement? 🙂 -dave
#180885From: Mark BoydJul 19, 1995 10:33 AM
Hi, Dave; Thanks for responding (you're the first). >hi Mark. didn't know if you received a response on this. is this still >occuring, and does this occur when you save out to an alternative file >format such as GIF? We're not using it in production, yet (seems too slow so far). We have an intern experimenting with it right now. I will try to narrow it down, starting with your suggestion.
#180957From: dave aguilarJul 19, 1995 5:16 PM
>> Thanks for responding (you're the first). << sorry it took so long. <g> >> We're not using it in production, yet (seems too slow so far). We have an intern experimenting with it right now. I will try to narrow it down, starting with your suggestion. << okay. if you can reproduce this error, please let us know. that's how things get fixed around here. -dave