Path: chuka.playstation.co.uk!news
From: Alex Herbert <aherbert@ndirect.co.uk>
Newsgroups: scee.yaroze.beginners
Subject: Re: GsSortClear in HI-RES
Date: Tue, 29 Sep 1998 19:22:45 +0000
Organization: PlayStation Net Yaroze (SCEE)
Lines: 27
Message-ID: <36112575.B390B4C9@ndirect.co.uk>
References: <360EDA53.9AF9921A@hotmail.com> <360FC0F5.29A2@writeme.com> <360FCF3B.BAF7BC9F@hotmail.com>
Reply-To: aherbert@ndirect.co.uk
NNTP-Posting-Host: th-usr00-30.ndirect.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.04 [en] (Win95; I)



ScoTT Campbell wrote:

> ......512-line and 256-line bugs........
>
> Have I missed a discussion about this somewhere?
>
> Is the 256 bug the same?
>

Now let's see if my memory is still working.  I had the same problem
with 512 lines.  GsSortClear() has no effect.  When .isbg=1, the screen
is cleared automattically each frame, and so GsSortClear() is no longer
needed.  But I seem to remember that this didn't fix the problem, as the
last scanline never gets cleared (due to the 512 line bug).  The
solution I opted for was to set the screen size to 640x511.  Ok, so you
lose a whole scanline, but for me this was not a big deal.

The 256 line bug is not the same.  This is when you set the screen
height to 256 lines, but only 240 are actually displayed.  Easily fixed
by setting the screen height in GsDISPENV.


Herbs