How Gamecube controlls works?

[Cheese Corn]

       I'm trying to play a Pokemon XD Hack Rom (Is that legal in this forum?I can edit if no.) but every time i try a battle it starts with C Stick, after i choose a move will work with Control Stick and later switches into D-Pad (I already tried to make all Controllers with ^v<> but only work if i press down together with the selected move button to hit someone  and after I receive literally more than 20 error mensages of invalid read/write .) 



Why nobody awnsers me ; ;? I'm checking for 12 hours and nothing

[mstreurman]

(02-24-2018, 10:08 PM)Cheese Corn Wrote:        I'm trying to play a Pokemon XD Hack Rom (Is that legal in this forum?I can edit if no.) but every time i try a battle it starts with C Stick, after i choose a move will work with Control Stick and later switches into D-Pad (I already tried to make all Controllers with ^v<> but only work if i press down together with the selected move button to hit someone  and after I receive literally more than 20 error mensages of invalid read/write .) 



Why nobody awnsers me ; ;? I'm checking for 12 hours and nothing

Does the Rom Hack work on a real Gamecube?

To solve the issue in Dolphin:
1. Try to turn off Cheats in Dolphin
2. Try to turn off Dual-core
If this doesn't help with the error messages try with your originally dumped iso file, if it does work on the original then the issue is with the hacked Pokemon XD iso. So you will have to reapply the hack to your original ISO file and try again, if it doesn't fix the issue you must contact the creator of the hack and see if he/she can fix it for you.

If using an originally dumped iso doesn't solve the issue please post the MD5-hash (right-click your game > Properties > Info > Generate MD5) and region of your original unchacked iso-dump here so we can check if it is a valid dump.

[MayImilae]

Please post a screenshot of your GameCube controller settings. Let's see if you have any controller configuration issues!

[Cheese Corn]

I tried http://prntscr.com/ijkhea and http://prntscr.com/ijkhxs controller settings (and the original) all failed, and the problem isn't with the hackrom because the original ISO also has the problem (MD5-hash 3bc1671806cf763a8712a5d398f62ad3 )

[DJBarry004]

It then got corrupted, probably. Redump it and try again.

[mstreurman]

(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

[Cheese Corn]

(02-26-2018, 05:05 PM)mstreurman Wrote: 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

Thanks, now only has a innonfensive problem, the sound is lagged and creepy... But now i can patch and start a New Game?

[mstreurman]

(02-27-2018, 03:10 AM)Cheese Corn Wrote: Thanks, now only has a innonfensive problem, the sound is lagged and creepy... But now i can patch and start a New Game?

The sound lagging and being creepy is probably happening because your CPU is too slow. Did you also turn off Dual Core because it caused the issue? if it didn't cause the issue you should be able to enable it again for a nice performance bump.

First: If you have speed issues ALWAYS make sure that ALL applications are closed: NO internet browsers, no music in the background, no nothing.

Try the following procedure:
1. If you haven't done so already download and extract the latest development version in a NEW folder *do not overwrite an existing installation*, you can find it if you scroll down a bit on the download page
2. Download and install the latest AMD Driver for your GPU (found here for Windows 10 https://www2.ati.com/drivers/beta/non-whql-win10-64bit-radeon-software-crimson-relive-16.2.1-sep20.exe or here for Windows 7/8.1 https://www2.ati.com/drivers/beta/non-whql-win8.1-win7-radeon-software-crimson-relive-16.2.1-sep20.exe)
3. Set up the Windows Power Options to "High Performance"
4. Make sure Dolphin is running at its Default settings (by deleting or renaming the Dolphin Emulator folder in "My Documents" or by creating a portable.txt in the same folder as Dolphin.exe)
5. In Dolphin set IR to 1x (Internal Resolution)
6. Set Ubershaders to Disabled (or off) *KEEP IN MIND THAT THIS WILL INTRODUCE SHADER STUTTERING, BUT THIS WILL GO AWAY WHILE PLAYING AS THE GAME BUILDS UP THE SHADER CACHE*
7. Set Graphics Back-end to D3D
8. Set Anti-Aliasing to 1x (or off)
9. Set Sound back-end to CubeB and HLE
10. Turn off Cheats
11. Do not use any Texture Packs
12. Run your game, is it still slow? Then your CPU is too slow to handle this specific game. You can try setting the emulated clockspeed to 90% or 75% (or even less) but keep in mind that there is a HUGE possibility that things will break spectacularly.

The game should always be running at 25/50FPS (PAL) or 30/60FPS (NTSC) or at 100% speed otherwise you will encounter slowdowns.
If it runs at 100% you can try increasing the IR to 2x and slowly increase the IR a single step at a time, but not higher than your native resolution, which is probably 1080p or 3x IR, if it goes below 100% speed at a higher IR at any time, go back one value.
If you've found the IR that your GPU can handle, you can slowly increase the Anti-aliasing step by step, if it goes below 100% speed at any time, go back one value.
Finally you can start increasing the Anisotropic Filtering, if it goes below 100% speed at any time, go back one value.
If you've done this, you have found the ultimate quality/speed settings for your computer to run this specific game.