Dolphin, the GameCube and Wii emulator - Forums

So, i loaded up TP. I press A and B at the beginning, Then It trys to make a save file and locks up here.



I cant press any buttons or point at the screen. Half of time the remote disconnects also. I have new batteries in the remote though.

Is there anything I can do? Or can someone upload a new save file made right after this that I can put in the save folder?

Thanks in advance!

Settings?

Sorry about the late reply. Here are my settings.



I hope that's what you needed.

---

I'm not sure how to edit my post so I'll just have to double post. Sorry.

I've tried backends other than openGL, all of them actually. That's just the setting that runs the majority of the games faster.

(02-14-2012, 12:53 PM)d8mien Wrote: [ -> ]I'm not sure how to edit my post so I'll just have to double post. Sorry.

Can't till you have 10 posts

Ah, ok that's why. lol.

YAY, finally fixed it.

HOW?! How did you fix it?? I'm having the exact same problem and this is the only thread I can find anywhere that addresses it. And just when I think I've found some help, you close your own thread by saying you "fixed it" but without uttering any details as to how. Did you stop to consider that these threads appear in search results and other people might need to know what worked for you?

All I can tell from this thread is that it can be fixed, somehow. Thanks for nothing.

---

Bleh sorry it's just a pet peeve of mine when people do this. It's very inconsiderate.

Anyway, could somebody please help me with this?! His settings look about right so assuming my settings are all the same, how do I go about fixing this?

---

(02-16-2012, 05:17 AM)d8mien Wrote: [ -> ]YAY, finally fixed it.

(12-19-2012, 03:56 PM)sirkris Wrote: [ -> ]HOW?! How did you fix it?? I'm having the exact same problem and this is the only thread I can find anywhere that addresses it. And just when I think I've found some help, you close your own thread by saying you "fixed it" but without uttering any details as to how. Did you stop to consider that these threads appear in search results and other people might need to know what worked for you?

All I can tell from this thread is that it can be fixed, somehow. Thanks for nothing.

---

Bleh sorry it's just a pet peeve of mine when people do this. It's very inconsiderate.

Anyway, could somebody please help me with this?! His settings look about right so assuming my settings are all the same, how do I go about fixing this?

I just tried using an emulated wiimote instead of my real wiimode. Works perfectly through the title screen, but then when it gets to the "checking save file" part, it freezes up again, same as with the real remote. So we can rule-out a problem with the remote/bluetooth itself. Any ideas? Would it be better if I created a new topic for this?

---

Just tried it on the latest Dolphin build. Same issue.

The remote is still synced. I can make it vibrate by clicking refresh while the game just sits there telling me to press A without touching the control stick. Virtual remote doesn't get recognized, either. I think this is a bug.

---

Up until then, though, the controls work perfectly. I even get the sword clashing sound through the remote's speakers when I hit A/B to start the game. But immediately after that, when it asks me if I want to create a new save file, the emulator no longer recognizes any inputs, whatsoever. After several seconds, the remote sync lost message comes up and it's just stuck there indefinitely.

I've finally managed to figure out a workaround! Unless the OP, I'll take a moment to share the answer here lol.

Due to what is certainly some kind of bug in Dolphin, the game will think that the wiimote lost sync immediately after the title screen, even though the remote is still perfectly synced and vibrates if you click refresh.

To get around this, you'll need to manually "reconnect" the remote by hitting [Alt]+[F5] on your keyboard. If you're using an earlier revision or the stable release, you'll need to do this twice (once to "disconnect" the remote and once again to "connect" it). After that, the remote will work perfectly.


Is there an open bug ticket for this? If not, there needs to be.

Actually this happens in a lot of games (could mention several). Never experienced this with Zelda TP though