Emulator

I've known about this for a while. I thought there was already an issue report? Oh well, very much confirmed.

Wii Motion Plus users (before -TR) are screwed by this. -TRs don't seem to have this issue though, at least, I haven't run into it with my -TR.

I'm getting mixed results when I try to reproduce the problem. I know that the Motion+ recognition isn't all that stable, but I first thought it was because of my 3rd party Motion+. Then I got 3 genuine Nintendo Wii remotes (no -TR) and 3 genuine Motion+ units. Now the black Wiimote works with Zelda:SS every time, and usually I don't even get to see the Connect motion + -screen, sometimes it stays for 1-3 seconds. The other 2 Wiimotes give the same result as mentioned in the issue, but even then it's sufficient to turn off the wiimote and press 1+2 again, no need to physically disconnect the motion +. So for me this problem isn't that consistent. I have Windows 8.1, Microsoft BT stack, A-data BT dongle, and 3 wiimotes (White, Black, Pink) and 3 motion + units (2x black, 1x white).

Please remember that just because it's a Wiimote Plus does not necessarily mean it is a RVL-CNT-01-TR.

@MaJoRoesch: For clarification, all of my Nintendo Wiimotes are units without motion plus, I only have those 3x M+ accesories (Nintendo brand). So they are non -TR for sure.
And now that I started trying out, I actually managed to connect also my Pink and White remotes (&m+accessory) with Zelda:SS "normally", meaning that I press 1+2 when I see the "bootscreen" (or how should the Wii remote warning screen be referred to..?), wait for it to connect (takes about 10 seconds for me). It first takes me to "connect motion + and nunchuc" screen, but after 1-4 seconds it starts succesfully the calibration. I was tapping on A-button while connecting, feels like it makes the initial connection more likely to succeed. Might be just a feeling, though.
But still, normal Wiimotes, normal M+ accessories and nunchucks, connection with basic Microsoft stack without m+/nunchuck dis-/reconnect. Controverses the issue somewhat.

This is a widespread issue; it's not at all controversial. Some wiimotes may or may not be more susceptible to it on certain bluetooth stacks. I've tried on DolphinBar, Microsoft, and Toshiba and been able to reproduce the issues on various builds of Dolphin. White Wiimotes seem to have it happen every time. My blue Wiimote doesn't always screw it up, though.

And when the M+ connection still fails for me sometimes (maybe 33%?), the M+ disconnect / reconnect is the fastest way around, not turning the wiimote off, and sure this bugs me when I need to do this, so I don't mind this being in the issue tracker.
btw, during connection I try to be as close to the bt dongle as possible, somehow I believe that this initial connection is maybe the most sensitive part of the whole bluetooth connection.

Just did a little testing. The issue doesn't seem to appear in the Toshiba Stack for my Non -TR (regular) wiimote. But this same wiimote suffered from this problem quite a bit when I played through skyward on this wiimote with the MS bluetooth stack.

For whatever it is worth, it's black.

I have a old Wii Remote Plus (a non -TR one) and it's working. Sometimes Motion Plus isn't detected but generally hitting Alt+F5 twice fixes that for me. I'll try to reproduce this behaviour again, maybe I find something new...

It's not happening to me any more, but I feel like it's more a fluke than anything.

Issue 7032 has been merged into this issue.

Rename.

Issue 7466 has been merged into this issue.

Follwing issue should be merged to this one: https://code.google.com/p/dolphin-emu/issues/detail?id=7466&q=motion

Also, it's still happening for me, everytime. As soon as the motion+ is detected, it stays that way, even when doing another sport. But it's a pain to always have to disconnect (actually I need to press Alt+F5 twice for the disconnect to really happen), plug in the nunchuk, reconnect, disconnect the nunchuk.
I have an old normal wiimote together with seperate motion+.

Thanks for merging. So its a common problem.

Issue 7839 has been merged into this issue.

Issue 7839 has been merged into this issue.

i've tested on 4.0-4107-x64 and 3.5-2450-x64,

RTZK01 (Korean Region)

Toshiba Stack & Dolphin Bar with RVL-CNT-01(MotionPlus intergrated Black Color Model) & RVL-CNT-01-TR(MotionPlus intergrated White Color Model, TR revision).

as conclude, RTZK01 is not pass that MP attach message screen in any versions beside Last 3.5.x ~ latest 4.0.x

but i remember at least 2years before, (maybe 3.0.x versions?)
it's passed that screen and working fine. (i'd playing bowling with mother :D)

i haven't test other region's Wii Sports Resort but i think maybe it seems could be easily fix.

I too am having this issue. on 4.0-5110, mayflash sensor, and RVL-WR/F-C3 and RVL-WR/M-C0.

Same problem with Sports Resort on Mac OS X / Dolphin 4. I have original Nintendo MotionPlus Inside controller. I can not pass the motionplus screen

Bump to this issue.
Whats happening to me is that whenever i attach the motion plus accessory the cursor freeze and cant move any more. I had been able to use the same sensor in a motion plus version of dolphin that i found on the internet but i would like to use the last build since its more stable and has a lot of cool features like auto detect the wiimotes.

So i really want this feature to go working again so i do some research. The last Working build for me was 3.5.2368. The next build just next to that one is 3.5.2381 and from there does not work any more.

So in conclusion the change that broke this feature must be right in the 3.5.2381 changes. Hope this help guys! I really want to use dolphin 4.x with this working :D

yeap, it pass on 3.5-2368
TR seems fine too.

thx for andres.
:D

I have a RVL-036 and it works randomly for me. Skyward sword is completely random, and in wii sports resort, it seems to work with efb2ram and not work with efb2tex. So i think this might be performance or sync related?

Confirm Pass on 4.0-6803
maybe it fixed?

Hey guys, i have an RVL-003 and this is still happening in both builds, 4.0-6803 as the new stable build 4.0-6848. So the issue is still happening at least with the RVL-003

I have the normal wiimote & motion+ and it's still the same issue here... I still need to connect the nunchuk, then disconnect and reconnect for it to find the motion+.

I suspect this is caused by us assuming we can duplicate any wiimote input report to maintain 200hz. Same as issue #10111.