Bluetooth Passthrough

Since, Dolphin has the ability to passthrough a Bluetooth adapter for emulated Wii software. This is a powerful option that allows for perfect Wii Remote behaviors on Dolphin, given a powerful enough Bluetooth adapter. Unlike standard Bluetooth emulation, Bluetooth Passthrough supports pairing third party Wii Remotes, Wii Remote audio, and can more accurately communicate fine motions. However, because Bluetooth Passthrough gives the Bluetooth adapter directly to the emulated software, there are heaps of limitations that make it only worthwhile for certain situations.

Limitations

 * Requires a specialized driver on Windows, and on Linux requires a udev rule. The Operating System will not be able to access the Bluetooth adapter while it is in use.
 * The functionality and stability of the connection heavily depends on the compatibility of the Bluetooth adapter used.
 * Even though most Bluetooth adapters can be used in passthrough mode, perfect compatibility is only guaranteed with the Bluetooth modules from Wii consoles.
 * Many features do not work. Netplay, input recordings will be limited.  The Wii Remote may disconnect if Dolphin is running too fast or too slow.  If the Bluetooth is disconnected from your computer, Dolphin may crash.
 * Save states made in Bluetooth Passthrough mode can't be loaded on "Emulate a BT Adapter" mode, nor vice-versa.
 * Wii Remote connection state dictates whether save states made in Bluetooth Passthrough mode will work or not:


 * {|class="wikitable"

! When saving state ! When loading state ! Works?
 * One or more Wii Remotes connected
 * One or more Wii Remotes connected on the same session[1]
 * bgcolor="#afa" | Yes
 * One or more Wii Remotes connected
 * One or more Wii Remotes connected on a different session[1]
 * bgcolor="#faa" | No
 * One or more Wii Remotes connected
 * Some or all Wii Remotes disconnected
 * bgcolor="#afa" | Yes[2]
 * No Wii Remotes connected
 * One or more Wii Remotes connected
 * bgcolor="#faa" | No
 * No Wii Remotes connected
 * No Wii Remotes connected
 * bgcolor="#afa" | Yes
 * }
 * No Wii Remotes connected
 * No Wii Remotes connected
 * bgcolor="#afa" | Yes
 * }
 * }


 * [1] Same session: for instances where Wii Remotes haven't been disconnected and emulation hasn't been stopped during anywhere between saving and loading of a save state. Different session: when any one of these has been intervened.
 * [2] First (re)connection will fail, subsequent connections will work. Depending of the Bluetooth adapter, it might be necessary to connect then disconnect the Wii Remotes before loading the saved state.

Linux
A udev rule has to be installed so Dolphin can use a Bluetooth adapter without having to get root privileges.

1. Paste the following into /etc/udev/rules.d/52-dolphin.rules (/lib/udev/rules.d/52-dolphin.rules if making a package). Replace 'YOURVID' and 'YOURPID' with the Vendor ID and Product ID respectively.

2. Reload udev rules with:

3. Reinsert the adapter.

Dolphin should be able to automatically unload the USB Bluetooth kernel module (assuming you have permission to; you typically need to be in the  group). If not, unload it with.

Windows
WARNING: While a libusb driver is installed, other programs/devices will not be able to use your Bluetooth device. This can be easily reverted in Windows Device Manager and instructions are provided below.

Download and open Zadig as Administrator, then:
 * 1) In the "Options" menu in Zadig, make sure "List All Devices" is enabled.
 * 2) Look through the devices for the radio to passthrough.
 * 3) On the right column, select "libusbK", then click "Replace Driver". Select "Yes" to modify the system driver.

If you wish to return your Bluetooth drivers back to normal, start "Device Manager" and locate "libusbK" devices in the list. Right-click the device you wish to restore and select 'Uninstall Device'. Upon plugging it in next time, Windows will install the default Bluetooth driver and it will resume normal functions. NOTE: If you used the winUSB driver instead, it will be located under "Universal Serial Bus Devices." Same instructions apply otherwise.

If Dolphin is unable to use your Bluetooth device after doing this, it may not have the necessary hardware features. You can attempt to use the "winUSB" driver from Zadig as a last ditch effort.

usbdk
As of usbdk is no longer supported.

Some users who wish to maintain use of their Bluetooth Device and use it in Dolphin without swapping drivers have opted to use usbdk. When Dolphin starts up, you will lose control of your Bluetooth Device and regain it when Dolphin shuts down. While this cuts down on the work you need to use your Bluetooth device across many controllers, usbdk has many bugs; the worst of which is that any ES_Launch will immediately crash/freeze the game due to usbdk losing control of the Bluetooth.

