Emulator Issues #12010
closedBluetooth LIBUSB_ERROR_NOT_SUPPORTED false negative
0%
Description
Game Name?
N/A
Game ID?
N/A
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
N/A
What's the problem? Describe what went wrong.
Launching a Wii game in Dolphin 5.0-11719 will prompt the "Failed to open Bluetooth device: LIBUSB_ERROR_NOT_SUPPORTED"
Choosing the "Ignore for this session" button, the game will proceed as normal, including Bluetooth passthrough working as normal
What steps will reproduce the problem?
Launching a Wii game and selecting "Ignore for this session"
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes (Dolphin 5.0-11719 as of writing)
Is the issue present in the latest stable version?
Feature not present in latest stable version
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
N/A
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
N/A
What are your PC specifications? (CPU, GPU, Operating System, more)
CPU: i5-9600k
GPU: AMD RX 5700
OS: Windows 10 (latest)
Memory: 16GB
Bluetooth Adapter: IOGear GBU421 [BCM2046]
Using libusbk driver
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Could not find relevant logs
Updated by Billiard26 about 4 years ago
Dolphin is probably trying to use the incorrect device for Bluetooth passthrough and then falls back to the proper device.
I helped a user with this problem by setting an undocumented passthrough VID/PID setting in Dolphin.ini.
We should probably expose this setting in the UI.
Updated by leoetlino about 4 years ago
- Status changed from New to Accepted
- Relates to usability changed from No to Yes
Yeah, that's a good idea. Another possible fix would be to merge the "open failed" panic alert with the "no usable Bluetooth device found" message, which has the benefit of reducing the number of panic alerts that are shown to the user, especially if they have several adapters.
Updated by leoetlino about 4 years ago
- Status changed from Accepted to Fix pending
Updated by leoetlino about 4 years ago
- Status changed from Fix pending to Fixed
- Fixed in set to 5.0-11774