Emulator Issues #6240
closedconnectionstate checkmarks in "Connect Wiimote" menu items and their keyboard-shortcuts behaving weird
0%
Description
What went wrong?
the check-marks indicating the connection-state of the wiimotes in the "Tools">"Connect Wiimote 1-4" menuitems are not behaving correctly. after connecting and refreshing 2 wiimotes and starting a game in which both wiimotes are working perfectly fine, no check-marks appear.
toggling the wiimotes via ALT-F5 or ALT-F6 or via the menu results in check-marks appearing sometimes, but not correctly. sometimes even toggling the wiimote 1 connection state results in the checkmark on wiimote 2 to change (or vice versa).
another thing i encountered is, that toggling the connection-state via keyboard shortcut (e.g. ALT-F5) multiple times results in the state set to "connected" 2 times and then "disconnected" 1 time and continuing this pattern. e.g. like this:
- Wiimote 1 Connected
- Wiimote 1 Connected
- Wiimote 2 Connected
- Wiimote 1 Connected
- Wiimote 1 Connected
- etc.
What did you expect to happen?
- the checkmarks to correctly show the current connection-state of the wiimotes
- and the keyboard shortcuts for toggling the connection states to actually behave like toggles (on/off/on/off/etc.)
What steps will reproduce the problem?
connect 2 wiimotes, start a game and play arount with the connection states either with menu or via keyboard shortcuts
What version of Dolphin were you using?
3.5-1210
64 or 32 bit Dolphin?
64bit
What version of Dolphin used to work?
3.5-471 definitely works.
What Operating System were you using and what are your hardware
specifications?
- Windows 7 x64
- Original Nintendo Motion Plus Inside Wiimotes (non-TR)
- Asus bt211 Bluetooth Adapter (tested with Microsoft Stack and Bluetooth Stack)
Updated by Billiard26 over 11 years ago
- Status changed from New to Accepted
- Issue type set to Bug
- Category set to ui
Yes, they are broken. Even in and before 3.5-471 they would desync.
Updated by rachelbryk over 11 years ago
- Regression set to Yes
Billiard broke it somewhere in real-wiimote-scanning.
Updated by JohnAllenYoung over 11 years ago
Still broken in 3.5-1321, 32-bit Dolphin. I also noticed that I have to manually connect every time I start the program, whereas in older revisions prior to this problem it would keep my emulated wiimote connected between sessions.
Updated by Billiard26 almost 6 years ago
- Status changed from Accepted to Fix pending
Updated by Billiard26 almost 6 years ago
- Status changed from Fix pending to Fixed
- Fixed in set to 5.0-9549