15,190
edits
Bluetooth Passthrough: Difference between revisions
→Adapter test results: none of the CSR8510 based adapters tested so far showed different behavior on Linux/macOS, so I'm assuming user error here
(→Adapter test results: dropped all links since nearly all are broken or unavailable for purchase, added Realtek RTL8852AE to the list and updated RTL8761B adapters to "not working", explaining why and how they might work in future) |
(→Adapter test results: none of the CSR8510 based adapters tested so far showed different behavior on Linux/macOS, so I'm assuming user error here) |
||
| (12 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
Since {{revision|5.0-910}}, Dolphin has the ability to passthrough a Bluetooth adapter for emulated Wii software. | Since {{revision|5.0-910}}, 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 == | == Limitations == | ||
* Requires a specialized driver on Windows, and on Linux requires a udev rule. | * 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. | * 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. | * 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. | * 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. | * 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: | * Wii Remote connection state dictates whether save states made in Bluetooth Passthrough mode will work or not: | ||
| Line 57: | Line 57: | ||
=== Windows === | === Windows === | ||
WARNING: While a libusb driver is installed, other programs/devices will not be able to use your Bluetooth device. | 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 [ | Download and open [https://zadig.akeo.ie/ Zadig] as Administrator, then: | ||
# In the "Options" menu in Zadig, make sure "List All Devices" is enabled. | # In the "Options" menu in Zadig, make sure "List All Devices" is enabled. | ||
# Look through the devices for the radio to passthrough. | # Look through the devices for the radio to passthrough. | ||
# On the right column, select "libusbK", then click "Replace Driver". Select "Yes" to modify the system driver. | # 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. | 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. | If this does not revert your device driver, you may right click on the Bluetooth device in Device Manager, select "Update Driver", "Browse my computer for drivers", then select "Let me pick from a list of available drivers on my computer". From there, select "Generic Bluetooth Adapter". This should permanently revert your Bluetooth driver. | ||
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 ==== | ==== usbdk ==== | ||
| Line 72: | Line 74: | ||
As of {{revision|5.0-10617}} usbdk is no longer supported. | As of {{revision|5.0-10617}} 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. | 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 === | === macOS === | ||
| Line 384: | Line 386: | ||
| bgcolor="#afa" colspan="2" style="text-align: center;" | Yes | | bgcolor="#afa" colspan="2" style="text-align: center;" | Yes | ||
|- | |- | ||
| bgcolor="#fda" | | | bgcolor="#fda" | Orico BTA-408 [BCM20702] | ||
| USB || 4.0 | | USB || 4.0 | ||
| 0A5C || 21EC || ? | | 0A5C || 21EC || ? | ||
| Line 429: | Line 431: | ||
| ? | | ? | ||
|- | |- | ||
| bgcolor="# | | bgcolor="#fda" | Sena Networks Parani-UD100 [CSR8510] | ||
| USB || 4.0 | | USB || 4.0 | ||
| 0A12 || 0001 || 8241 | | 0A12 || 0001 || 8241 | ||
| bgcolor="#afa" colspan=" | | bgcolor="#afa" colspan="3" style="text-align: center;" | Yes | ||
| bgcolor="#fda" | Limited | |||
|- | |- | ||
| bgcolor="#fda" | Silicon Wave Bluetooth Wireless Adapter | | bgcolor="#fda" | Silicon Wave Bluetooth Wireless Adapter | ||
| Line 449: | Line 452: | ||
| ? | | ? | ||
| bgcolor="#afa" | Yes | | bgcolor="#afa" | Yes | ||
|- | |||
| bgcolor="#fda" | TP-Link Bluetooth 4.0 Nano USB Adapter (UB400) [CSR8510] | |||
| USB || 4.0 | |||
| 0A12 || 0001 || ? | |||
| bgcolor="#afa" colspan="3" style="text-align: center;" | Yes | |||
| bgcolor="#fda" | Limited | |||
|- | |||
| bgcolor="#faa" | TP-Link Bluetooth 5.0 Nano USB Adapter (UB500) [RTL8761B] | |||
| USB || 5.0 <sup>[[#Notes|[15]]]</sup> | |||
| 2357 || 0604 || ? | |||
| bgcolor="#faa" colspan="4" style="text-align: center;" | No <sup>[[#Notes|[9]]]</sup> | |||
|- | |- | ||
| Trendnet TBW-106UB [CSR8510] | | Trendnet TBW-106UB [CSR8510] | ||
| Line 477: | Line 491: | ||
| bgcolor="#fda" | Limited <sup>[[#Notes|[7]]]</sup> | | bgcolor="#fda" | Limited <sup>[[#Notes|[7]]]</sup> | ||
| bgcolor="#afa" | Yes | | bgcolor="#afa" | Yes | ||
|} | |} | ||