Hi guys, I'm trying to decide on which controller to get, either a Wii U Pro Controller or a Dualshock 4, and I just want to clarify a couple of things before deciding.
I'm going to use it for PC gaming, mainly emulators. I have skimmed over both the Wii U Pro Controller threads so please correct me if I'm wrong.
1. You need to have a Wii U, you have to pair the controller to the console first before pairing it to the PC. (I don't own a Wii U by the way)
2. If paired successfully, the buttons work welll, but the analog still has issues.
3. There's only a slim chance that the Wii U Pro controller will work outright as a PC gamepad without the need for the Toshiba Bluetooth stack or some kind of hack. (Nintendo has no plans on releasing drivers?)
Hope you guys can help, thanks in advance.
Actually, it's more like this:
1. You
may have problem connecting the controller, and in that case you
may need a WiiU. You may not have any problems, and if you do, there is also an alternate fix involving button mashing that usually works. Only if you're really unlucky will you need WiiU.
2. Again, it's only a problem for some people. As far as I have seen, it seems to mostly happen with windows 8 users. And if you look through the past 2-3 pages, you'll see that many manage to resolve the issue by fiddling a bit with the different vJoy devices. (As for me, it works perfectly. I'm using Win7.)
3. Nope, no chance. There's a slim chance for wiimotes+, and a larger chance (I think) for normal wiimotes, but the WUPC will never work. You
need the Toshiba Stack. And no, technically this whole thing is a hack - the WUPC was never intended for use with a PC, so unless Nintendo suddenly decides to change its mind there's practically no chance of the drivers being released.
Edit: By the way, AFAIK the problem is not in the lack of drivers, but in the way the WUPC sends signals through BT, which just doesn't work with the default Windows bluetooth stack. And as far as I understand, that's how the windows stack works, and no program or driver can get around it, which is why you have to install a whole different stack.