Emulator Issues #7444
Wii Remote extensions are not detected properly with MotionPlus and Emulated Bluetooth
Wii Sports Resort - RTZE01
Skyward Sword - SOUE01
Likely other Wiimotion+ games.
What's the problem? Describe what went wrong in few words.
Sorry about the long name, but that's as simple as it gets. What happens is that if you're using a motion+ adapter, you can simply plug it in after booting the game, and everything's fine. This is a bit strange though, as the real Wii doesn't not require this massaging to work.
Things get worse for the those with Motion+ build in Wiimotes. They do not have the option to plug in the Wiimotion+ after boot. What those users have to do is plug in ANOTHER peripheral, then unplug it to get the Wiimotion+ to be detected. It's rather annoying.
What did you expect to happen instead?
I expected it to work properly. Has this question ever been useful? I'm just wondering.
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
1. Start a Wiimotion+ game with the Wiimotion already plugged in.
2. Navigate to a point where it won't let you past without Wiimotion in.
3. It won't let you past.
4. Either unplug and plug back in the Wiimotion plus, or use a nunchuck or something on a Wiimotion+ Wiimote.
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-1981, 4.0, 3.5; various others I've played Wiisports resort for recreation.
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
No; I swear this was working at one point. but even when I went back to 3.5 I was having this issue.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Core i5 3570K at 3.4 GHz, GTX 760, Radeon HD5850, Windows 7. Using Toshiba Stack, and in 3.5 I used the DolphinBar.
Accepting immediately because this is a widespread issue.
#2 Updated by hosode over 5 years ago
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).
#4 Updated by hosode over 5 years ago
@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.
#5 Updated by JMC4789 over 5 years ago
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.
#6 Updated by hosode over 5 years ago
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.
#7 Updated by MayImilae over 5 years ago
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.
#14 Updated by mwernerxy about 5 years ago
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+.
#19 Updated by hong620 about 5 years ago
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.
#22 Updated by andresmcalandri over 4 years ago
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