Emulator Issues #9248
closedAggressive Wiimote disconnects crash Dolphin
0%
Description
Game Name?
N/A
Game ID? (right click the game in the game list, properties, info tab)
N/A
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
N/A
What's the problem? Describe what went wrong.
When using the "Real Wiimote" configuration setting, it is possible to crash Dolphin in a number of ways:
- If using the built in BT stack, take the batteries out of the Wiimote
- If using the Mayflash Dolphin bar, disconnect the USB connection
- If using the Mayflash Dolphin bar, press the mode button to move the bar out of mode 4 and into mode 1
What steps will reproduce the problem?
[Note that I have Wiimote motor and Speaker Data enabled]
Built in BT stack
- Start any game with "Real Wiimote" support enabled
- Ensure that Wiimote is connected using the Refresh or continuous scanning mode in the Controllers window
- Kill power to the Wiimote by removing a battery
Mayflash Dolphin bar USB
- Start any game with "Real Wiimote" support enabled
- Ensure that Wiimote is connected using the Refresh or continuous scanning mode in the Controllers window
- Pull the Dolphin bar USB connection out of the machine
Mayflash Dolphin bar mode change
- Start any game with "Real Wiimote" support enabled
- Ensure that Wiimote is connected using the Refresh or continuous scanning mode in the Controllers window
- Press the Dolphin bar's mode button
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?
Verified to fail on most recent build 4.0-8666 but also reproduced on 4.0-8437 (the first version of Dolphin I ever used)
What are your PC specifications? (CPU, GPU, Operating System, more)
MacBook Pro (15 inch late 2011)
2.5GHz i7
8GB 1333MHz RAM
AMD Radeon HD 6770M 1GB
OS X El Capitain 10.11.2
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Let me know if there is something I can provide.
Updated by JMC4789 almost 7 years ago
- Status changed from New to Won't fix
By using Bluetooth passthrough, we don't have to rely on the host state and nothing like this will happen.
I haven't seen any interest in trying to work around edge-cases in the emulated bluetooth path that only happens on certain adapters...