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


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Controllers v
« Previous 1 ... 189 190 191 192 193 ... 320 Next »

Wiimote handshake issue
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Wiimote handshake issue
03-07-2014, 11:42 AM
#1
bob__
Unregistered
 
I'm trying to get dolphin up and running on a brand new pc I bought from newegg this week. Everything seems to go fine except connecting the wiimote. When I add it in the Windows 8 bluetooth dashboard (don't know what it's properly called), the pc seems to think it's working fine and adds it to my list of devices, but the wiimote keeps all 4 lights flashing like it's waiting for a further part of the handshake that the pc doesn't know about. It will stay like that until I use the power button to turn it off. If I start dolphin (with or without the wiimote installed in windows), both wiimote and dolphin act like they have no awareness of the other's existence.

I have both a -TR and a...er...non-TR Wiimote, and they behave the same way. (they both have the built-in Motion+, though, and I'm trying to emulate Skyward Sword, so I need that functionality) When I bring up bluetooth settings (or device manager), the list of devices under "hardware" (or "Bluetooth") includes the following:

"Bluetooth USB Module"
"Device Identification Service"
"Microsoft Bluetooth Enumerator"
"Microsoft Bluetooth LE Enumerator"
"Nintendo RVL-CNT-01"
"Service Discovery Service"

Things I have tried:

1) Downloaded the Toshiba stack, but apparently the bluetooth device in my new pc isn't supported; and I don't feel comfortable forcing the drivers onto the adapter.
2) Updating the drivers for my bluetooth devices. Windows tells me they're all already up to date. I can't find any data on the bluetooth that comes in this pc other than "Bluetooth 4.0", so I don't know where to begin searching for ways to update those drivers myself.
3) Registering the device with Windows with or without dolphin already running, with or without the game already running, with or without the nunchuk attached to the wiimote, telling the wiimote to connect by hitting A, holding 1+2, or by pushing the red "sync" button inside the battery cover, rebooting in between windows registration and dolphin attempt and not rebooting at all, and every combination of these options that I can think of. It all resulted in the same behavior, but I'm sure I didn't try all 48 combinations of these values.
4) Someone on another similar thread suggested deleting the ini file that holds the wiimote configuration in dolphin. I tried this, but it had no effect that I noticed.

I realize this isn't a dolphin problem (the Wiimote never even gets to the point where Dolphin can interact with it), but I'm not sure where else to go for help. So I guess my question is whether this sounds like a problem with my hardware, with my drivers, or with some setting I have somewhere. I would include my dolphin log, but--again--it doesn't sound like a problem with dolphin proper to me. But all the support out there that I can see, either says to get the toshiba stack (but that sounds like it's more for solving the problem with the TR-specific wiimotes; I haven't seen that advice on a thread that mentions the older ones) or some combination of syncing and button-pressing that falls under the list of stuff I tried. And anyway, the threads I found were all dealing with times when the wiimote doesn't acknowledge the pc at all; I couldn't find anything about the wiimote waiting for a handshake completion that never comes.

By the by, on the machine I had before this one (I still have it, but I'm migrating away from it for dolphin b/c its processor is way too slow to handle wii games in real time), I attached the pre-TR wiimote in windows some months ago (don't remember exactly how, but I didn't have nearly as much trouble with it as I'm having on this new pc) and can connect either of the wiimotes to the old machine's Dolphin just by mashing the A button until the two devices started talking. With the new machine, the wiimote just seems to not believe the handshake has been finished.

Again, I realize this isn't a dolphin-specific question, but any help you guys can give would be greatly appreciated. I just want to make sure it's a hardware problem before I go buying more hardware or--if it's a software issue--get some direction on where I should go for the software I need. Thanks again.
Reply
03-07-2014, 12:34 PM
#2
AnyOldName3 Offline
First Random post over 9000
*******
Posts: 3,528
Threads: 1
Joined: Feb 2012
Firstly, have you definitely followed this? https://dolphin-emu.org/docs/guides/wii-remote-plus-rvl-cnt-01-tr-connection-guide/

Secondly, you may want to try something else which interacts such as GlovePie to see if you get any life out of them.
OS: Windows 10 64 bit Professional
CPU: AMD Ryzen 5900X
RAM: 16GB
GPU: Radeon Vega 56
Find
Reply
03-07-2014, 01:45 PM
#3
bob__
Unregistered
 
(03-07-2014, 12:34 PM)AnyOldName3 Wrote: Firstly, have you definitely followed this? https://dolphin-emu.org/docs/guides/wii-remote-plus-rvl-cnt-01-tr-connection-guide/

Secondly, you may want to try something else which interacts such as GlovePie to see if you get any life out of them.

Well, I have followed those instructions up to installing the toshiba stack. It gives me the "Please plug in the Bluetooth device and click the OK button" message, and every time I click ok the message comes back 20-30 secs later. As I understand it, that means my bluetooth hardware is not compatible with the toshiba stack and I can't really do anything further from that document.

However, now I'm starting to think maybe it IS more of a dolphin issue I'm having. I'm honestly not sure what GlovePie even does, but I downloaded and installed it and ran it. When I run the prepackaged wiimotionplus script that comes with it, my wiimote goes into "Player One" mode. I have no idea if the script is running correctly or not (I'm not even sure what it's supposed to do), but when I'm running that script, clicking A on my wiimote has the same effect as clicking my left mouse button, so I guess some sort of signal is actually getting through. But whenever I tell Dolphin to "Connect Wiimote 1", it immediately spews "Wiimote connected." and "Wiimote disconnected." in the game's window. But as soon as I terminate the script, the wiimote shuts off.

Ok, forget everything I said. Apparently running GlovePie has somehow gotten it connected properly, and all of a sudden it seems to work magically. ... Dunno why or how, but thanks for the help!


Attached Files Thumbnail(s)
   
Reply
04-01-2014, 02:47 AM
#4
inteGReddy Offline
Somewhat Useful Senior Member
****
Posts: 421
Threads: 11
Joined: Jun 2010
Do not use the BT control panel to pair the wiimote. Just bring up the wiimote panel in dolphin, set player 1 to real, press 1+2 on the wiimote, and then click the refresh button. Just make sure you keep pressing buttons on the mote until it is fully paired and vibrates.
[Image: 53r3k4.png]
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