🚀 go-pugleaf

In article <1992Dec26.163436.11402@blkbox> collins@blkbox (Chad R. Collins) writes:
>	Now, of course you are going to loose a bit of time copying the
>screens, but 32-bit copying is pretty darn quick. The question is, would
>this elimate the strobing effect? Or, as a more memory efficient way,
>just use one visible screen and do the copying during the vertical retrace,
>elimating the page flipping all together.

Up until now, this thread was pretty much hardware independent... Copying
frame buffers can be a very time-consuming business, depending on what kind
of hardware you are running on. It takes ages to copy a 640x480x8bit frame
buffer on most personal computers. (Ages > time for one frame.)

I guess you are talking about PCs and 320 x something resolution... IMHO,
most computers are now so fast that game designers should move on to higher
resolutions. Resolution independent code is the ultimate solution, but it
does cause some problems to those who are used to thinking about raster
graphics and sprites.

-- 
  Juri Munkki					       Windsurf: fast sailing
 jmunkki@hut.fi					      Macintosh: fast software