I've asked around to see if anyone else had this problem. It is strange as the change between the two is very small, and should be quite reliable. How sure are you that the CD32 image was burned correctly?
I the meantime I've made v1.20 available for download as well as v1.21 so people have the option.
This is a technical limitation on the Amiga. The display actually consists of three 'screens', each with its own palette. The credits screen has to be separate from the gameplay screen because it fades independently. It takes a certain number of scanlines for the copper to change palette for each screen change meaning you need a few black lines which is where you may see a gameplay sprite get cut off.
The original Turrican 2 does the same thing, although as it only uses 16 colours it can do the screen swap in 1 scanline.
Thanks for the positive comments, and the comprehensive bug reports.
I haven't look into detail for them all, but regarding 'water surface level aware color tint effect', I'm not sure what you mean. The effect where the lower part of the player changes colour when they are in the water is working in World 1. World 2 uses a different approach where the entire palette changes as you travel under water. Both of these should be the same as the original Amiga version.
As for the Make my day sound effect. I knew about this, but my choice to use an audio mixer (and so never have the music channels cut out) meant it was not as easy as the original game to modify sound effects to play at different frequencies.
"If you press MENU to change the games settings in the menu, the A500 Mini will modify the uae file, undoing some of the performance improvements and degrading the experience."
It is possible you inadvertently modified some joypad settings here too. Although I can't say for sure if that was the problem.
Anyway, I'm happy you've got it working and that you are enjoying the game!
I just installed FS-UAE v3.1.66 and v3.1.68 launcher on my Windows 10 machine.
All I did was select CD32 from the Amiga Model, the ISO file in the CD-ROM drive, and set Fast RAM to 4MB. It ran without problem. Took maybe a minute to get to the main menu though. You don't need a CUE file.
When you say it crashes, what happens? And what system are you running on?
One user reported a "Out of Chip RAM" crash that could occur when doing many playthrough's in the NewGame+ mode, in WHDLoad.
The v1.19 release fixes it. Although the change is tiny, it has not been as thoroughly tested as previous releases, so please let me know of any problems.
I hadn't noticed that the OCS Amiga version didn't do the same thing to be honest. I've added it to my list to look at if I do an update in the future.
When you unlocked the golden armour it gave you a code that you could type in at the player menu to unlock it again. That code still works. Email me if you forgot it, but it is easy to guess!
It was confusing players who expected it to be more like a save/load on demand system that lets you undo your mistakes etc. and I was getting a lot of queries about it. Really it was only ever intended as a way to resume games if the player doesn't have time to play through the entire game. Getting rid of the save slots menu clears up the confusion (I hope!).
I've no idea. If they are Amiga emulators I presume they can handle ADFs, HDF or WHDLoad files. So one of those versions should work. Don't use the A500 Mini version though unless you know what you are doing.
Unfortunately there are so many different Amiga emulators out there, I can't say how to get it working on all of them. You're best consulting the relevant communities for advice.
I've just tried to reproduce this with 4.9.1 (also 4.10.0) of WinUAE (both 32 and 64bit versions). I ran the floppy version as it looks like that was what you were using. I tried PAL and NTSC versions. I tried official ROMs and AROS ROMs. I can't get the problem to occur. Almost all testing was done using WinUAE, and I probably played it a thousand times so something odd is going on here.
If you can get it to happen repeatedly, it would be useful to have your WinUAE config file, or you may have been extremely unlucky and hit a very rare problem. You could also try moving to WinUAE 4.10.1 which was just released.
FPGA machine by any chance? The only times I’ve seen issues like that are on FPGA machines with less than perfect emulation. In some cases updating them to the latest core can fix it.
Here is a screenshot of how your THEA500/whdboot/game-data/whdload_db.xml file may look after you add the game. Normally there would be other games in there too.
I rewrote the code from scratch attempting to recreate the original as close as possible just by playing the original (and by watching longplay videos). I didn't have any access to the original source code.
I can't see that Facebook link, but I know some of the FPGA hardware has problems on World 3. There was a firmware update for minimig's that fixed it, and I believe an update for Vampire v4 is coming soon. Not sure about mister, but check you have the latest, or ask the author to look to fix it.
It does of course work on real Amigas and the latest WinUAE.
Thanks. From my experience a base A1200 would not have been able to do this without losing something (probably fewer bitplanes and fewer enemies or smaller bosses, or perhaps drop to 25hz). However an A1200 with just a little bit of Fast RAM (no accelerator needed), is a pretty competent machine, able to do a great deal more.
If you are, you need to configure the input device to act like a CD32 joypad, and not just a normal joystick. For WinUAE, in the menu (F12), go to "Game Ports", for Port 2 select your controller, and then under that change it from "Default" to "CD32 pad"
This is enabled by default, but can be turned off by settings "Secrets" to "Original" in the gameplay menu.
Each level (excluding the spaceship sections) contain three hidden drones. They become visible when shot, but also let off a sound when they are on screen as a hint. Follow the drones to find secret items. Collect all 24 secret items and complete the game to unlock a special gameplay option.
Tap fire to shoot. (Auto-fire functionality recommended).
Hold fire for lightning.
Space for powerline.
Crouch + Space for gyroscope/wheel.
Fire + Space for super weapon.
If your joystick has two unique buttons, Fire 2 will work the same as Space.
1 Button Auto-Fire:
This control scheme makes life easier if you do not have an auto-fire on your joystick.
Hold fire whilst moving to auto-fire.
Hold fire whilst not moving for lightning.
Powerline/Gyro/Super as the same as original.
2 Buttons:
For 2 button joysticks.
Fire 1 for auto fire.
Fire 2 for lightning.
Powerline/Gyro/Super as the same as original.
Joypad:
CD32/Xbox buttons are named, but other controllers work.
Red/A for jump.
Green/X for shoot.
Blue/B for lightning.
Reverse/L1 for powerline.
Forward/R1 for gyroscope/wheel.
Yellow/Y for Super.
Joypad Customised:
Set your own controls!
Select your Pad as CD32, Xbox, Playstation to visualise the correct button names.
Auto (this is the default):
Detects if a CD32 joypad is plugged in.
Uses the Joypad scheme if found.
Uses the original scheme if not found.
Additional controls:
Pause: P on keyboard, or Play/Menu on a joypad.
Suicide: Escape on keyboard, or HOLD Play/Menu on a joypad.
Look Down:
If you enable this option, crouch for a second without shooting and the screen will scroll down and slightly ahead. This is useful in cases where you have to make blind jumps.
Gyro Jump:
If enabled, you can jump out of the gyroscope mode at any time, rather than only when on the ground.
