forums.jaspp.org.uk

Mirror your *Configure settings exactly in Arculator, perhaps it's a combination of memory settings that's triggering an edge case? Check the Modules match up as well. The lockup after selecting the difficulty might be sound related, so also try turning it completely off in the options. Does running...

Idge wrote: ↑Thu Apr 11, 2024 4:41 pm Cheers Jon,
I will have a proper go at it at the weekend, but did quickly try the RMAFree 4 in the script, This actually gets the game to load without asking for the disk swap, however when you try and start a level, I get a lockup.

Try increasing it from 4; 256 for example.

Updated build in the OP with a few bug fixes for IOC / IOMD

I then just did a shift boot without the mode change or next change, and it still worked, so it now seems to be related to something in my boot. If you can pin it down and it's something I can fix in the script, I'll alter it. Things to check, off the top of my head: The size of the RMA and amount ...

I now get an SWI &103F10 not known error Now fixed. I meant to go back and completely rewrite the CPU / Cache detection, but forgot. I've not managed to produce the other errors you're seeing with the revised script - I've tested on 4MB ARM2 and 4MB ARM3 both with RISC OS 3.11. It does sound li...

It's a bug in the game code. It looks like its supposed to transition to black at the end of a level, then fade back up for the next, but its doing both in parallel. I suspect there's supposed to be a timer running whilst it fades out, before it goes to the next level to the fade back in. I've disab...

I've looked at the game code and can't see any obvious reason for the palette to go black. The palette swap code is all hanging off VSync, so does occur at the correct time...so it's more likely to be a bug in the game or possibly protection kicking in. Whilst investigating, I've back-ported the var...

It's an issue caused by WolfLoad. Instead of allocating the correct amount of memory for the game, it allocates all memory leaving none in the free pool. That causes RMA memory allocations to come from the end of application space, which triggers an abort the next time the User stack is touched by t...

Interestingly, &0001A3DC is *adfs:Dismount :0

I'm not sure why that would trigger an abort.

See if the attached recording file works. I quickly tested I could start a new level, but haven't played beyond that to see if I need to capture more sectors.

If it works for you, I'll add it to the ADFFS 2.84 public beta, which I need to update this week following a few bug fixes.