Emulator

MD5 HASH: cc8f92066bb30f1716e77148d99d8202

Is this issue present in 5.0-10912 (which just was released a few minutes ago)?

pokechu22 wrote:

Is this issue present in 5.0-10912 (which just was released a few minutes ago)?

im not sure, it wont let me load a save state as its incompatible with that version, and in the main save(saved through the game) im already ahead of that part, is there a way i can get that save-state to load

No.

Using savestates for testing bugs is not recommended anyway, as the issue can be baked into the savestate even if later builds have the bug fixed.

JMC4789 wrote:

Using savestates for testing bugs is not recommended anyway, as the issue can be baked into the savestate even if later builds have the bug fixed.

yeah, i wanted to continue playing so i just kept going and made a save-state right before krazoa palace, figuring i could just load it back for testing later.
Is there anything else you want/need me todo?

If you can't reproduce the issue and don't have a regular savefile nor a way to make one, there's not much point of keeping this open besides documentation for the next person who plays through. Hopefully if it still happens, they'll report it.

This seems like it can happen on real hardware too. See this Let's Play: https://youtu.be/jhQyLkkjr-Y?t=1790

Maybe disc timing related?

Well that made this a lot more interesting.

How do you know that's on the actual GameCube?
I've played the OG GameCube one a few times and I've never had it happen.

OG GameCube has the slowest disc drive. Newer GCs, White Wiis, and especially late wiis have faster disc drives.

I checked with the LPer and they're using a modded WiiU to play the game. So it's not exactly real hardware, but closer than what Dolphin is, so, uh, no idea what that means for us. Might be worth experimenting with anyway.

I would not trust Nintendont for verifying any DTK related behavior. It should be fine if it's purely a DSP thing, but I'm assuming that's not the case here. (This game does use DTK for all the dialogue, right?)

That's fair. I believe the dialogue in this game is DTK, yes.

Nintendont seems to make the same mistake as the one I fixed earlier of resetting the current position when stopping the stream: StreamEndStream resets StreamCurrent to 0, and their implementation of command 0xE1 will return 0 if the stream is stopped or such.

Entergroot: It might be possible for you to test the behavior if you load your save state, and then update dolphin and load the actual save file. I'm not sure 100% if save states include the save file or not though, but this is possibly a way to test. (It would probably be worthwhile to also check if the issue reproduces on 5.0-10910 when doing that, though; it might be something more tricky that is consistent from a savestate but doesn't always happen when loading from an actual save.)

Savestates don't include the memory card contents, but it may or may not be possible to create a new memory card save after loading the savestate.

pokechu22 wrote:

Nintendont seems to make the same mistake as the one I fixed earlier of resetting the current position when stopping the stream: StreamEndStream resets StreamCurrent to 0, and their implementation of command 0xE1 will return 0 if the stream is stopped or such.

Entergroot: It might be possible for you to test the behavior if you load your save state, and then update dolphin and load the actual save file. I'm not sure 100% if save states include the save file or not though, but this is possibly a way to test. (It would probably be worthwhile to also check if the issue reproduces on 5.0-10910 when doing that, though; it might be something more tricky that is consistent from a savestate but doesn't always happen when loading from an actual save.)

yeah it doesnt let me, as it says "This is not the memory card with which you began the game, Game cannot be saved"

Do you have the BIOS enabled? If the "Config > GameCube > Skip Main Menu" box is not checked, check it and try.
Some games have issues with this, Starfox Adventures is one of them, and displays the same exact behavior you're describing.

This was discussed in https://bugs.dolphin-emu.org/issues/10956#note-13. They are not using the IPL, and the issue that only happens when using the IPL is supposed to be fixed nowadays.