Wiimote disconnect + 360 analog sticks

[Darius Freeman]

I've been unable to play any game with either the real wiimote or 360 controller effectively since again getting Dolphin yesterday. I'm using 3.5-1545; every game I tried to play tells me the wiimote has lost connection, alt+f5 occasionally reestablishes connection for 2 seconds before it's lost again. I am using the same setup that worked on older builds many months ago and "enable speaker data" does not fix it.

On the other hand I use a wired 360 controller (XBCD) as GC and classic controllers but both analog sticks are very off-center. Setting a higher deadzone stopped the game moving by itself but it's still very hard to play. This issue is unique to Dolphin.

[ron975]

I had this problem as well earlier, the wiimote problem, haven't tested the XInput controller problem yet. I even thought it was a problem with my BT adapter, spent an hour reinstalling the drivers, to no help.

I went back a few revisions, and it works, so I started going up. Turns out the bug is present in builds 3.5-1526 (Merge branch 'JP-wiimote-savestate-fixes') and later. 3.5-1522 works fine. I tested with 2 Wii remotes, and interestingly, Dolphin will pick up the second Wii remote, which the Home Menu, and Brawl, which I tested with, shows up as Wii Remote 1. However, the first wii remote, as determined by bottom LEDs, won't pick up at all. If you Alt-F5, it'll connect for a second or two, then disconnect again.

I'm on Windows 7 x64, using the x64 builds, my BT adapter is an Atheros based ASUS BT211, GPU is a HD7770 with 1GB VRAM @ 1GHz, CPU is an i5-2500K @ stock 3.3GHz speeds, and I used continuous Wiimote scanning to connect my remotes.

Use 3.5-1522 if you have this problem. Something in the JP-wiimote-savestate-fixes branch broke it

[Darius Freeman]

(06-29-2013, 10:46 AM)ron975 Wrote: I had this problem as well earlier, the wiimote problem, haven't tested the XInput controller problem yet. I even thought it was a problem with my BT adapter, spent an hour reinstalling the drivers, to no help.

I went back a few revisions, and it works, so I started going up. Turns out the bug is present in builds 3.5-1526 (Merge branch 'JP-wiimote-savestate-fixes') and later. 3.5-1522 works fine. I tested with 2 Wii remotes, and interestingly, Dolphin will pick up the second Wii remote, which the Home Menu, and Brawl, which I tested with, shows up as Wii Remote 1. However, the first wii remote, as determined by bottom LEDs, won't pick up at all. If you Alt-F5, it'll connect for a second or two, then disconnect again.

I'm on Windows 7 x64, using the x64 builds, my BT adapter is an Atheros based ASUS BT211, GPU is a HD7770 with 1GB VRAM @ 1GHz, CPU is an i5-2500K @ stock 3.3GHz speeds, and I used continuous Wiimote scanning to connect my remotes.

Use 3.5-1522 if you have this problem. Something in the JP-wiimote-savestate-fixes branch broke it.

XBCD driver gives DInput functionality to 360 controllers, it's recognized as DInput by dolphin and pretty much everything else. I tested 1522 and it worked to an extent (so thanks for that! ). The only games available to me right now are Sonic Colors and SMG2; Sonic Colors still did not detect a wiimote and instead forced me to the GC controller option. SMG2 worked right away but when I got to the gameplay mario kept moving left on his own, although this did not happen after restarting dolphin.

It all seems so unstable at the moment, I need to test more games. Very few people seem to have this issue, if this was a widespread issue there would be a whole lot more threads about it.

[Scootaloo]

(06-29-2013, 11:52 AM)Darius Freeman Wrote:

(06-29-2013, 10:46 AM)ron975 Wrote: I had this problem as well earlier, the wiimote problem, haven't tested the XInput controller problem yet. I even thought it was a problem with my BT adapter, spent an hour reinstalling the drivers, to no help.

I went back a few revisions, and it works, so I started going up. Turns out the bug is present in builds 3.5-1526 (Merge branch 'JP-wiimote-savestate-fixes') and later. 3.5-1522 works fine. I tested with 2 Wii remotes, and interestingly, Dolphin will pick up the second Wii remote, which the Home Menu, and Brawl, which I tested with, shows up as Wii Remote 1. However, the first wii remote, as determined by bottom LEDs, won't pick up at all. If you Alt-F5, it'll connect for a second or two, then disconnect again.

I'm on Windows 7 x64, using the x64 builds, my BT adapter is an Atheros based ASUS BT211, GPU is a HD7770 with 1GB VRAM @ 1GHz, CPU is an i5-2500K @ stock 3.3GHz speeds, and I used continuous Wiimote scanning to connect my remotes.

Use 3.5-1522 if you have this problem. Something in the JP-wiimote-savestate-fixes branch broke it.

XBCD driver gives DInput functionality to 360 controllers, it's recognized as DInput by dolphin and pretty much everything else. I tested 1522 and it worked to an extent (so thanks for that! ). The only games available to me right now are Sonic Colors and SMG2; Sonic Colors still did not detect a wiimote and instead forced me to the GC controller option. SMG2 worked right away but when I got to the gameplay mario kept moving left on his own, although this did not happen after restarting dolphin.

It all seems so unstable at the moment, I need to test more games. Very few people seem to have this issue, if this was a widespread issue there would be a whole lot more threads about it.

It'll be fixed sooner or later so I wouldn't worry too much .

[pauldacheez]

Dolphin supports XInput too, I dunno why y'all need to use XBCD.

(Note that I'm not a Windows user, nor do I have a 360 'pad, so take this statement with a grain of amphetamine salts.)

[ExtremeDude2]

I use my xbox 360 controller (wired) all the time in dolphin

[Darius Freeman]

I like having direct control over what button does what, specifically the triggers. Some emulators/games don't support Xinput either.