Wii u pro controller as xbox controller on windows 10 with built-in bluetooth device instructions january 2016 first and foremost, i did not make this software. From pcgamingwiki, the wiki about fixing pc games this page is a stub, it lacks content and/or basic article components. Dolphin’s Official GameCube Controller Adapter for Wii U has far the most stable driver build. They release regular updates and feature step-by-step installation guides for every major platform that is supported (including Windows, MacOS, Linux and Android). So if you used a different guide to set up your Wii U USB GCN Adapter, use this guide.

Wii U Gamecube Controller Adapter Driver For Windows
Wii U Controller Driver For Windows 7
Wii U Controller Driver For Windows 7 32 Bit

How to use it?

To use Nintendo Wii Remotes, or any compatible device, on linux, you need:

So I want to use my Wii U Pro Controller on the PC since my older XBOX 360 Controller has 'sticky buttons' and it's really irritating. Also the Pro Controller feels really good. I watched multiple tutorials and guides but none of them helped me. I always ended up with a disconnection after 1 second or nothing working.
Earlier there were intructions on getting your Wii U Pro controller as a gamepad. However, these instructions were inadequate for people with either Windows 8, built-in Bluetooth, or both.
Wirelessly connects your Wii u pro controllers to your pc by usb. Bluetooth v2.1 with EDR (enhanced data rate) for superior wireless performance. Supports turbo or auto fire function. Supports the built-in vibration feedback with no delays. New & Used (3) from $13.48 FREE Shipping on orders over $25.00 shipped by Amazon.

linux kernel 3.1 or newer (3.11 or newer recommended)
bluez-4.101 or newer (bluez-5.0 or newer recommended)

The kernel driver is available since linux-3.1 upstream. However, you need at least linux-3.11 for a hotplug-capable driver and proper device support. Older versions of the kernel driver are no longer recommended (still supported, but may lack important features). Most major distributions provide toose kernels out-of-the-box with the hid-wiimote driver enabled. But you might have to call modprobe hid-wiimote to load the driver manually.
The bluez bluetooth stack is the official linux bluetooth stack which is provided by all major distributions. Since version 4.101 it includes fixes so Nintendo devices can be paired with linux hosts. If you use an older bluez version, you may still be able to use Nintendo Wii / Wii U devices, but you cannot pair them.

Once you made sure you have the required software installed, you can start a bluetooth-manager of your choice (eg., blueman, gnome-bluetooth) and perform a bluetooth inquiry (ie., search for nearby devices). Your remotes will show up as Nintendo RVL-CNT-01 (Revolution was the codename of the Nintendo Wii) or with slightly modified names (eg., the balance board shows up as Nintendo RVL-WBC-01). Select a device and connect to it. If you use a new enough bluez version, it will automatically select the correct PIN. If you are prompted for PIN input, your bluez stack is too old. In this case simply select 'Connect without PIN' or 'Connect without Pairing' as you cannot enter the required PIN via these interfaces.

If you connected a device, the hid-wiimote kernel driver will pick it up and provide kernel input interfaces for it. As these interfaces are pretty useless on its own, you need a user-space application or driver that uses the device. The kernel interfaces provide the parsed data input (eg., accelerometer data, IR cam positioning information, ...) but do not apply any policy. So if you want to use your device to emulate mouse-input, you need a user-space driver which does exactly that. There is no sane generic way how X11 or other applications could use this data, as it is very device specific.
The xwiimote tools provide a library and some programs to help application-developers use Nintendo Wii / Wii U remotes. It is highly recommended to install the xwiimote-package before using a device. It will install some X11 blacklists so your X-Server will not pick up those devices by default. It also provides a tool called xwiishow, which can be used for testing.

From this point on, there are several ways to use the device:

Use xwiishow for testing
Install xf86-input-xwiimote to make X11 use the device as input device
Use the device with an application that supports xwiimote

Official GameCube Controller Adapter for Wii U

As of 4.0-4599, Dolphin has built in support for the Nintendo GameCube controller Adapter for Wii U, the only official USB GameCube adapter available. With Dolphin's implementation, the GameCube controller is auto-configured and calibrated, with full rumble support. Wireless controllers and bongos are supported.

This method of connecting controllers is intended to work with all adapters that are compatible with Super Smash Bros. for Wii U, but certain third-party adapters don't seem to work with this method. Adapters by Nintendo and Mayflash are known to work.

Compatible third-party adapters generally have a switch for choosing between PC mode and Wii U mode. If your adapter has such a switch, you have to set it to Wii U mode before following these instructions. Official Nintendo adapters don't have a switch.

1Installation
- 1.2macOS
- 1.3Windows
- 1.4Android
2Dolphin Setup

Linux

Linux support does not require any special drivers, as long as Dolphin was built with libusb support. However, a udev rule must be created to allow access to the device.

Paste the following in the /etc/udev/rules.d/51-gcadapter.rules file (/lib/udev/rules.d/51-gcadapter.rules if making a package):

SUBSYSTEM'usb', ENV{DEVTYPE}'usb_device', ATTRS{idVendor}'057e', ATTRS{idProduct}'0337', MODE='0666'

Reload udev rules with:sudo udevadm control --reload-rules

Then re-insert the adapter. Dolphin should now detect it in the controller settings (refer to #Dolphin Setup below).

If you want to change the rule, links for instructions are available on the libusb FAQ.

macOS

Due to the nature of Apple's HID implementation, all HID devices (including non-standard ones) are intercepted by IOKit's HID driver. Since the adapter does not supply a valid report descriptor, this makes the IOKit driver useless for direct communication.

Instead, IOKit's behavior may be manipulated via a codeless .kext to simply ignore the adapter and permit a lower-level connection (like the one Dolphin makes):

Easy Install

Terminal Install

Once installed, Dolphin should be able to recognize that the adapter has been plugged in. You do not need to configure the controllers manually within Dolphin's controller settings but any controllers plugged into the adapter should work immediately.

For questions on any of these macOS connection techniques, please see the forum thread.

macOS with System Integrity Protection (SIP)

On El Capitan (10.11) and later, the unsigned Kernel Extension will fail to load.The only current workaround is to disable kernel-extension signing verification, which can be done in macOS Recovery Mode.This will lessen security, and is not recommended.

See this StackExchange thread for more details.

Windows

On Windows, the GameCube controller adapter will need a certain driver to let Dolphin detect it and use it. If you are using 5.0-2472 or newer, you need to either install a filter driver using Zadig or install UsbDk. (Doing both is unnecessary, but doesn't lead to any problems.) If you aren't sure which one to pick, use Zadig. If you are using 5.0-2341 or older, using Zadig is required.

Avoid vJoy

The software that utilizes vJoy drivers, such as GameCube USB Adapter Driver, can treat the GameCube controllers as generic gamepads for Windows. They can be configured in Dolphin like any other controller. Unlike vJoy, Dolphin's native support will offer more straightforward a

Wii U Controller Driver For Windows