SUBSYSTEM="usb", ATTRS="YOURPID", TAG+="uaccess"ĭolphin should be able to automatically unload the USB Bluetooth kernel module (assuming you have permission to you typically need to be in the plugdev group). Replace 'YOURVID' and 'YOURPID' with the Vendor ID and Product ID respectively. Paste the following into /etc/udev/rules.d/les (/lib/udev/rules.d/les if making a package). Setting up LinuxĪ udev rule has to be installed so Dolphin can use a Bluetooth adapter without having to get root privileges.ġ. Depending of the Bluetooth adapter, it might be necessary to connect then disconnect the Wii Remotes before loading the saved state. First (re)connection will fail, subsequent connections will work. 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.ĭifferent session: when any one of these has been intervened. One or more Wii Remotes connected on a different session One or more Wii Remotes connected on the same session
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.Even though most Bluetooth adapters can be used in passthrough mode, perfect compatibility is only guaranteed with the Bluetooth modules from Wii consoles.The functionality and stability of the connection heavily depends on the compatibility of the Bluetooth adapter used.4.4 Wii Remotes do not stay paired after closing the game.4.3 "Failed to detach kernel driver for BT passthrough".
4.2 "Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED".4.1 "Failed to open Bluetooth device: LIBUSB_ERROR_ACCESS".
I used a fresh and portable Arduino environment to do this. I'd really like to get this figured out and get a character emulated. I think all we need now is a way to write RAW (!) HID data from the Arduino, because that's the protocol the Portal uses. Because we replaced the driver in Zadig, the Test GUI won't recognize our Portal anymore, so I used USBlyzer to see the data. Make sure to use Zadig 2.0.1! So now Dolphin is recognizing the Portal and it's working just like a real console. So I followed these instructions to get the Portal working, and got it. It recognized the (real) Portal, but it wouldn't recognize figures. I ripped my copy of Skylanders Swap Force to a WBFS file and started the game in Dolphin. I used Serial.write() to try to replicate the data that the Portal was sending to my PC, but I forgot that the Portal used a Raw HID method of data transfer, not Serial. I started placing figures on the Portal and the Portal would send data to the computer (however, the colors of the Portal were not changing based off of the type of character I placed on the Portal). Here's where I got excited: THE GAME RECOGNIZED IT AS A PORTAL! Now I got excited I fired up a Test GUI from a library called HIDAPI, and I plugged in my main Portal.
I fired up Skylanders Swap Force on my Wii and plugged in the Arduino Micro into the USB port of the Wii.