Emulator

Try using cached interpreter/interpreter instead of JIT. I don't have this game and can't test it at the moment.

If none of that works, then we can go from there.

Okay i will try that, i just tested 4.0.2 Dolphin and game runs correct no problems

thanks

I tested out cached interpreter still same bug.

I would like to pinpoint it but i would have to test so many builds it would take forever

should i just test every 20 or so back until i find one that works then test forward until it stops? i think that's the best way i can do it right?

Thanks

https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds

Try this

Fog wrote:

https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds

Try this

4.0-6974 Works
4.0-6976 Does not, this is the problem
https://dolphin-emu.org/download/dev/7b7d1b0dcf6801eb508877c0b180b82caa20b729/

it could be 4.0-6975 but i can't find that one

hi. I wrote that tool. yeah the tool might give you a bogus build as the "breaking build" sometimes. Just have to look around for the closest one. Generally if you give us like, 2-3 build range we'll pretty much be able to tell immediately which one would be the cause.

"before the door make a save state, opening the door will cause the bug again but when you load the save state the game works correct also if you boot the game and load the save state game will work correct."

This seems kind of scary. Savestates shouldn't be changing the timing.

Savestates mess up a lot of things.

magumagu9 wrote:

"before the door make a save state, opening the door will cause the bug again but when you load the save state the game works correct also if you boot the game and load the save state game will work correct."

This seems kind of scary. Savestates shouldn't be changing the timing.

no idea, reason i saved state is because i had no idea why it was hanging so i was testing out all the settings like dual core, different CPU emulation engines etc

and makes no sense that i can load a save game and if i try load a 2nd time it hangs

Another Game i found hanging at loading screens

Scooby-Doo! Unmasked G5DE78

Starting a New game asks you to make a save when you do create one it will say save successful and you have to press A to continue once you do it hangs on loading screen, on top of the screen you can see Dolphin yellow info that a save was created.

Again making a save state on the save successful screen makes the game load correct when loading the save state, also rebooting the game and loading the created save from memory card works.

If you don't have any Scooby-Doo! Unmasked saves on memory card when you create one it will hang on loading screen and you can see Dolphin created the save at loading screen, if then you boot the game again and start new game, make another save below the old one the game will load and Dolphins save yellow text appears after loading screen.

I don't know if this information is needed for you guys

Can you try setting fast disc speed on that game too?

Fog wrote:

Can you try setting fast disc speed on that game too?

Fast Disc Speed fixes this issue as well.

it does? i am 100% it did not for me it was one of the first things i tried.

Its the setting in option on the game right? you make the check box blank ?

i will test it

Fog wrote:

Fog wrote:

Can you try setting fast disc speed on that game too?

Fast Disc Speed fixes this issue as well.

yea i just tested that does not work for me

You click the box twice and you'll see a checkmark

Fog wrote:

You click the box twice and you'll see a checkmark

yes you are correct, sorry i misunderstood i thought that the little black box meant it was ON but i see the check box has 3 options.

Thanks this works on latest build

I've set SUDTR for both games in https://github.com/dolphin-emu/dolphin/pull/3852

@JosJuice: Build 5.0-2431 (and later to the current build) still exhibits endless memory error loops when attempting to load saved games from the main menu. I am forced to use save states just to play. In addition, the load screens when moving from one area to another occasionally (not always as before) will also still get caught in these endless memory error loops.

I looked into this about 5 months ago and talked about it in #dolphin-dev, but I guess I never wrote it up here. It seems this is icache-related.

Here are some logs, one with normal behavior and one with sped up disc transfer rate. These are from Dolphin 5.0-11333.

This change seems to fix the issue, by disabling the existing icache emulation. If I recall correctly, things also worked fine in uncached interpreter; my guess is that this is related to JIT caching causing the emulated icache to not get invalidated properly. The patch does still seem to work (I can, at least, get into and out of the credits, which wasn't possible before), though it causes issues with the GC IPL (possibly related to #11503).