Real Wiimote disconnects at startup (since rev 7271)

gunmoule · 06-11-2011, 02:58 AM #1

Well I recently tested the long awaited rev 7559 from Skidau. Tried it, ticking the DisableWiimoteSpeaker in Gameini. But no luck, I still have the same problem. Wiimote conected and paired, recognized by dolphin (showing 1 wiimote paired and vibrating). But when I launch a Wii game (I own RE4 and Link Crossbow Training) I can see Wiimote connected in the main window, but nothing is responding (cant press A, move cursor...).

In LCT it happens the Wiimote respond a few seconds (time to press A and skip the safety screen, but when it comes to the main menu, it stops responding, and dolphin main window shows No wiimote connected)

In Resident Evil 4, it's not responding at all, even at safety screen, but dolphin main window still display "Wiimote connected"

No related Console or Log entries

Got this problem on every rev since 7271 (the last working one i found at mamarios). With 7271 and earlier everything is fine, so its not wiimote or bluetooth related...
Im using x64 revs on Win7, with a decent config. Ticking the option to disable wiimote speaker doesn't solve the problem in recent revs.

Is it a known issue, or shall I open a new one with more details ?

onsterion · 06-11-2011, 11:52 AM #2

With the rev 7120 my wii mote and sensor bar work perfect, but with the last rev 7590 work tooo bad.

Why :S?

gunmoule · (This post was last modified: 06-11-2011, 09:51 PM by gunmoule.)

Nice to see I'm not the only one having this problem. The thing I don't understand is I wrote a very clear message about an emulation issue and people prefers trolling @Wifi connect emulation thread or Wii U emulator guy.

If youre okay I will open an issue at Dolphin SVN, and hope this finally gets the interest of a dev.

07-28-2011, 02:37 AM #4

I also am experiencing this issue. I would continue to run 7271, but when I go to widescreen from 640x480, it expands off the screen. Do you know how to get around this? Did you write a SVN? Has any prgress been made to fix. It doesn't appear many others have this issue. Coul we be using the same dongle(IO Gear) and that is the problem?