• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 178 179 180 181 182 ... 1189 Next »

Problem When Shutting Games Down (w/ Bluetooth Passthrough)
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Problem When Shutting Games Down (w/ Bluetooth Passthrough)
06-23-2019, 12:32 PM
#1
awosaibi
Unregistered
 
Exclamation 
Hello everyone!


First, let me say that I have WinUSB installed and it works great when I have a game up and running. There is only one small issue...

After I close a game and try to start another, I get an endless black screen. The problem goes away when I restart Dolphin and start a game, but persists when I try to launch any subsequent titles.
I also found out that after closing a game down (using the stop button), I get abnormally high CPU usage for Dolphin:
[Image: tVSOgla.png]
Whenever I launch a game while it's in this state and with Bluetooth Passthrough enabled, I get the black screen.

It also spits this out in the logs:
Code:
01:50:855 core\ios\stm\stm.cpp:48 I[IOS_STM]:     IOCTL_STM_VIDIMMING
01:50:871 core\ios\ios.cpp:475 I[IOS]: Opening /dev/usb/oh1/57e/305 (mode 0, fd 6)
01:50:881 core\ios\usb\bluetooth\btreal.cpp:89 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:a12f
01:50:881 core\ios\usb\bluetooth\btreal.cpp:106 N[IOS_WIIMOTE]: Using device 8087:0aa7 (rev 1) for Bluetooth:  
01:51:448 c:\buildbot\release-win-x64\build\externals\cubeb\src\cubeb_wasapi.cpp:377 N[Audio]: Audio device property value changed.
and nothing after that.
It seems to correctly identify and select the Bluetooth device, I'm just not sure what the 3rd line Failed to get config descriptor for device 8086:a12f means.

Obviously, this is a Bluetooth Passthrough related issue, as when I use Emulated and close a game down, I don't get the same high CPU usage.
Could it be stuck in some sort of loop...? I'm currently using version 5.0-10551.


Any help is highly appreciated. Thanks!
-Abdullah
Reply
06-24-2019, 02:11 AM (This post was last modified: 06-24-2019, 05:23 AM by Rusty Potato. Edit Reason: phrasing )
#2
Rusty Potato Offline
Junior Member
**
Posts: 34
Threads: 1
Joined: Feb 2019
(06-23-2019, 12:32 PM)awosaibi Wrote: Hello everyone!


First, let me say that I have WinUSB installed and it works great when I have a game up and running. There is only one small issue...

After I close a game and try to start another, I get an endless black screen. The problem goes away when I restart Dolphin and start a game, but persists when I try to launch any subsequent titles.
I also found out that after closing a game down (using the stop button), I get abnormally high CPU usage for Dolphin:
[Image: tVSOgla.png]
Whenever I launch a game while it's in this state and with Bluetooth Passthrough enabled, I get the black screen.

It also spits this out in the logs:


Code:
01:50:855 core\ios\stm\stm.cpp:48 I[IOS_STM]:     IOCTL_STM_VIDIMMING
01:50:871 core\ios\ios.cpp:475 I[IOS]: Opening /dev/usb/oh1/57e/305 (mode 0, fd 6)
01:50:881 core\ios\usb\bluetooth\btreal.cpp:89 E[IOS_WIIMOTE]: Failed to get config descriptor for device 8086:a12f
01:50:881 core\ios\usb\bluetooth\btreal.cpp:106 N[IOS_WIIMOTE]: Using device 8087:0aa7 (rev 1) for Bluetooth:  
01:51:448 c:\buildbot\release-win-x64\build\externals\cubeb\src\cubeb_wasapi.cpp:377 N[Audio]: Audio device property value changed.
and nothing after that.
It seems to correctly identify and select the Bluetooth device, I'm just not sure what the 3rd line Failed to get config descriptor for device 8086:a12f means.

Obviously, this is a Bluetooth Passthrough related issue, as when I use Emulated and close a game down, I don't get the same high CPU usage.
Could it be stuck in some sort of loop...? I'm currently using version 5.0-10551.


Any help is highly appreciated. Thanks!
-Abdullah

https://dolphin-emu.org/blog/2019/06/02/dolphin-progress-report-may-2019/#updates-on-the-libusb-situation
This seems to be a known issue for WinUSB. Try switching to libusbk.
EDIT: This may be inaccurate, see below. Sorry! Keeping an eye on the thread themanuel linked may be your best bet for now.
Find
Reply
06-24-2019, 04:44 AM
#3
themanuel Offline
Parasitic Member of the Community
*****
Posts: 828
Threads: 63
Joined: Oct 2009
(06-24-2019, 02:11 AM)Rusty Potato Wrote: https://dolphin-emu.org/blog/2019/06/02/dolphin-progress-report-may-2019/#updates-on-the-libusb-situation
This seems to be a known issue for WinUSB. Try switching to libusbk.

It is not just WinUSB, it happens with libusbK as well, but not to everyone.
See here:
https://forums.dolphin-emu.org/Thread-5-0-10344-broke-bt-passthrough-for-me?pid=494458#pid494458
Windows 10 Pro x64  |  i7-9700K @ 4.6-5.0GHz  |  MSI Z370 Gaming Plus  |  MSI RX 5700 8GB Factory-OC  |  16 GB DDR4-3000
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode