Emulator Issues #6049
closedWiimotes not detected after real-wiimote-scanning merge - device in use by other program
0%
Description
Have you searched the issue tracker for a similar issue?
Yes
What went wrong?
After manually connecting the wiimote, Dolphin fails to pick up the connection after clicking the "Refresh" button in Wiimote Settings.
What version of Dolphin were you using?
Dolphin 3.5 builds 471 and newer
64 or 32 bit Dolphin?
64 bit
What version of Dolphin used to work?
Dolphin 3.5 builds 409 through 432 (64 bit) work.
What Operating System were you using and what are your hardware
specifications?
Windows 7 Ultimate
Toshiba bluetooth stack v9.10.00(T)
IOGEAR GBU421 Bluetooth 2.1 USB Micro Adapter
64 or 32 bit Operating system?
64 bit
Any other relevant information or links to logs:
The Console logs don't display anything when clicking the Refresh button. I've tried both an older-model wiimote and one with MotionPlus built-in. I tried using the Dolphin versions in question on a virtual machine with the Microsoft stack, and the wiimotes paired fine there.
Updated by Billiard26 over 11 years ago
- Status changed from New to Questionable
- Issue type set to Bug
Please test 3.5-423 and 3.5-424 of the real-wiimote-scanning branch.
Does your wiimote work in either of those?
downloads: http://dolphin-emu.org/download/list/real-wiimote-scanning/1/
Updated by Heimddallr over 11 years ago
The wiimote pairs successfully on 3.5-423, but not on 3.5-424.
I went back to 3.5-477 and set the log config to Warning, then tried pairing again. It gave me this:
03:44:780 Src\HW\WiimoteReal\IOWin.cpp:424 W[Wiimote]: IOWrite[MSBT_STACK_MS]: ERROR: 00000001
03:44:780 Src\HW\WiimoteReal\IOWin.cpp:424 W[Wiimote]: IOWrite[MSBT_STACK_MS]: ERROR: 00000017
03:44:780 Src\HW\WiimoteReal\IOWin.cpp:424 W[Wiimote]: IOWrite[MSBT_STACK_MS]: ERROR: 00000017
03:44:780 Src\HW\WiimoteReal\IOWin.cpp:424 W[Wiimote]: IOWrite[MSBT_STACK_MS]: ERROR: 00000017
Updated by Billiard26 over 11 years ago
A significant change in 3.5-424 (which I assume is the problem change) is no longer opening the wiimote device for shared writing.
Toshiba stack does still work for other people.
Do you have any sort of utility running that might have the wiimote device open.
Some kind of hotkey program, another game, anything?
Updated by Heimddallr over 11 years ago
The only things I can think of are my Steam client and Parallel Port Joystick. I tried shutting both down and it still didn't work.
Think it might be the BT stack version I'm using?
Updated by Billiard26 over 11 years ago
I don't know, but I really don't want to revert that change because it probably fixes issue 6031.
Updated by Heimddallr over 11 years ago
Looks like the problem's located somewhere else. I went back to the Microsoft stack and it still won't work.
I'll have to figure out what's causing it. Thanks.
Updated by Billiard26 over 11 years ago
Yes, the issue would exist with MS Stack as well.
Fairly sure some program on your system is using the wiimote when it shouldn't be.
Updated by Billiard26 over 11 years ago
Issue 6055 has been merged into this issue.
Updated by daveyjc over 11 years ago
Support this! RVL-CNT-01 ain't working either with Toshiba stack since the merge. Reading comments seems that the merge has in fact almost broken real wiimote support.
Updated by guikubivan over 11 years ago
So I can kind of get around this if I first remove the bluetooth devices and then, while I have the Wiimote dialog open in Dolphin, I re-add the device and connect through Windows explorer. Then click the refresh button (then my wiimotes shake, etc.)
However, once in the game I seem to get the BSOD, though I've only tried with the already problematic Epic Mickey 2.
Updated by napala over 11 years ago
Mine too, after 424, i cant sync my wiimote anymore, old versions work fine, changed to mstack and same thing ocurs. Im using toshiba btstack with RVL-CNT-01-TR
Updated by daveyjc over 11 years ago
Don't understand why the status is questionable, when almost all of us are finding big problems. Not working is not questionable, it's quite objective.
Updated by scientificraver over 11 years ago
I fully agree. There is no reason to completely cutoff support for all modern real TR-Wiimotes just to implement a nearly useless new feature.
The Wiimote-scanning merge commit needs to be reverted and further development of Wiimote-scanning should happen in a separate branch until these major problems are fixed.
As you cannot buy older non-TR Wiimotes in stores anymore this change should get high priority.
Updated by hatarumoroboshi over 11 years ago
Bluesoleil doesn't work anymore as well
Updated by pauldacheez over 11 years ago
On OS X (10.7/10.8, two different Macs), connecting my remotes (two original remotes included with my Wii + one non-TR MotionPlus remote that came with Skyward Sword) is perfectly possible, but somehow input no longer works. Worked perfectly fine on the last rev of the branch, but somehow it stopped working right when it was merged (?!).
Updated by Anonymous over 11 years ago
The status is "questionable" because it's possible everyone with wiimote problems has a broken program on their system opening all HID devices. (broken Hotkey program, broken game, other)
Wiimotes still work for many, with all bluetooth stacks.
Updated by scientificraver over 11 years ago
There is a huge difference between standard and integrated Motionplus Wiimotes in the way they communicate, please refer to issue 5011. All TR-Wiimotes seem to be broken.
Updated by Billiard26 over 11 years ago
- Status changed from Questionable to Work started
@ scientificraver
That seems irrelevant? All wiimotes are affected by this issue.
(and the fix is known and I am going to push it in a second even though I don't want to, but I am such a nice guy :p)
Updated by Billiard26 over 11 years ago
Please confirm this is fixed by rcedfa452b4497590f828306b42b1e7c24915fd58.
Updated by scientificraver over 11 years ago
I don't want to test it, but I am such a nice guy too. It works, the TR-Wiimote now connects with Toshiba stack.
Updated by Billiard26 over 11 years ago
I didn't want to push it because it unfixes something else and shouldn't be needed.
I do want wiimotes fixed :p
Updated by daveyjc over 11 years ago
It's working now with Toshiba stack and RVL-CNT-01!
I wasn't previously getting the "device in use by other program" message. It just wasn't doing nothing when refreshed.
Thanks!
Updated by Billiard26 over 11 years ago
There was no "device in use by other program" message, it would simply not connect because the device cannot be opened when opened elsewhere.
Updated by Heimddallr over 11 years ago
It's now working for me with the Toshiba stack. Thanks very much :D
Updated by beaubois.florian over 11 years ago
Hello everyone, i'm having the exact same issue connecting my wiimote (classic with no motion plus) in dolphin using a trendnet 107ub dongle.
I tried the ms stack, bluesoleil and toshiba and had the same results.
I first searched here for people with the same problem and found this post, so i tried 3.5-423 and the wiimote connected and worked in game.
Any version above that and it won't connect.
I'm not sure if i have to create a newpost or not, thanks in advance if someone can help.