Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!ucsd!sdcsvax!ucsdhub!jack!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Fixing flicker... (Vector display systems).
Message-ID: <2824@crash.cts.com>
Date: 15 Apr 88 11:36:50 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 19

doug@eris (Doug Merritt) writes:
>You said you "didn't want to get this specific", but without more
>specifics I have difficulty seeing what you have in mind. So far it
>*sounds* like a mutually exclusive set of specifications. Can you clarify?
>Ideally what I'm after here is an architectural description; the display
>could be Alien Crayons, but how is it functionally linked to memory??

        One of the engineers' working for Evens-Sutherland described how their
system works.  Basically, the first level of software (using co-processing)
fills structures, and the second level analayzes them and transforms them into
line descriptors, which are then then anti-aliased in yet another step.  Each
step includes its' own hardware.  It really is wonderful to see what can be
done if money is no object :^).


                                                        Wade.

UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM