Article View: comp.sys.amiga.tech
Article #8525Re: Fixing flicker, & future frame rate issues
From: Bryan Bayerdorffer
Date: Fri, 15 Apr 1988 22:13
Date: Fri, 15 Apr 1988 22:13
62 lines
4761 bytes
4761 bytes
In article <160@kesmai.COM> dca@kesmai.COM (David C. Albrecht) writes:
=-In article <11234@ut-sally.UUCP>, bryan@mothra.cs.utexas.edu (Bryan Bayerdorffer) writes:
=-> 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.
=->
=-> 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).
=->
=-If you're so smart why ain't you rich. The FACT is, fF is the only product
=-so far which addresses the flicker problem on the Amiga. LP phosphor
=-monitors have their own set of problems which are more objectionable than
=-and cost as much or more than the fF solution. If you find the design so
=-flawed then don't buy it. Better yet, build a non-flawed solution and we
=-will all thank you rather than argue with you. Flawed or not, it fF does
=-fix the flicker and at a fairly reasonable cost. Personally, unless something
=-better comes along, at some point I hope to get together the scratch for
=-fF and a multi-sync and have one on my desk. I find the picture coming
=-apart much less objectionable than I find flicker. At least the fF people
=-have made an attempt at a solution (which some people at least find useful).
=-
This sort of irresponsible flame contributes nothing to the discussion,
and makes its originator look like someone who is either incapable of grasping
the issues, or like someone who came in in the middle and didn't bother to go
back a couple of articles to see what it was all about before burdening the rest
of us with a paragraph of nonsense.
That said, let me respond: Just because something is a partial solution
to a problem, even the ONLY existing partial solution, is no reason not to
criticize it. Following your logic, technological development would have come
to a halt about ten minutes after it began. Moreover, the discussion is about
the REASONS why the design is flawed, not whether the people at MicroWay should
be killed for producing it, as you seem to imply. I fail to see how you could
have read anything like that into this series of articles, except that your
comments indicate that being judgemental is endemic to your reasoning, so you
are incapable of understanding how anyone else might not be. I sincerely hope
that that's not the case: there's enough of that about as it is.
IF you had been following this from the beginning, you would know that
I DID buy the flickerFixer. My only purpose in starting this thread was to
make people aware of the problem, and to discuss ways in which it could be
solved. Never once did I say, "gee, I'm sorry I wasted my money on this--
don't buy it, it sucks." In fact, I'm quite happy with the fF, since I think
I got my money's worth. A fF without the breakup problem would be nice, but
it would also cost a good deal more, since the memory would have to be doubled,
which would be a tight squeeze in the space above the video slot.
Oh yeah: I *am* rich. 8-}
______________________________________________________________________________
/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/_____/
|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|_____|
_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:
<11271@ut-sally.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!husc6!im4u!ut-sally!mothra!bryanReferences:
<11157@ut-sally.UUCP> <8528@agate.BERKELEY.EDU> <11182@ut-sally.UUCP> <11234@ut-sally.UUCP> <160@kesmai.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watmath!clyde!att-cb!osu-cis!tut.cis.ohio-state.edu!husc6!im4u!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: <11271@ut-sally.UUCP> Date: 15 Apr 88 22:13:09 GMT References: <11157@ut-sally.UUCP> <8528@agate.BERKELEY.EDU> <11182@ut-sally.UUCP> <11234@ut-sally.UUCP> <160@kesmai.COM> Sender: news@ut-sally.UUCP Reply-To: bryan@mothra.cs.utexas.edu Organization: Spam Detection & Removal Squad, Austin, TX Lines: 62 Spam-Content: Negligible