 |
Working fine when I test it in WinUAE. Do you know which version of the game you're using? |
 |
Hello - it's the single disk version. I've just been doing some testing myself and I created my HD file using Winuae then wrote it to an SD card for use with pistorm. The game works from the HDF file on Winuae but using the same HDF file with pistorm lrads to these issues. However, there are no issues if I boot from the floppy version of the game whilst using pistorm. I wonder if it's an issue with the whdload and pistorm in combination. |
|
|
Sorry should also have said its SPS0019. |
|
|
I'm not familiar with Pistorm to be able to say why that is the case. Could it be something run during Workbench startup that is not run when booting directly from disk? Have you experienced any other WHDL games failing to read joystick/pad controls? |
|
|
Hi - thanks for the suggestions. I haven't found any other WHDL games that fail to read the joystick (yet). Through trial and error I found that by adding the nocache tooltype the issue is resolved. Not sure why I don't get this problem when booting from floppy but the game is now playable via WHDload now. |
|
|
That's interesting to know - thanks. |
|
|
As I suspected, there is self modifying code in this game that happens when the batarang is used. I'm surprised it has never been noticed before but that's probably because the code doesn't sit in the cache on 040/060 CPUs, but does on Pistorm (which I assume has a bigger cache). I will continue investigating further. |
|
|
I have a fix for this now - 3 different instances of self-modifying code, in both level 1 and 5. I am adding support for 2 more versions of the game so I have other work to do, but I should have a fix out soon. |
|
|
v1.6 now released that should fix this bug. |
- Anonymous
