Dolphin, the GameCube and Wii emulator - Forums

Full Version: Graphics randomly gone wild
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
The one on the far right is the folder you mentioned. Can you see what i've done wrong?
Having unnecessary folders in the folder where the Dolphin executable is is wrong, but it doesn't cause any problems. I don't see why this wouldn't be working, unless you did something like deleting the save files from the Dolphin Emulator folder in My Documents.
Could it possibly have something to do with the way I run the game on dolphin? I don't remember why this became a problem but months ago when i first got Dolphin, i wasn't able to add Melee to my game library. I have to go through some lengthy process and ended with my resolution of right clicking my Melee file and clicking Open With Dolphin
That sounds incredibly unlikely.
As long as i didn't delete anything in the process of updating, why should my save file be so hard to find
@NeonShadowz: In Dolphin Folder where you have the Dolphin.exe, delete everything but what you see here:

[Image: sfXdkPI.png]

Then, in the Dolphin Emulator folder in Documents, in the Config folder, delete the "Dolphin.ini" file, and then re-run Dolphin. Next, click the Browse button, and navigate to where you have your game file is saved, and it should now show back up.
What this does is clear any old file path settings, and reset where Dolphin is looking for your memory card to the global directory.
Is this the ini one you referred to
Yes. I'd suggest making a backup of it in case you want it back, though.
I was able to follow all of the steps except for browsing the game. I'm going to the exact folder location that is on my desktop where i can see the game, but it's not in the options to select.
(09-06-2015, 01:52 AM)JosJuice Wrote: [ -> ]Are you launching Dolphin with the Steam overlay enabled or something like that?
I've had this happen once when I ran a game through Steam after a driver update. It somehow fixed itself with more driver updates but is there any way I'd be able to fix it manually in the future?
Pages: 1 2 3