Pokemon Hearth 0.1.27, constant crash

[TwinTusks]

Per title, was playing Pokemon Hearth version 0.1.27 and experience constant crash with the error "bad jump" when going into double battle, learning new moves, or even enter a new area.

The issue persists in FrogGBA, I suspect it might be due to memory issue? But strangely, Pokemon Heart and Soul runs pretty much fine (with a bit of stuttering) and they had way more overworld pokemons.

[andymcca]

The 'bad jump' message is triggered by a translation error on a block, this could be an emulator bug or a ROM hack bug - gpsp forks like this are more susceptible to the latter than real hardware or the likes of mgba/nano boy etc.

I'll try and debug this based on your report when I get the chance.

[andymcca]

I've also seen this error reported due to a bad or corrupted sd card, so that's a possibility as well especially if you're using a PSP1000 which can't store the whole gamepak in ram. Can you try with an original Memory Stick if you have one?

I've played the first 15 mins and haven't seen a crash yet? Do you have a save file and can you give me a concrete place where it crashes?

[TwinTusks]

I bought the PSP (3000) second hand, I just checked the memory card seem be original Memory Stick (no adapter).

The crash is randomly triggered, for example exiting pokemon center would trigger the crash one time, but after restart, it won't. After testing, renaming the pokemon after catching it would also trigger the crash after pressing "confirm", if you switch the pokemon in your lineup, it will trigger the crash when you next encounter or enter a new area but it might not trigger for you. However the most constant crash currently is when entering the double battle.

See below save file, just when you enter cut scene with the Crobat Shadow team, they'll double battle you, the game always crashes when "JUST" before the two zubats came out.

https://limewire.com/d/33q2c#013sqDNaRL

(Sorry for an alternative download link, github can't seems to upload .sav files)

Thank you for looking into this

[andymcca]

Hey @TwinTusks , thanks for the save file, I have downloaded it. Could you do me a favour please and 1) record the full 'Bad Jump' message including the two hex addresses it gives you and let me know what it is (if it varies that's good too, just need to know what they are) and 2) can you try changing the mode in Emulator Options from 'Partial + Reuse' to 'Full Flush' and seeing if you still get the crash?

[TwinTusks]

Hey @TwinTusks , thanks for the save file, I have downloaded it. Could you do me a favour please and 1) record the full 'Bad Jump' message including the two hex addresses it gives you and let me know what it is (if it varies that's good too, just need to know what they are) and 2) can you try changing the mode in Emulator Options from 'Partial + Reuse' to 'Full Flush' and seeing if you still get the crash?

Thank You Andy.

I tried to record the full sequence in video, but you know what, when I turn to record the double battle with the Crobat Shadow team, expecting it crash, the two zubats actually came out ... I beat them and everything is normal (LOL). Just when I needed them eh. So you have to make do with the image of other crashes (had several, but hard to capture as it disappeared when I grab my phone and open camera. The numbers are random.

The crashes are all while the "mode" in emulator options as "Partial+Reuse", I will try "Full Flush" now and see if it makes any difference.

Again, thank you~

Update:

After playing for several hours straight, there's no more crash when emulator mode on "Full Flush", I will continue to test if it's a full solution or just I'm getting lucky.

[andymcca]

Thanks very much for the update! OK so in the meantime I've used the 'bad jump' info you posted above to investigate, it looks like a register corruption or timing issue which matches the random occurrence that you see. Is the number in brackets (03000190) always the same? That number is a valid IWRAM address which is the program counter for the game at the time of the crash - the reason for the crash is that it's trying to jump to the other address to continue execution, but it is a garbage value (i.e. should be a valid GBA memory address and it definitely isn't!).

It's likely a corner-case bug in TempGBA where the registers get corrupted at a certain point - tricky to trace back to the exact issue, I expect that if I get to the point of just going on general bug fixing it will get fixed as a by-product! Good to hear you've had success using Full Flush, I'll leave the issue open though as its symptomatic of a problem that still needs fixing.

[TwinTusks]

The numbers in the bracket are not the same everytime.

[andymcca]

@TwinTusks the Heart & Soul test release may fix this issue as well, if you could put the emulator back into Partial Flush + reuse and test for crashes pls?