Emulator

What do you mean by "don't work"? Is what you mentioned in that forum post ("everytime i start to fire up Hoth it hangs after the cutscene") the only problem?

Normally i can play, now after the cutscene it hangs and freeze up dolphin. This issue is present from build 4.0-5450 to 4.0-5456. Since the translation respect the CPU translation mode got added

Right click the game in the game list, hit properties, and go to the info tab. Next to "MD5 Hash", there's a button - compute. Press it and paste the results here please.

Why do you need a hash of my game ? it's dolphin that has a issue. It played fine before and i finished the game completely in dolphin. The new builds have a issue since this one got added in master

https://github.com/dolphin-emu/dolphin/pull/1856

Sometimes bad dumps stop working because of changes that make the emulator more accurate. Please post the MD5 so we can be sure that the disc image isn't the problem.

Like i said i finished this game twice completely on earlier builds and never had issues with HOTH. Now since the CPU translation mode got added it has issues. If i look in that thread https://github.com/dolphin-emu/dolphin/pull/1856 something was forgotten to add.

My iso is perfectly fine and is not a bad dump!. I played hoth 30 times if not more in dolphin because its 1 of my favorite maps in that game.

Ah look someone confirmed it

https://forums.dolphin-emu.org/Thread-gc-star-wars-rogue-squadron-ii-rogue-leader?pid=359996#pid359996

It doesn't matter how many times you played through it, it could still be a bad dump. If you are so confident the iso is fine, please provide the md5 hash for it and that will prove it?

Prove what ? i don't see any reason why a md5 hash could give you any information about a good or bad dump.

Why don't you give me a md5 string so i could see if it matches ?

Thanks for confirming.

Took me 30 seconds, we implemented MD5 checksum calculation in dolphin for a reason.

Next time refusing the instructions of a project member could result in your issue being invalidated until instructions are followed. It saves us time to eliminate possibilities like that. I know it may seem unrelated, but really, it does help, and we implemented MD5 checking in Dolphin for a reason.

Case and point - a DVD timing change broke Super Mario Sunshine for me a while back, and I reported it as a regression. Turns out my dump of Super Mario Sunshine was bad even though I had completed the game several times in dolphin.

I don't think there's a reason to ask for MD5 before anyone even reproduce it. And if MD5 turns out to be different you're going to invalidate it anyway, right? :)

Not really. There are tons of times where there's a bad MD5, but it ends up not mattering. We just ask for the user to redump. I ran into that case in Super Mario Sunshine as well.

Not really. There are tons of times where there's a bad MD5, but it ends up not mattering. We just ask for the user to redump. I ran into that case in Super Mario Sunshine as well.

Newer build not fixed either

dolphin-master-4.0-5458-x64
dolphin-master-4.0-5460-x64
dolphin-master-4.0-5462-x64

You can try this Pull Request - https://github.com/dolphin-emu/dolphin/pull/2040

This isn't a regression, as much as the removal of a hack that was making it work.

Thanks it's fixed :D