(02-26-2018, 05:15 AM)DJBarry004 Wrote: It then got corrupted, probably. Redump it and try again.
According to http://www.gametdb.com/Wii/GXXE01 that is a correct hash for an NTSC-U dump. So no need to redump your game.
Your controller setup seems to be without any issues.
To find out what the issue is and to try and solve it please do the following:
1. Download the latest development version from the download page, you can find it if you scroll down a bit (as of 2018-02-26 this is the latest build: https://dl.dolphin-emu.org/builds/dolphin-master-5.0-6382-x64.7z)
2. Extract Dolphin to a new and empty folder
3. Create an empty text file called portable.txt in that same directory (this is to make sure that Dolphin uses all it Default settings)
4. Do not change ANY setting except for the controller set up.
5. Start your ORIGINAL UNMODIFIED version of Pokemon without ANY cheats enabled.
6. Start a NEW game and DO NOT EVER use ANY Savestates, only use the ingame memory card save function. Savestates are known to cause strange issues with Pokemon because of the anti-cheat / anti-duplicate code in the game crapping out.
If the error occurs again > Try disabling Dual-core and try again.
Is there still an issue? Then you have probably hit a regression in Dolphin and you might need to file a bug report so it can get fixed properly. You can file a bug here: https://bugs.dolphin-emu.org/projects/emulator/issues
Keep in mind to fill in the form correctly and fully when filing a bug report so it will/can get fixed as soon as possible. The most important thing to do here is to bisect in which version the problem started occurring by using the Bisect tool which you can find in this thread: https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds
Check my profile for up to date specs.