Which builder (mamario, orlenas etc.) and arhitecture did you used?
Which OS?
Which stack?
Of course. I am using Mamario's builds. (Should be highly trusted obviously), and Windows 7 64bit Ult., and the 64bit version. And microsoft stack for blue tooth drivers.
And for others, please also note which OS, 32bit or 64bit (i believe i'm already seeing mixed OS versions having this issue, 32bit AND 64bit.)
So far, 2 people have PM'd me today also confirming this fix working for them. So far, so good.
I wish i could pm you and say its working. I guess i will have to continue digging.
But any way, since controller works fine in recording, there is no doubt that problem is on doplhin side. And maybe your and mine problems are connected.
just wanted to state that its not working for me as well. the wiimote rumbles when i click "pair up wiimotes", but other than that: nothing, no buttons or analog stick movements(classic controller). im going to check out 5105 now. i hope this fixes it.
p.s. test both x64 & x32 5222 on win7 64bit
I have the same problem, buttons not working anymore with my Wiimote (knock off). For the record the last working build I've tried was 5021. The latest build I've tried is 5240 which has this bug.
I also want to say that the default ms stack didn't worked with my wiimote, so I've used bluesoleil and it works without problems (up to 5021). In fact, this was the only reason for me to buy bluesoleil. Please check this issue since I'm stuck with this build (5021) now and I can't upgrade my dolphin. Thanx.
PD: I will try intermediate builds as soon as I can to help identifying the svn that caused this bug.
EDIT: I forgot to mention that, as other users with the same behavior, the Wiimote gets connected (via Bluesoleil in my case) and Dolphin sees it as paired, and it vibrates on "refresh real wiimotes".
I was notified on the issue tracker that this should likely be fixed in SVN Rev. 5237. I have been away from home a lot lately and haven't tried, but i would believe it's fixed in any revision above 5237 from what it said.
5237 is fix for black screen in some games as far as i can read. There are some patches for wiimote, but only IR sensitivity and auto reconnect.
Anyway, i hope fix is there even if i can't find it
EDIT: My bad i just read in comments that 5237 also fixes wiimote.
Well, I've tried 5271 and was showing same behavior, buttons not being recognized ingame. However, after recording a few movements, all problems were gone. So, maybe this could help someone with similar problems.
EDIT1: I posted too soon, this problem is intermittent, sometimes it works sometimes it doesn't. The strangest thing is that Dolphin sometimes gets to see the movementes in the "recording" section, all sensors are working. But even then, when a game is started buttons are not working.
Anybody else with this issues?? I'm sure original wiimotes don't have this problem or the forum would be flooded with this, but knock-offs were working fine before, and now I can't upgrade my Dolphin because of this.
EDIT2: After trying a few things I've noted that this issue maybe related to the new "auto reconnect wiimote" feature. Enabling auto reconnect seems to solve this problem, at least so far. I'll post more issues on this subject when I do more research
Hi!
I'm having the same issue. Sometimes wiimote works (in-game) and sometimes don't.
Dolphin pairs wiimote correctly every time (i'm using bluesoleil), and it shakes every time for check,. Going into recording, wiimote works correctly but not always (i'm using the original wiimote).
Tried with RC1 and other previous svn.
Using WiinRemote to test input from wiimote, all seems to work correctly (all inputs received). So I think it's definitely a dolphin problem.
Are you enabling "auto reconnect wiimote" in config as I suggested? It's working for me this way now.
I'm using 5289 BTW, I havent tried RC1 but you should try the latest SVN and report.