Re: [hatari-devel] Motion demo Susie screen

[Laurent Sallafranque <laurent.sallafranque@xxxxxxx>]

That's what I also suspected.

From all my tests, hatari CPU emulation has greatly improved in general 
(some demos that never worked with the old versions of hatari now work 
(eg: explot screen from Motion demo (I've disasm its DSP code in 2014 
and searched a long time where the problem could be and now it works)

I'm sure the cpu cycles will improve again in the future, so, no hurry 
here ;)

Regards

Laurent



Le 30/11/2020 à 22:53, Nicolas Pomarède a écrit :
> Le 30/11/2020 à 22:47, Laurent Sallafranque a écrit :
> > Hi,
> >
> >
> > I don't know if this will help, but the bisect of Suzie gives the 
> > following result (between hatari V1.6.2 and hatari 1.7.0) :
> >
> >
> > 4db18160c6141ef9a74dd0308eee41da3729a33f is the first bad commit
> > commit 4db18160c6141ef9a74dd0308eee41da3729a33f
> > Author: Laurent Sallafranque <laurent.sallafranque@xxxxxxx>
> > Date:   Fri Feb 1 19:55:43 2013 +0100
> >
> >      change: take into account the 68030 cycles in cache mode ON
> >
> >   src/cpu/newcpu.c      | 11 +++++------
> >   src/includes/m68000.h |  2 ++
> >   2 files changed, 7 insertions(+), 6 deletions(-)
>
> Hi
>
> thanks for bisecting the issue ; unfortunately, if it's a 68030 cycle 
> accuracy problem, there's not much that can be done at the moment.
> even if winuae improved a lot for 68020/030 (mmu, bus/address errors, 
> ...), cycles emulation is not accurate enough yet. In some case it 
> will be better than older Hatari version, in some other cases it will 
> be worse.
>
> Nicolas