Emulator Issues #9900
closed
Non-TR remotes do not work on Windows 10 with the Dolphin Bar
0%
Description
What's the problem? Describe what went wrong.
All builds (4.0-8325+) after pull request 3245 (https://github.com/dolphin-emu/dolphin/pull/3245) fail to recognize my non-TR Wiimotes on Windows 10.
The build immediately before 4.0-8325 (4.0-8321) functions perfectly.
What steps will reproduce the problem?
Try running 4.0-8325 under Windows 10 (Version 1607/Anniversary, build 14393.447) with a Dolphin Bar.
Wiimotes function in other programs such as WiinRemote, but not Dolphin.
Try 4.0-8321, and Wiimotes will function perfectly.
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
Any build above 4.0-8325 fails to work. Any build below, including 4.0-8321, functions perfectly.
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10 Pro x64 1607 (Anniversary Update), build 14393.447
Intel 4790k
NVIDIA GTX 980
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Log output from the failed builds looks something like this:
02:46:796 HW\WiimoteReal\WiimoteReal.cpp:489 N[Wiimote]: Wiimote scanning has started.
02:46:796 HW\WiimoteReal\WiimoteReal.cpp:670 N[Wiimote]: WiimoteReal::Initialize
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000001
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000001
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000001
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:798 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:799 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
02:46:799 HW\WiimoteReal\IOWin.cpp:860 W[Wiimote]: IOWrite[WWM_WRITE_FILE]: Error on WriteFile: 00000057
Updated by neersighted over 7 years ago
I do not have any TR remotes to test with, all of mine are of 2006-2007 vintage and came with two separate Wiis.
Updated by JMC4789 over 7 years ago
That's happened to me with my Dolphin Bar occasionally, where it just fails to communicate to Wii Remotes. I don't know if -TR makes a difference since you said you couldn't test them.
You bisected though; so that helps a lot. I don't have jloehr on here to ping though.
Updated by neersighted over 7 years ago
It appears that a -TR Wiimote does not function either. I went out and purchased a 'Toad'-styled Wiimote today (with the Wii U branding on the box), and it shows similar behavior in the current dev build.
Updated by JMC4789 over 7 years ago
- Status changed from New to Questionable
This appears to be some kind of bug with the DolphinBar where it occasionally will decide to not connect Wii Remotes. I do not know of a solution, and I'm not sure whether the bug resides in Dolphin or the DolphinBar.
Mine is no longer functional so I can't provide further assistance.
Updated by neersighted over 7 years ago
I don't believe we are talking about the same bug. This bug is not intermittent but reliably reproducible, and only manifests on Dolphin versions newer than 4.0-8321. The DolphinBar (and I have tested three now) functions perfectly in lower builds.
Updated by mbc07 about 7 years ago
Well, I have two non-TR Wiimotes and they work fine through the Dolphin Bar in Mode 4 even on current development builds. I'm also on Windows 10, the only thing different from your setup is that I'm using the default MS BT stack instead of the Toshiba BT stack, if that makes a difference...
Updated by Billiard26 over 3 years ago
Is this issue still present in recent builds?
Updated by Billiard26 about 1 month ago
- Status changed from Questionable to Working as intended
Will re-open upon request.