Emulator

willthingy, will you confirm this is fixed in real-wiimote-scanning?

http://dolphin-emu.org/download/list/real-wiimote-scanning/1/

Is this issue resolved by r46adbfa9ede116aaed876ecf1d3a21002e399910 (latest master)?

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..

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.)

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)

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.

@ 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.

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.

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.

Fix was reverted.

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...

1. Connect controller successfully to Bluetooth Stack.
2. Open up WiiUProController.exe (v1.6) to verify I'm getting input.
3. Open up dolphin.
4. Successfully connect WiiU Pro Controller to dolphin.
5. Open game and the controller completely disconnects from bluetooth.

@ 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...

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).

I'm not sure if this is fixed, invalid, or somewhere in between.

My question: Why should Dolphin connect a Wii U Pro Controller???