macOS
There is currently no way to use this feature on versions newer than 10.9, because Apple removed the ability to unload the Bluetooth kernel module.

A potential solution would be to force the OS to ignore the adapter with a codeless .kext, but this hasn't been tried yet.

Android
This feature is not supported on Android.

Using passthrough mode in Dolphin
In Dolphin, open the Controller Configuration dialog, then select the "Passthrough a Bluetooth adapter" option in the Wii Remotes section.

While a game is running:
 * Wii Remotes can be synced and paired to Dolphin by using the Sync button.
 * All saved Wii Remote pairings can be reset by using the Reset button. This will also disconnect all currently connected Wii Remotes.

Sync button hotkey
It is possible to use the "Press Sync Button" hotkey as an alternative to the buttons in the controller configuration dialog.

You will need to map "Press Sync Button" to a key or combination of keys. This can be done within Dolphin by left clicking on the "Hotkey Settings" tab under "Options" to bring up the appropriate configuration menu. You must then left click on the "Wii and Wii Remote" tab and left click on the box for "Press Sync Button" to map this hotkey.

"Press Sync Button" is designed to work just like the Wii's red sync button:
 * Pressing the hotkey will trigger a sync.
 * Holding the hotkey for 10 seconds will clear all saved pairings.

Forcing a specific adapter
If you need to use a specific adapter, instead of using the first Bluetooth adapter that is found, you can force Dolphin to use it by editing Dolphin's configuration file (Config/Dolphin.ini). In the BluetoothPassthrough section, set "VID" and "PID" to your adapter's vendor ID and product ID. These values should be converted from hex to decimal, for example a VID of "057E" should be inputted as "1406".

"Failed to open Bluetooth device: LIBUSB_ERROR_ACCESS"
This error means that Dolphin doesn't have permission to use the Bluetooth adapter.

If on Linux, make sure the udev rule is set up correctly.

"Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED"
On Windows, this typically means that the libusb/WinUSB driver was not installed for the adapter.

"Failed to detach kernel driver for BT passthrough"
Dolphin tried to automatically unload the Bluetooth USB kernel module and failed to. Unload the module manually before starting a game to avoid this issue.

Wii Remotes do not stay paired after closing the game
This means that your adapter is likely broken and does not remember Wii Remote link keys properly. Use a different adapter to avoid this issue.

This may also happen if your SYSCONF is corrupted or if you changed to a Dolphin version which doesn't have BT passthrough. If your adapter is listed as working with pairing or if you're sure it supports pairings (by having checked the HCI command replies), you can try deleting Wii/shared2/sys/SYSCONF and Wii/btdinf.bak.

Black screen on boot
Games send a reset command to the Bluetooth adapter when they start and wait for it to be acknowledged. If you are getting a black screen for a long time (more than 10 seconds), your adapter may be stuck in a broken state and is unable to respond to any commands. Unplug the adapter and try again.

No usable adapter found
This can happen with some adapters. You'll need to force your adapter to be used.

Adapter test results

 * Unknown. Not enough information to classify.
 * Incompatible. Does not work or has significant limitations.
 * Partially compatible. Works well in most cases, but there may be some issues.
 * Fully compatible. Works well in all cases and will give the same experience as a Wii Bluetooth adapter.

Stability
 * [1] May stop working after HCI resets (stopping, resetting emulation or going back to the system menu).
 * [2] Has issues with games which send a lot of commands (including New Super Mario Bros. Wii and The Legend of Zelda: Skyward Sword before you get in game).
 * [3] Starts having lag issues after ~30 minutes. Reconnecting the Wii remote is required.
 * [4] May stop working after HCI resets on Windows, works fine on Linux and macOS.
 * [5] Randomly stop working on Windows, works fine on Linux and macOS.
 * [6] Has issues connecting multiple Wii Remotes.

Pairing
 * [7] Has issues reconnecting multiple Wii Remotes.
 * [8] Remembers only one Wii Remote.

Other
 * [9] Doesn't expose its internal Bluetooth adapter, can't be used with Bluetooth Passthrough in any capacity.


 * [10] Must be modified before use, refer to this forum thread.
 * [11] CNVi card, must be paired with a compatible Intel CPU and chipset to work.
 * [12] Supported Bluetooth version may vary depending of the chipset model paired with this card.
 * [13] Proprietary 10-pin BTB connector, usually found in older laptops (2010 and earlier).
 * [14] This is the Bluetooth version supported out of the box (e.g. no drivers installed), can go as low as 4.0 and as high as 5.3, depending of the proprietary Realtek driver version installed.