CompuServe Thread

#ANIM7

4 messages in this thread
#30376From: Vance SchowalterMay 20, 1993 6:00 PM
I have to state that I have a 25mhz 68030 based A3000T and have a great deal of leeway with speed, easily meeting and exceeding 30fps. I've done it in DCTV with full overscan camera movement as well as object motion. What type of memory are you using? -= Vance =-
#30400From: Mark DannerMay 21, 1993 8:09 AM
Vance, I too have a 25MHz 3000 and can't seem to get that kind of speed. The animation I was experimenting with only had motion in it's lights (thereby creating movement across the centered object) but the camera and background were stable. I have 10Meg, 8 of which are static Zips. All 32 bit. Still, if you're getting higher rates, maybe a little more experimenting is in order. Thanks for your input.
#30412From: Vance SchowalterMay 21, 1993 1:54 PM
I would think that it wouldn't be a problem. When I've tested it on my DCTV output, I was also using 4 bitplane, not 3, so I could get the best quality from it. One test I did, I had the voyager do a flyby with the camera tracking it. As it passed the camera, the Earth would come into the scene occupying 70% of the screen. Everything was moving and I used alot of stars, to boot. Another earlier test I did, had a Cylon fighter fly-in towards a planet from lower-left of the camera, seemingly just out from under the left. The deltas were huge in all of the tests and worked really well. I changed the settings in the ViewTek icon to lock the speed at a default of 30fps instead of using the jiffies. This may have made a difference, but none that I could see (from just using the function keys to adjust speed). Ultimately, an A1200 or A4000 with 040 would be the best environment to use ANIM7 or ANIM8 with, for consistantly accurate FPS. -= Vance =-
#30547From: Mark DannerMay 24, 1993 9:21 AM
Vance, the kind of anims you describe are much more complex than my test. This leads me to one conclusion… There's something I'm missing. I'll try some other anims and slap in CPUblit. Thanks, for your input.