The "Match a500 speed" Option only works if CPU is set to Mc68000.

The "Match a500 speed" Option only works if CPU is set to Mc68000.

I am booting with Mc68020, and "Match a500 speed" is too fast.

If I change the CPU from Mc68020 to Mc68000 inside a "non-system friendly" game or demo it works, but I get software failure when I change back to a mc68020 and go back to workbench.

Tested using winuae 1.5.4 public beta 4

[Toni Wilen]

Originally Posted by Sp_

The "Match a500 speed" Option only works if CPU is set to Mc68000.

I am booting with Mc68020, and "Match a500 speed" is too fast.

Behavior of match A500 speed in non-A500 configurations is undefined.

If I change the CPU from Mc68020 to Mc68000 inside a "non-system friendly" game or demo it works, but I get software failure when I change back to a mc68020 and go back to workbench.

Different stack frames. Most demos do not care but OS surely does (different data saved/restored when switching tasks etc..)

How about implementing a match amiga 1200 speed? That would be very nice.

[Dimlow]

How about implementing my setup, 1200 with 80Mhz Apollo, or my other setup with a 47Mhz Apollo , or my dear friends setup or, or or or or..


Mmm

Ok

[Mad-Matt]

A simple clock cycles slider for cpu would be welcome , with he chipset speed locked and full priority before cpu clocks.

[Toni Wilen]

How about reading earlier posts?

The chipset is already emulated cycle excact. A mhz selector in the CPU-menu would be a enough.

Pc's are getting faster and faster With JIT enabled WinUae runs 4-5 times faster than a 50mhz Mc68060. I wish I could run demos and games at
the speed they were made for.

[Toni Wilen]

Repeating the usual again:

It is never going to work without emulating 68020+ internal caches.
JIT can't be throttled.

Caches needs to be emulated because with high DMA contention cached instructions can run very fast compared to fetches from chipram. Not cached fetches may cause CPU to stop. (speed difference can be huge with exact same clock speed)

Simply CPU speed selection wouldn't improve compatibility without cache emulation.

-> Either you get (too) fast emulation (like now)
or extremely slow but exact emulation. (nobody would use it)

Also I am not interested in CPU cache logic emulation.

-> final words:

A500 mode: exact and "slow"
68020+ modes: fast. games and demos that don't like it: tough luck.

[jotd]

I'm using "match A500 speed" sometimes with my 68040 config to slow things down and it kind of works. Not sure it is cycle exact, but slows things down.

BTW Tony I thought of a nice option to add: why not an option which enables JIT only when in RTG mode?

That would allow to run all PAL apps (most of them are games) without JIT (no or less blitter/speed problems, easier debug/smc/hrtmon, no strange effects), but get full speed when returning to RTG WB.

Personnaly, when I develop whdload slaves with WinUAE, I use JIT to assemble the code/load/run the slave, but when the game runs I often need to debug/set wd or smc options which don't like JIT

[Dimlow]

BTW i was being sarcastic, i don't play games so slowing speed does not worry me at all, the faster the better i say.