Article View: comp.sys.amiga.tech
Article #8488Re: Fixing flicker, & future frame rate issues
From: Bryan Bayerdorffer
Date: Wed, 13 Apr 1988 22:09
Date: Wed, 13 Apr 1988 22:09
46 lines
3131 bytes
3131 bytes
In article <2954@leo.UUCP> harald@leo.UUCP ( Harald Milne) writes:
=- Well, I wouldn't go as far as saying FF is flawed, it does what it was
=-designed to do. Remove flicker.
=-
Oh? Gee, you must still be driving a 1975 Pinto. It too does what it
was designed to do, only it has this tendency to come apart under certain
conditions. And here all these years I thought it was a flawed design.
=- However you are correct in saying that an object can come apart. I just
=-saw this last night by accident. But, and a big one at that, it was visible in
=-the silly and useless boxes demo. I guess this demo blits so fast, it exceeds
=-the 30HZ display rate of video. It was barely perceivable. The only reason I
=-noticed it, was it just didn't "look" right. You would never know if you had
=-never seen the demo without FF, and 2 amiga's side by side.
=-
=- On the other hand, I would defy you to create a "useful" animation
=-that would make this "defect" perceptable, much less objectionable.
=-
=- Are we worried about the Amiga going trans-warp? I'm not trying to
=-be nasty, but if you can, I'd like to see it!
=-
If you read my latest article, you will see it plainly stated why
objects DO come apart even thought the motion is synched to the 30Hz display
rate. If you really did see the fF in action, then you saw the mouse pointer
come apart, and you will see it in every animation that moves anything faster
than 1 pixel/(1/30th sec).
=- I'm not 100% sure you would need to buffer even 2 frames. If I
=-were a clever engineer, I would use a dual port video ram to clock out one
=-half-frame at twice the speed, along with the other, while a half-frame was
=-being clocked in slower, behind the first half-frame going out. How's that
=-for total confusion!
=-
See if you still say this when you've thoroughly understood the problem.
=- I suggest you guys chew on this a bit.
=-
Ick! Not after you've touched it!
______________________________________________________________________________
/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|
_No dark sarcasm in the classroom|_____|_____|_____|_____|_____|_____|_____|___
|____Teachers leave the kids alone__|_____|_____|bryan@mothra.cs.utexas.edu___|
___|_____|_____|_____|___{ihnp4,seismo,...}!ut-sally!mothra.cs.utexas.edu!bryan
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|
Technical Details
Message-ID:
<11234@ut-sally.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ncar!noao!ut-sally!mothra!bryanReferences:
<11157@ut-sally.UUCP> <8528@agate.BERKELEY.EDU> <11182@ut-sally.UUCP> <8577@agate.BERKELEY.EDU> <2954@leo.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!lll-winken!lll-tis!ames!ncar!noao!ut-sally!mothra!bryan From: bryan@mothra.cs.utexas.edu (Bryan Bayerdorffer) Newsgroups: comp.sys.amiga.tech Subject: Re: Fixing flicker, & future frame rate issues Message-ID: <11234@ut-sally.UUCP> Date: 13 Apr 88 22:09:38 GMT References: <11157@ut-sally.UUCP> <8528@agate.BERKELEY.EDU> <11182@ut-sally.UUCP> <8577@agate.BERKELEY.EDU> <2954@leo.UUCP> Sender: news@ut-sally.UUCP Reply-To: bryan@mothra.cs.utexas.edu Organization: Spam Detection & Removal Squad, Austin, TX Lines: 44 Spam-Content: Nearing Saturation Point