🚀 go-pugleaf

In article <61@pdxgate.UUCP> griffith@eecs.cs.pdx.edu (Michael Griffith) writes:
>anyways. Hmmm. Okay, well if you limit the colors available to each layer
>that is scrolling (I assume you are talking about scrolling as in Shadow of
>the Beast) perhaps the key would lie in scrolling the sprites at different
>rates, so that you could simulate the layers early on, before you had time
>to actually set the screen data up. I don't know. Anyone from Psygnosis care
>to tell us the full details? BTW: You might notice that in Shadow of the

My sprite hardware is a little faulty (16th column is unstable), which
reveals some very interesting facts about sprite usage.  From looking at
SotB I, I would say that the whole moving foreground, from side to side
(ie. 320 + pixels) is one big sprite object, with (though this bit is
only a guess) four sprites side by side being reused again and again in
a scanline.  I found this surprising.

When I looked into this, I got the impression that the one scan line was
only necessary to reload the header info.  If you were using the
copper to move the data directly into the registers, the maybe sprites
can be reused on the same line.  I haven't had the time to check this,
but it sounds feasable...

Comments, hardware hackers?  I know that someone in Sydney did a demo
called "Bones going home" which was a sendup of SotB, but I don't know
his/her/its name to contact them and ask.  If definately used the same
system, as I got the same "bug" effect.

--
Ian Farquhar                      Phone : 61 2 805-7420
Office of Computing Services      Fax   : 61 2 805-7433
Macquarie University  NSW  2109   Also  : 61 2 805-7205
Australia                         EMail : ifarqhar@macuni.mqcc.mq.oz.au