Wii Remote (old rev) not working in dolphin (but e.g. GlovePie)

[Malmodir]

Hi there,

I have problems using the wii remote with dolphin. It connects, it rumbles when discovered, but in game it seems to get constantly disconnected. While HotD2 can be reconnected for a few seconds (alt+f5), Zelda does nothing (and won't show the overlay/state in status bar). I already searched the forum here for advises, but I'm kind of lost. Some information here might not be relevant, but I'll try giving as much details as I can.

A few details:

• Windows 8 Pro x64
• 3$ bluetooth dongle (some usb sublicence of Microelectronics)
• First-party wii remote (Nintendo RVL-CNT-01)
• Stacks I tried: System-supplied MS stack, Toshiba (8.00.03 Premium Edition)
• Dolphin versions: 3.0, 3.5-599
• Games I dumped: House of the Dead 2, Zelda Twilight Princess
• No sensor bar (the connection and buttons should still work, shouldn't they?)
  

Other considerations:

• A few people recommended using some alternate timing, but I can't find that option (right-clicking where?)
• I used GlovePie before and it works well, even mapping the remote to the keyboard and the keyboard to an emulated remote. Can't map the accelerator right atm.
• Tried the MSDN HID Sample and the button reports show up. Since I don't know if the input reports generally don't operate normally or I mismatch the format, other data reports can't be activated. (http://code.msdn.microsoft.com/windowshardware/HClient-HID-Sample-4ec99697)
• Browsing your code it seems you operate on a rather low level with L2CAP. This is the most obvious difference to the other projects interfacing HID.
• A continuous discovery will somehow disconnect all surrounding wifi devices (handy, laptop). Also had this issue when working with RFCOMM winsock if the timeout was too high. I expect frequency hopping to cause interference, although the problem seems not being widespread...
  

Any suggestions appreciated. Thanks.


Edit:
Sorry, someone posted a similar thread this morning. The behavior mentioned is the same with me playing HotD2 although 20 minutes is 19m55s longer than my remote stays available. Zelda just reacts to the return button on my keyboard although real wiimote is selected. http://forums.dolphin-emu.org/Thread-intermittent-controller

[admin89]

Quote:right-clicking where?

Right-click the game (that show in Dolphin) - properties - tick "alternate wiimote timing"
It should look like this

[Malmodir]

Sorry, this took some time. I had a friend lend me a few games. There really was no option for alternate timing and this is not caused by my lazy eyes, but I solved my problem which I initially caused.

If anyone is interested:

It seems that my wifi interfered with the bluetooth adapter. My Dell XPS has a revision with inbuilt bluetooth, which I did not buy. Firmware thought, the dongle was native, used custom Intel drivers and screwed up some packets for the L2CAP routing. Don't ask me why. Fortunately, this is a minor issue because I downgraded my bios to A06 (to reduce fan noise), an update to A10 seemed to help.

This also solved the wifi disconnecting while discovering bluetooth devices. The frequency hopping reached the one of my wifi channel, so the Intel firmware couldn't distinguish wifi from bt and actually became a non-working access point for surrounding devices. Had to browse my system's and handy's logs to find that out. At some time, I really considered some strange ghost-karma-thingy happening....