Re: [hatari-devel] Hatari screen test

[Thomas Huth <th.huth@xxxxxxxxx>]

Am Thu, 28 May 2020 21:22:00 +0200
schrieb Thomas Huth <th.huth@xxxxxxxxx>:

> Am Thu, 28 May 2020 02:23:38 +0300
> schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
[...]
> > However, the really interesting thing is that
> > *5* additional VBLs are needed for screenshot
> > to look correct! [1]
> > 
> > Looking at the assembly code, install_all()
> > subroutine sets A0 value first, then does
> > 2 vsyncs, and get_lines() subroutine does also
> > 2 vsyncs.  These are before the real fullscreen
> > routine starts, which explains the need for
> > extra 5 VBLs.  
> 
> Are you sure that your breakpoint triggered at the right point in
> time? A0 is only set to FFFF820A in the open_top2 section during
> fullvbl ... which should be called only after all the initialization
> stuff has been done. During install_all, A0 is set to FFFF8201
> instead. ==> Please double check that your breakpoint really triggers
> at the right location.

I just notice another thing: Please check your --frameskips setting. If
it is set to something different than 0 (it is "auto" by default), then
you could run into the situation that the screen is not updated yet,
though it should be correct already from the ST side.

 Thomas