Turrican II WHDLoad slowdown

[Radertified]

Here's a strange one.

Using the WHDLoad version of Turrican II with a no JIT setup, has anyone noticed the slowdown when the screen "opens" before you see the player? When you enable JIT, it works perfectly.

I've uploaded a video of it to http://eab.abime.net/zone/turrican2.mp4

I first saw this on Amiberry and reproduced it in WinUAE so it's not just a single machine occurrence. CPU, RAM, emulation speed, etc. don't seem to matter. Just JIT.

Does this happen on a real machine? Is this a bug? If so, where? UAE? The WHDLoad slave?

[jotd]

i suppose your files are xpk pzcked? maybe twice.

is that really a big issue btw?

[Radertified]

It's a pre-installed version from RetroPlay and from what I can see from the data files, they're not packed.

As for is it a big issue, nope! I just thought it was strange so wanted to mention it in case anyone was curious.

[turrican3]

could you post your config file ???

[Wepl]

Which slowdown?
You mean screen of pages before it is disassembled? At this point the level data is loaded...
I would recommend to load the game from floppy to compare.

[Radertified]

I've found enabling/disabling "More Compatible" reproduces this too, so I'm guessing this has to do instruction caching instead of JIT.

I've confirmed this in WinUAE. I'll have to test in Amiberry but presumably that's the fix there too.

Originally Posted by turrican3

could you post your config file ???

It can be reproduced with a quick start A1200 config. Turn off "More compatible" in the "CPU and FPU" tab, add a HDD and boot the WHDLoad game.

Originally Posted by Wepl

Which slowdown?
You mean screen of pages before it is disassembled? At this point the level data is loaded...
I would recommend to load the game from floppy to compare.

Yeah, the screen of pages, but it's directly after the level data is loaded. When using a floppy, it's about a second after the drive stops being accessed and the game begins.

I had tested with a floppy previously and didn't see the same thing, but now I tested and *DID* see it, so it's not a WHDLoad slave problem. It's an emulator configuration problem.

[hexaae]

I use this additional tooltype (requires 'uae-configuration' from WinUAE package in your Amiga C: dir...) and see no slowdown or issues in TurricanII WHD in my high-end 060 emulated Amiga (see my signature):

ExecutePostDisk=C:uae-configuration cachesize 0 cpu_speed real immediate_blits false cpu_memory_cycle_exact true waiting_blits true

[Radertified]

Using uae-configuration is a good idea when using WinUAE. Unfortunately it's not available on the Pi with Amiberry

EDIT: Copied it from the WinUAE archive onto my Amiberry HDD setup and hey, it works. No reason why it wouldn't, so that's good to know!