Project

General

Profile

Actions

Emulator Issues #10151

closed

Two step launching not working with Bluetooth Passthrough

Added by WallK about 7 years ago. Updated about 7 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
Windows
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
5.0-3123

Description

Game Name?

Games with launchers: Wii Sports + Resort, Metroid Prime Trilogy, etc.

Game ID? (right click the game in the game list, properties, info tab)

SP2P01 and R3MP01

What's the problem? Describe what went wrong.

Having Wii Bluetooth Module (WML-C43, BCM2045) in passthrough mode and trying to launch before-mentioned games.
Launcher part works fine, but after selecting what game to launch -- Dolphin sends error "Failed to open Bluetooth device: LIBUSB_ERROR_OTHER (https://puu.sh/uHsUP/eb4af97e53.png) and then that no usable devices was found, aborting (https://puu.sh/uHsZr/5b9c651ca9.png)

What steps will reproduce the problem?

Just launch those titles and try to launch actual game.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

5.0-2644
5.0-2856
5.0-2872

What are your PC specifications? (CPU, GPU, Operating System, more)

i5 6600k, GTX1070, Win10x64

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

Screenshots of errors:
https://puu.sh/uHsUP/eb4af97e53.png
https://puu.sh/uHsZr/5b9c651ca9.png

Tried to get the logs, not sure what log types are relevant:

17:48:177 HW\WiimoteReal\WiimoteReal.cpp:727 N[Wiimote]: WiimoteReal::Initialize
17:48:179 HW\WiimoteReal\WiimoteReal.cpp:559 N[Wiimote]: Wiimote scanning thread has started.
22:24:988 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
22:25:324 IOS\USB\Bluetooth\BTReal.cpp:118 N[IOS_WIIMOTE]: Using device 057e:0305 (rev 100) for Bluetooth: Broadcom Corp BCM2045A 
22:41:012 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
22:42:112 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
24:24:918 Core.cpp:272 I[CONSOLE]: Stop [Main Thread]       ---- Shutting down ----
24:25:024 Core.cpp:649 I[CONSOLE]: Stop [Video Thread]      ---- Shutdown complete ----

Files

Dolphin_2017-03-13_23-22-50.png (3.11 KB) Dolphin_2017-03-13_23-22-50.png LIBUSB_ERROR_OTHER WallK, 03/13/2017 09:28 PM
Dolphin_2017-03-13_23-23-32.png (4.27 KB) Dolphin_2017-03-13_23-23-32.png WallK, 03/13/2017 09:29 PM
Actions #1

Updated by JMC4789 about 7 years ago

  • Status changed from New to Questionable

It's a problem with usbdk on Windows. Windows is trying to take back the bluetooth device. If you use Zadig and permanently overwrite the driver with WinUSB, Windows won't try to take it back, so even using usbdk it'll work. Can you try that?

Actions #2

Updated by WallK about 7 years ago

No, it's exactly the same with WinUSB

Actions #3

Updated by JMC4789 about 7 years ago

It's an issue on your end then; as I cannot reproduce. usbdk/winusb seem volatile at best with various adapters... I really don't know how to debug this any further. LibUSB error in teh logs is out of our scope.

Actions #4

Updated by WallK about 7 years ago

After rebooting with WinUSB driver on BCM2045A -- Dolphin crashes on game boot. What Log Types should I check and provide?

Actions #5

Updated by JMC4789 about 7 years ago

Well, the issue is that Dolphin isn't getting control of the USB device, which is bad. When in passthrough mode, Dolphin pretty much HAS to get it, or else things go poorly.

