"Cycle Exact" how many games need it?

[rsn8887]

My default A500 config has "Cycle Exact" enabled by default. However, I keep running into more and more games where this option is just simply too slow on my machine. So I've been turning it off a lot recently.

It seems to me that almost no games actually need cycle exactness!

I mean even a game like Lionheart which uses insane amounts of Copper/Blitter stuff seems fine without cycle exact.

In fact, the only game I found so far that needs this setting is Nebulus 2. Without cycle exact, the doors on the tower are not visible!

So should I just turn it off by default?
How many games do you guys know that actually need this setting "on"?

Thanks in advance for help.

[Paul]

Yes you only should enable Cycle Exact if the game needs it (i.e. if the game does not work/load correctly)

[Toni Wilen]

Copper is always cycle exact (there was "fast copper" option but it was removed because it broke too many programs and didn't really help with speed because it was incompatible with most copper effects)

CE is usually only needed if game has timing based copy-protections (SPS images mainly), crappy code (most common is no blitter waiting, immediate blitter can usually fix it but not always), most common is probably program expecting slower blitter or CPU because of high copper and/or bitplane DMA activity stealing chip bus cycles (emulated very approximately in non-ce mode, most common result is flickering graphics)