Congratulations on finishing the game! 🙂 I tested again the final version, but unfortunately I was not able to complete it as planned, as there seems to be a bug in the 5th world (level 13) that even occurred in the latest version at the time of our livestream. I had to skip the world completely to avoid ending up in the workbench again. This happened with both the WHDLoad and the regular version. You can see the bug in our video below at 04:18:15. There are also some problems in the form of "hanging" inside objects like stairs. Our German-language review starts at 03:47:45. English subtitles are also available.
11 hours ago (+1)
Edit: I noticed that you are not playing the latest version. Latest version (January 26) features that instruction text at the bottom of the options menu, like in the picture below. I'm still adding things and fixes (check last paragraph in this post).
I wasn't able to reproduce your issue, it simply doesn't happen with me (check this video, same situation as you, I tried to force the crash).
It may be low chipRAM. Even if your Workbench says "1,800,000" of chip, it isn't always true (as memory gets corrupted due to Wb apps loaded and other stuff). I would suggested to please test the vanilla CastlevaniaAGA_January2025.lha on a higher chipRAM situation: hold both mouse buttons on boot, boot with no startup, then Work: (or equivalent name of the partition) >> cd CastlevaniaAGA >> game-crunched.exe
AGA games launched from Workbench are always at risk, even with WHDLoad. Remember that back in the day, Super Stardust AGA had a boot-disk? That's the reason! A similar crash happened a while ago on AmigaBill's stream, and after that, he always used boot with no startup method (just to make sure). And since that, it always worked without problems.
It might be other incompatibility related to hardware. I would like to know what is your hardware (specially accelerator model and the KS ROM on the Amiga).
Regarding complete version, in technical terms, the game is BETA, which means that the game is feature complete, i.e., all features and content scheduled for release are in the game, including the full CD soundtrack on CD32. However, as a BETA the game is largely untested and thus has issues that need to be fixed (like what you experienced). This is why companies will do in-house betas, limited release/private betas, and public betas as their games become more solid on the way to full release. To be precise, the A1200/A4000 version is slightly behind beta because its .MOD soundtrack is still not fully complete. Hopefully, all will be finished in time for Amiga's 40th anniversary celebrations.
Thanks for playing, live streaming it and reporting! :)
I updated the original version from February 20th (at the time of preparation for the broadcast) to the latest version during the livestream after two failed attempts. Funnily enough, the version was updated during our stream, so that the version from the last attempt was only 45 minutes old, see position 04:32:53. Unfortunately, this didn't help and I couldn't use the CD32 version because the trainer didn't work (keys didn't work during the game). I will definitely take another look at the game later and adjust my rating accordingly. It is and remains a damn good and technically very high-quality game. And sometimes a livestream like ours can be very helpful for troubleshooting, as our example shows. It would not be the first time that another update follows shortly afterwards. 🙂
The game was tested with WinUAE 5.2.0 (not the most recent version, as this apparently contains changes and a few small errors in sound playback). This runs with a realistic, cycle-accurate A1200 standard configuration with HDD, Kickstart 3.1, 2 MB Chip- and 8 MB Fast-RAM without a turbo card in order to simulate the most realistic setting as possible. The color palette under the Workbench (OS 3.1) was set to 256 colors by default, which requires a bit more Chip RAM and there are actually games like "Bunnito's Feast" that need more to start. However, based on previous knowledge, it was not to be expected that the error would also occur during gameplay.
Edit: The bug also occurs in the (now) current version from 26.2., even with the color palette reduced to 2 colors under OS 3.1. To be on the safe side, it was tested again with the current WinUAE 5.3.1, and as expected, there were no differences. I would be happy to send you my WinUAE configuration that causes the problem so that you can troubleshoot it. If you are interested, just send me an email using our contact form: https://www.radio-paralax.de/kontakt/