Wiimote input issues (Windows 10, RVL-003, Bluetooth or Dolphinbar Failing)

[snaito]

Windows 10, Wiimote is RVL-003, Used multiple version up to current revisions with no success and same behaviors. Using the log it shows that Dolphin is unable to send info back to the wiimote. This is while using mode 4 on the dolphibar.

Trying to use the wiimote via bluetooth dongles (including ones wiihomebrew says should work) but it will not connect to any bluetooth stack I use successfully which is why I have dolphinbar. (I have tried to update dolphinbar firmware, but at first it said I couldn't because its already updated, and now it just thinks its not even the right hardware so it doesn't try to update)

Using Hybrid controller and mode 3 I can get dolphin to recognize button inputs but not IR stuff.

The problem is when I open any game the sync with dolphinbar will die, dolphin will not accept inputs, and the following log says what it says.

I have tried many different kinds of fixes and troubleshooting to no avail. If anyone knows any workarounds or fixes please let me know. I have been working on this for the better part of a month now.

Now I have gotten dolphin to the point where the dolphinbar and the wiimote show full connection, rumble works when it connects, the logs show NO errors of any kind. still can not put in any inputs.

I have also tried a new bluetooth adapter that uses broadcom/widcomm with no effect. Made sure there is nothing logitech existing on computer as well just in case.


49:38:950 Src\HW\WiimoteReal\WiimoteReal.cpp:607 N[Wiimote]: WiimoteReal::Initialize
49:38:950 Src\HW\WiimoteReal\WiimoteReal.cpp:440 N[Wiimote]: Wiimote scanning has started.
49:46:488 Src\HW\WiimoteReal\WiimoteReal.cpp:473 N[Wiimote]: Wiimote scanning has stopped.
49:46:490 Src\HW\WiimoteReal\WiimoteReal.cpp:440 N[Wiimote]: Wiimote scanning has started.
49:54:379 Src\ConfigManager.cpp:140 N[BOOT]: Saving settings to C:/Users/Seiren/Documents/Dolphin Emulator/Config/Dolphin.ini
49:54:717 Src\Main.cpp:709 N[Wiimote]: Not connected
49:55:862 Src\Boot\Boot.cpp:199 N[BOOT]: Booting F:\Emulators\Dolphin\Games\game1.iso
49:55:883 Src\HLE\HLE_OS.cpp:43 N[OSREPORT]: 81200614->81300000|
Apploader Initialized.
49:55:883 Src\HLE\HLE_OS.cpp:43 N[OSREPORT]: 81200630->81300000| This Apploader built Jun 22 2009 18:54:04 for RVL
49:57:256 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - EXI release build: Feb 27 2009 10:02:03 (0x4302_145) >>
49:57:256 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - SI release build: Feb 27 2009 10:04:44 (0x4302_145) >>
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]:
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: Revolution OS
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: Kernel built : Feb 27 2009 10:04:29
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: Console Type : NDEV 2.1
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: Firmware : 53.16.17 (6/25/2007)
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: Memory 88 MB
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: MEM1 Arena : 0x8067b560 - 0x817fa380
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: MEM2 Arena : 0x90000800 - 0x93ae0000
49:57:296 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - OS release build: Feb 27 2009 10:04:29 (0x4302_145) >>
49:57:348 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - SC release build: Feb 27 2009 10:05:17 (0x4302_145) >>
49:57:349 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - NAND release build: Feb 27 2009 10:05:16 (0x4302_145) >>
49:57:353 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - DVD release build: Feb 27 2009 10:01:59 (0x4302_145) >>
49:57:359 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: ProgArea (aaa0 / 686000)
49:57:359 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - VI release build: Feb 27 2009 10:04:46 (0x4302_145) >>
49:57:462 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - GX release build: Feb 27 2009 10:04:13 (0x4302_145) >>
49:57:503 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - WPAD release build: Jun 22 2009 18:33:21 (0x4302_145) >>
49:57:503 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - KPAD release build: Jun 22 2009 18:32:13 (0x4302_145) >>
49:57:886 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - AI release build: Feb 27 2009 10:01:30 (0x4302_145) >>
49:57:950 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - AX release build: Feb 27 2009 10:01:36 (0x4302_145) >>
49:57:950 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - DSP release build: Feb 27 2009 10:01:57 (0x4302_145) >>
49:57:972 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << NW4R - G3D final build: Nov 20 2008 03:23:14 (0x4199_60831) >>
49:57:972 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << NW4R - LYT final build: Aug 21 2008 05:21:58 (0x4199_60831) >>
49:57:976 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << RVL_SDK - ENC release build: Feb 27 2009 10:05:42 (0x4302_145) >>
49:58:064 Src\Main.cpp:709 N[Wiimote]: Connecting...
49:58:374 Src\HW\EXI_DeviceIPL.cpp:284 N[OSREPORT]: << NW4R - SND final build: Nov 20 2008 03:40:00 (0x4199_60831) >>
51:11:773 Src\HW\WiimoteReal\WiimoteReal.cpp:473 N[Wiimote]: Wiimote scanning has stopped.
51:11:774 Src\HW\WiimoteReal\WiimoteReal.cpp:440 N[Wiimote]: Wiimote scanning has started.
52:06:094 Src\HW\WiimoteReal\IOWin.cpp:675 N[Wiimote]: WiimoteIOWrite[MSBT_STACK_MS]: Unable to send data to the Wiimote
52:08:586 Src\HW\WiimoteReal\WiimoteReal.cpp:473 N[Wiimote]: Wiimote scanning has stopped.

