Hi

I recently bought Blizzard 68060 accelerator, its overclocked to 66mhz.

I currently use latesta Phase5 68060 library, cyberpatcher and blizkick. Setpatch is from boingbag2

It seems to be not so much faster than my previous 68040 40mhz apollo accelerator.

What paches I should install to get it faster?? ie. Duke 3d is totally unplayable, was at least 50% faster with apollo.

WB screen refreshing seems allso slower etc.

Games like DOom, quake, napalm runs only little bit faster 10%-15%

I'm allso interested to know what options I should enable/disable from CyberGraph options?

I currently use latesta Phase5 68060 library

Are you sure you've installed it correctly?

Oxypatcher might be better than Cyberpatcher in some cases, it has more supported instructions.

If you are gaming thru ZorroII bus, it does max. 3.5 MB/s, in effect just 2 -2.5 MB/s crippling screen refresh and making everything more than 320x240 impractical. So making the difference between 040 and 060 smaller.

I would uninstall cybpergraphix and re-install selecting 060 as the processor, should install the 060 versions of the libs

If you are gaming thru ZorroII bus, it does max. 3.5 MB/s, in effect just 2 -2.5 MB/s crippling screen refresh and making everything more than 320x240 impractical. So making the difference between 040 and 060 smaller.

With the PIV there's little practical difference - less than 1 FPS in the Quake timedemo between my A2000 and A3000 (both '060 50MHz), dropping to around .5 FPS difference at higher resolutions. (Overclocking the A2000 to 60MHz gives it a few FPS advantage.) *edit* -- are the A1200 busboards are slower than real Z2?  

With the TekMagic at least, writes across the Z2 bus hit 3.6 MB/sec (according to bustest), reading is 2.8 MB/s at 50MHz, 3.6 MB/s at 60MHz. (Reading from the PIV directly is a bit slower.) Benchmarks are roughly equal up until a 24-bit 1024x768 screen is selected, where the A2000 is finally measurably slower.

-Latest libs! (040_060Libs.lha) : I currently use mmu libs
-BlizKick : I can't use this, I have 1mb kickstart/rom and blizkick soesn't support them, only 512kb roms is supported. I use CPU Fast command. Better solution would be nice.
-FBlit : It is towerized system with RTG
-FText : - " " -
-BlazeWCP : I'm running this, it doesn't affect Picasso96
-CopyMem060 : I use MPC's
-UtilPatch060 : Need to check this
-CyberPatcher : Most of apps/games are for 040/060 anyway?

-Latest libs! (040_060Libs.lha) : I currently use mmu libs
-BlizKick : I can't use this, I have 1mb kickstart/rom and blizkick soesn't support them, only 512kb roms is supported. I use CPU Fast command. Better solution would be nice.
-FBlit : It is towerized system with RTG
-FText : - " " -
-BlazeWCP : I'm running this, it doesn't affect Picasso96
-CopyMem060 : I use MPC's
-UtilPatch060 : Need to check this
-CyberPatcher : Most of apps/games are for 040/060 anyway?

To be frank, most of this is not really helping much. "CPU Fast" is nonsense and does not work for a 060 at all since it does not support it. If you want to mirror the ROM into RAM and have the mmu libs, use "MuFastROM". Not any third party program.  Additionally, depending on the board, "MuFastZero" might also help to mirror execbase into fast memory.   "FBlit" is nonsense if you have an RTG system anyhow (in such a case, blits are executed by the CPU in first place, through the RGB system, and you don't need an additional source of instability in first place). The same goes for FText. All this is already run through the RTG System in first place, no patch needed - and not exactly helping either. I don't know what BlazeWCP is, but it falls probably into the same category.  CopyMem060 is most likely not helping, only damaging a perfectly fine copy. Besides, how much software are you aware of that copies huge amounts of memory around so that this would create a measurable difference?  Seriously, the 060 should - out of the box - reach approximately twice the speed of the 040. If it does not, none of the above programs will help either. Something is then seriously wrong, for example the CPU caches are off. (No, the *CPU* command does not help here. It is the processor library, i.e. the 68060.library that is then not loaded. The CPU command is a legacy program that has not been updated and that does not support the 68060.).