Emulator Issues #6031
closed
Dolphin recognizing Wii U Pro controller as wiimote, d/cing it
0%
Description
Have you searched the issue tracker for a similar issue?
yes
What went wrong?
using texhaxor69 and daku93's pro controller connector, a wii u pro controller was connected. Nintendo RVL-CNT-01-UC.
If at any point, dolphin searches for a wii remote, it finds the pro controller and disconnects it.
the idea was to use a pro controller keybound to dolphin's GC controller.
What did you expect to happen?
to ignore the pro controller completely and only connect the wii remotes
What steps will reproduce the problem?
1.install toshiba bluetooth stack
2.download both 1.2 and 1.3 of this tool:
http://gbatemp.net/threads/wii-u-pro-controller-to-pc-program-release.343159/
3.connect pro controller with BT
4.open v1.2
5.open v1.3
6.close v1.2
7.connect wii remote
8.open dolphin
9.set 1(or multiple) real wii remote(s)
10.launch game
11.controller will disconnect
What version of Dolphin were you using?
dolphin 3.5, compiled Dec. 24, 2012, at 21:11:27
64 or 32 bit Dolphin?
64-bit.
What Operating System were you using and what are your hardware
specifications?
Windows 8,
ISSCBTA bluetooth adapter,
Nintendo RVL-CNT-01-UC
64 or 32 bit Operating system?
64-bit.
Any other relevant information or links to logs:
pro connector v1.2 and v1.3:
http://gbatemp.net/threads/wii-u-pro-controller-to-pc-program-release.343159/
Toshiba BT stack:
http://aps2.toshiba-tro.de/bluetooth/index.php?page=download-toshiba
Updated by parlane almost 12 years ago
- Status changed from New to Accepted
I believe this is due to our search for matching strings starting with RVL-CNT-01 or something close. We will need to add an exception for RVL-CNT-01-UC I believe.
Updated by Billiard26 almost 12 years ago
- Status changed from Accepted to Work started
We actually attempt to connect to any available HID device and use it as a wiimote on Windows. (ya rly, wtf)
The "RVL-CNT-" name handling is only for connecting new bluetooth devices. (MS BT only)
This might be "fixed" in the "real-wiimote-scanning" branch which no longer opens the wiimote device with the FILE_SHARE_WRITE flag.
Updated by Billiard26 almost 12 years ago
willthingy, will you confirm this is fixed in real-wiimote-scanning?
http://dolphin-emu.org/download/list/real-wiimote-scanning/1/
Updated by Billiard26 almost 12 years ago
Is this issue resolved by r46adbfa9ede116aaed876ecf1d3a21002e399910 (latest master)?
Updated by Billiard26 almost 12 years ago
The potential fix had to be undone to fix other things.
Telling me if the issue is present in r11e4403fb245 would still be useful, however..
Updated by tueidj almost 12 years ago
I would guess that the actual disconnection is caused by trying to read the pro controller's eeprom memory - although it communicates the same as a wiimote it doesn't support reading/writing to the eeprom and will instantly disconnect if such a command is received.
(This is likely by design - for some reason the pro controller is stored in SYSCONF for the wiiU's virtual wii mode, so wii games do actually accept connections from the controller but it disconnects when they try to read the calibration data.)
Updated by willthingy almost 12 years ago
sorry for the delay, i don't check my google email nor visit here often.
the problem is fixed in 3.5-430(dunno how early it was fixed), i must be using an old version of dolphin(again, compiled in december)
Updated by willthingy almost 12 years ago
nevermind, thats just because 3.5-430 has broken wiimote connectivity. i'll test around the different versions on that page and report back.
but i dont have visual studio, or any builder or frameworks on this computer, and i probably wont be able to compile the latest sources for another 3 weeks.
Updated by Billiard26 almost 12 years ago
@ willthingy
Downloads here!
http://dolphin-emu.org/download/list/real-wiimote-scanning/1/
Just tell me if the problem is resolved in the latest of that branch.
Updated by willthingy almost 12 years ago
I cannot tell if the problem is resolved, as the latest of that branch breaks all wii remote connectivity over toshiba BT stack, not just the wupc. technically yes, since it cannot connect the wupc, but the toshiba stack is required for the wupc, which means all wii remotes must be connected over toshiba stack. which means wii remotes cannot work while the wupc is connected.
Updated by Billiard26 almost 12 years ago
OK, you are one of "those" people then. :p
It does work for some with the Toshiba stack.
Anyways, the solution is not trivial then.
Updated by Billiard26 almost 12 years ago
- Status changed from Work started to Fixed
This issue was closed by revision 059e1004259c.
Updated by Billiard26 over 11 years ago
- Issue type set to Bug
- Operating system Windows added
Updated by 
Updated by
Updated by samgattin about 10 years ago
I hate to bump this but I'm experiencing the same exact issues as above.
I'm using Dolphin 4.0 4071
To recreate the problem...
- Connect controller successfully to Bluetooth Stack.
- Open up WiiUProController.exe (v1.6) to verify I'm getting input.
- Open up dolphin.
- Successfully connect WiiU Pro Controller to dolphin.
- Open game and the controller completely disconnects from bluetooth.
Updated by willthingy almost 10 years ago
@ samgat
IIRC, There is a workaround to this problem: Run dolphin and connect any wii remotes first, and then use the WUPC program to connect the WUPCs afterwards.
This way, dolphin connects wii remotes first, and doesn't need to try to connect to the "fake wii remotes" after that.
Also, your
step 4. Successfully connect WiiU Pro Controller to dolphin.
shouldn't happen...
Updated by leoetlino about 8 years ago
This was probably fixed because Dolphin's real Wiimote code now explicitly checks the device name, which needs to be exactly equal to Nintendo RVL-CNT-01, or Nintendo RVL-CNT-01-TR (-TR Wiimotes), or Nintendo RVL-WBC-01 (Balance Board).
Updated by JosJuice about 8 years ago
- Status changed from Accepted to Fixed
I'm setting the status to Fixed, then. If this still is happening for anyone, please comment.
Updated by JMC4789 about 8 years ago
I'm not sure if this is fixed, invalid, or somewhere in between.
Updated by JosJuice about 8 years ago
- Status changed from Fixed to Questionable
Okay, let's put it as Questionable then.
Updated by JMC4789 about 8 years ago
My question: Why should Dolphin connect a Wii U Pro Controller???
Updated by leoetlino almost 7 years ago
- Status changed from Questionable to Fixed
It's fixed in the emulated BT path by whitelisting acceptable device names, and also "fixed" by Bluetooth passthrough mode with which behaviour is identical to a Wii, so there's nothing to fix.