Progress Continues
We've already had 21455 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: August, September, and October 2023 Progress Report.
User-info.png The Dolphin Emulator Wiki needs your help!
Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin.

Bluetooth Passthrough: Difference between revisions

Jump to navigation Jump to search

Bluetooth Passthrough (view source)

Revision as of 07:13, 19 October 2020

1,810 bytes added ,  19 October 2020
→‎Windows: Grammatical/sentence fixes
(→‎Adapter test results: convert audio column to ?/No/Limited/Yes, prefer commercial adapter name and list model number (if available) under parenthesis and add "WiFi Card" suffix to generic adapters where applicable)
(→‎Windows: Grammatical/sentence fixes)
(5 intermediate revisions by 3 users not shown)
Line 2: Line 2:


== Limitations ==
== Limitations ==
* The functionality and quality of the connections heavily depend on the quality of the adapter.
* The functionality and stability of the connection heavily depends on the compatibility of the Bluetooth adapter used.
* Even though most adapters work fine in passthrough mode, the only perfect adapter is the Wii's Bluetooth module (so far).
* Even though most Bluetooth adapters can be used in passthrough mode, perfect compatibility is only guaranteed with the Bluetooth modules from Wii consoles.
* Save states can be used with some limitations.
* When using Bluetooth Passthrough mode, the emulated software directly communicates with the Bluetooth adapter, so it's not possible to mix passthrough mode with emulated Wii Remotes and some Dolphin features like Netplay, TAS input, input display, among others, won't be available.
* Because Bluetooth Passthrough Mode skips Dolphin's emulated Bluetooth and Wii Remote code entirely, it is not possible to mix passthrough mode and emulated/real Wii Remote. This means that netplay, TAS input, input display, etc. cannot work.
* 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'''<sup>[[#SaveStateNotes|[1]]]</sup>
| bgcolor="#afa" | Yes
|-
| One or more Wii Remotes connected
| One or more Wii Remotes connected '''on a different session'''<sup>[[#SaveStateNotes|[1]]]</sup>
| bgcolor="#faa" | No
|-
| One or more Wii Remotes connected
| Some or all Wii Remotes disconnected
| bgcolor="#afa" | Yes<sup>[[#SaveStateNotes|[2]]]</sup>
|-
| No Wii Remotes connected
| One or more Wii Remotes connected
| bgcolor="#faa" | No
|-
| No Wii Remotes connected
| No Wii Remotes connected
| bgcolor="#afa" | Yes
|}
 
<div id="SaveStateNotes">
::<sup>[1]</sup> 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.<br/> Different session: when any one of these has been intervened.
::<sup>[2]</sup> 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.
</div>


== Setting up ==
== Setting up ==
Line 11: Line 43:
A udev rule has to be installed so Dolphin can use a Bluetooth adapter without having to get root privileges.
A udev rule has to be installed so Dolphin can use a Bluetooth adapter without having to get root privileges.


SUBSYSTEM=="usb", ATTRS{idVendor}=="YOURVID", ATTRS{idProduct}=="YOURPID", TAG+="uaccess"
'''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.
 
<code>SUBSYSTEM=="usb", ATTRS{idVendor}=="YOURVID", ATTRS{idProduct}=="YOURPID", TAG+="uaccess"</code>
 
'''2.''' Reload udev rules with:
<code>sudo udevadm control --reload-rules</code>
 
'''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 <code>plugdev</code> group). If not, unload it with <code>modprobe -r btusb</code>.
Dolphin should be able to automatically unload the USB Bluetooth kernel module (assuming you have permission to; you typically need to be in the <code>plugdev</code> group). If not, unload it with <code>modprobe -r btusb</code>.
Line 21: Line 60:
Download and open [http://zadig.akeo.ie/ Zadig] as Administrator, then:
Download and open [http://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 device to passthrough.
# Look through the devices for the radio to passthrough.
# On the right column, select "libusbk" or 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 back to normal, start "Device Manager" and locate "libusbK" devices in the list.  Right click the device you wish to restore and uninstall device.  Upon plugging it in next time, Windows will install the default Bluetooth driver and it will continue functioning per normal.  NOTE:  If you used the winUSB driver instead, it will be located under "Universal Serial Bus Devices." Same instructions apply otherwise.
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.
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 32: Line 71:
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.  When Dolphin starts up, you will lose control of your Bluetooth Device and regain it when Dolphin is shutdown.  While this cuts down on the work if 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.
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 ===
Retrieved from "https://wiki.dolphin-emu.org/index.php?title=Special:MobileDiff/170168...174389"

Navigation menu