[snaito]

No one have any ideas at all about this?

[leolam]

Probably not the reply you're waiting for, but I have no idea why it would fail. Since you have a DolphinBar, it should normally just work.
(Perhaps try an OS with a more sane Bluetooth stack? )

[snaito]

Nope, not the reply I am looking for. Dolphinbar fails, bluetooth stacks fail, multiple different adaptors fail. wiimote works perfectly, wiimote is first party. I just don't know, and if there is any developer or staff at all on this site who might have a clue about this issue I would be eternally greatful.

[leolam]

In that case, it sounds like it could really be an issue with your OS, especially if you tried several adapters, even the DolphinBar, and the Wiimote is not third-party. I don't know what to suggest since you're on Windows. I personally use Linux and it has always worked flawlessly and in more cases than with Windows.

[KHg8m3r]

Run command prompt as an administrator and run the command sfc /scannow

[snaito]

(07-19-2016, 02:08 AM)KHg8m3r Wrote: Run command prompt as an administrator and run the  command  sfc /scannow

Just tried a full reformat of my system. Downloaded latest version of Dolphin, ensured dolphinbar was updated, it says it already is. Put it in mode 4, synced it to controller. Dolphin connects the wiimote successfully, Opened a game in dolphin. Still no input sadly.

It still can't be found via Bluetooth itself.

Trying a system scan like you said, not sure what it would discover after a format, but hell why not at this point.

[Craftyawesome]

Make sure wiimote 1 is real wiimote? No other wiimotes. Just to make sure.

[leolam]

(07-19-2016, 09:56 AM)snaito Wrote: Just tried a full reformat of my system. Downloaded latest version of Dolphin, ensured dolphinbar was updated, it says it already is. Put it in mode 4, synced it to controller. Dolphin connects the wiimote successfully, Opened a game in dolphin. Still no input sadly.

It still can't be found via Bluetooth itself.

Since you already went through the trouble of reformatting your whole system, I'd suggest also trying to run Dolphin under Linux, and see if that works with your Bluetooth dongles (the DolphinBar is currently not supported) to see if the issue is really with your OS or with something else.

Quote:Make sure wiimote 1 is real wiimote? No other wiimotes. Just to make sure.

"WiimoteIOWrite" means Dolphin has already found and is connected to the Wiimote, but is just failing to write data to it.