For some reason, something else else (whether another program or a bug, I don't know,) is making it so we cannot get control of the bluetooth adapter.

None of these issues exist on Linux, and my Windows PC isn't running into it. The logs you gave say what's going on, but, I don't know how to fix it outside of just messing around with it until it works.

Actions #6

Updated by WallK about 7 years ago

Can you suggest in which way should I mess on? Maybe I'll stumble on my setup's problem

Actions #7

Updated by JMC4789 about 7 years ago

With LibUSB, I tend to try different USB ports, unplugging various USB devices, if you have other USB bluetooth adapters, you can try those, etc.

You want to make sure Windows isn't trying to use the adapter (if it shows up in the taskbar, that means it can access it and that usually means bad things can happen.)

You can always try resetting the drivers and installing again... this entire thing is finicky to the max.

Actions #8

Updated by WallK about 7 years ago

I do want to make it work properly, so I'll fiddle with it throughout. Thank you!

Actions #9

Updated by JMC4789 about 7 years ago

If you can, try older builds with passthrough too, just to make sure we didn't muddle up anything in particular setups too.

Actions #10

Updated by WallK about 7 years ago

Wow! It works with WinUSB in versions from 5.0-2204 to 5.0-2341 including (didn't go deeper)
Stops working (crash) on 5.0-2352 (https://dolphin-emu.org/download/dev/d244597b4250214a4bd529db649a4042cdbfa249/)

Actions #11

Updated by WallK about 7 years ago

Actually, works with usbdk too. But now it crashes with every version newer than 5.0-2341.

Wasn't doing this before with libusbK before

Actions #12

Updated by JMC4789 about 7 years ago

usbdk isn't supported in the older builds. If you uninstall the usbdk drivers, it should fallback to the old behavior.

Actions #13

Updated by WallK about 7 years ago

But it's working with older builds, not working with newer starting on 5.0-2352

Actions #14

Updated by WallK about 7 years ago

Damn, I meant usbK

usbdk doen't want to install on my system

Actions #15

Updated by WallK about 7 years ago

So what happened in 5.0-2352 that broke my ability to play games with launchers?

Actions #16

Updated by WallK about 7 years ago

 17:45:486 HW\WiimoteReal\WiimoteReal.cpp:559 N[Wiimote]: Wiimote scanning thread has started.
 17:45:486 HW\WiimoteReal\WiimoteReal.cpp:727 N[Wiimote]: WiimoteReal::Initialize
 17:54:023 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
 17:54:141 IOS\USB\Bluetooth\BTReal.cpp:101 E[IOS_WIIMOTE]: Failed to get config descriptor for device 1b21:1242: LIBUSB_ERROR_NOT_FOUND
 17:54:141 IOS\USB\Bluetooth\BTReal.cpp:101 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:a12f: LIBUSB_ERROR_NOT_FOUND
 17:54:142 IOS\USB\Bluetooth\BTReal.cpp:118 N[IOS_WIIMOTE]: Using device 057e:0305 (rev 100) for Bluetooth: Broadcom Corp BCM2045A 
 18:01:649 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
 18:02:743 HW\WII_IPC.cpp:140 I[WII_IPC]: Resetting ...
 18:02:850 IOS\USB\Bluetooth\BTReal.cpp:101 E[IOS_WIIMOTE]: Failed to get config descriptor for device 1b21:1242: LIBUSB_ERROR_NOT_FOUND
 18:02:850 IOS\USB\Bluetooth\BTReal.cpp:101 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:a12f: LIBUSB_ERROR_NOT_FOUND
 18:02:851 IOS\USB\Bluetooth\BTReal.cpp:118 N[IOS_WIIMOTE]: Using device 057e:0305 (rev 100) for Bluetooth: Broadcom Corp BCM2045A 

Now it does this and gets stuck on black screen after trying to launch game from launcher. On winusb and usbk the same

Actions #17

Updated by Koppis about 7 years ago

I'm having the exact same problem with the Wii bluetooth module. I guess I'll just use 2341...

If someone wants more logs I'll be happy to help. I can also give debug logs.

There is a related issue on the usbdk github page here: https://github.com/daynix/UsbDk/issues/35

Actions #18

Updated by leoetlino about 7 years ago

  • Status changed from Questionable to Fix pending
  • Operating system Windows added
  • Operating system deleted (N/A)
Actions #19

Updated by JosJuice about 7 years ago

  • Status changed from Fix pending to Fixed
  • Fixed in set to 5.0-3123
Actions

Also available in: Atom PDF