Wii Remote won't connect to GlovePie, but does connect to Dolphin.

[TheSniffer]

I've tried connecting my Wiimote Motion Plus to GlovePie, but the program won't detect it. It works fine on Dolphin.

I've connected the remote to the Bluetooth (Atheros Qualcomm) and it asks for a password. After I click "enter", it loads and the Wiimote's lights turn off. After that, the Wiimote is connected, but won't connect to GlovePie. GlovePie won't even acknowledge its existence. It works fine on Dolphin, but I want to use it on GlovePie. I'm running Windows 10 x64.

Does anyone have any solutions to this?

Thanks in advance!

[leolam]

This is a support forum for Dolphin, so why do you want/need to use GlovePie? You don't need it at all to use your real Wiimote with Dolphin…

[TheSniffer]

This is a support forum for Dolphin, so why do you want/need to use GlovePie? You don't need it at all to use your real Wiimote with Dolphin…

The GlovePie Support forum is down for some reason. A lot of people here work with Wiimotes, so I was hoping someone would have the same problem and help me solve it. I'm sorry if this isn't the right place for this. I've seen a few questions regarding GlovePie in this forum.

[JulianLoehr]

As far as i know GlovePIE Development is abandoned with the last version from 2010. In computer terms that is quite old (just half a year after Windows 7 was released). So don't expect any out of the box support for newer systems.

If you like me to get a little bit more technical, my guess is it is using the HID Set/Get Report Methods for interacting with the devices. Those are depreciated and won't work with "TR-" Wiimotes at all due to some internal things they do the newer Wiimotes don't like.

What is you goal to do with GlovePIE and your Wiimotes? There are a lot of better alternatives out for it.

[TheSniffer]

As far as i know GlovePIE Development is abandoned with the last version from 2010. In computer terms that is quite old (just half a year after Windows 7 was released). So don't expect any out of the box support for newer systems.

If you like me to get a little bit more technical, my guess is it is using the HID Set/Get Report Methods for interacting with the devices. Those are depreciated and won't work with "TR-" Wiimotes at all due to some internal things they do the newer Wiimotes don't like.

What is you goal to do with GlovePIE and your Wiimotes? There are a lot of better alternatives out for it.

I really just want to be able to map keys to the buttons and the gyroscope. Nothing special. I might get a nunchuck and start playing FPS games. I heard of GlovePIE and thought that sounded like something that would help me achieve that.

Any alternatives? How would one go about getting around the HID Set and finding another way for the computer to respond to the wiimote?

Thanks for replying.

[mbc07]

AFAIK the last version of GlovePIE worked fine with -TR Wiimotes if you manually connected them through Toshiba BT Stack and checked "No Auto-Bluetooth Connect" in GlovePIE's Troubleshooter menu...

[Bighead]

I really just want to be able to map keys to the buttons and the gyroscope. Nothing special. I might get a nunchuck and start playing FPS games. I heard of GlovePIE and thought that sounded like something that would help me achieve that.

I still think GlovePIE is very useful for some stuff due to its high level of customization through scripts, although on these forums there is a general vibe of animosity towards it because the author proved himself to be a tool. Plus it is old at this point, to get true analog support you also need to install PPJoy which requires putting windows forever in "test mode" because if you map to keyboard you are only getting a digital input with no range. And if you don't own an original wiimote I guess it can be a hassle. In my case, test mode doesn't bother me and I own only original wiimotes.

I hate to tell you though using the wiimote for most FPS games is not really a viable option even with GlovePIE. These games do not use the absolute position of the mouse, rather they use Direct-X Mouse which reads how far the mouse has moved from its previous position. This means when you're pointing at your screen, the camera just rapidly spins out of control because you are using the full range of your screen and there is no true "center" to compare to. And its not just limited to FPS games, Child of Light for example uses absolute position when running around, but in battle it uses DX Mouse. It's touch and go. There are ways to limit the range to decrease the speed, but it's near impossible to get it to a satisfactory level where playing with a wiimote is enjoyable, because the game is only reading how far you moved the cursor, not where the cursor actually is.

Where GlovePIE does come in handy is using it as a mouse in general, which is a large reason I still hold onto it. My wiimote is connected almost 24/7 as a mouse. You can smooth the input so its not all jittery like the mouse mode with Dolphin Bar. And there's the ability to create macros, so to speak. An example is a script I made for Axiom Verge. Press Home+Up/Down and D-Pad/Analog is switched between movement/weapon select. Press Home+Right and enable rapid fire. Press Home + Left and it enables a function to dash in any direction with a right joystick press rather than tapping forward twice. As far as I know, nothing else offers this level of customization with such relative ease.

In the end I will agree that there are definitely far better options that exist if all you want to do is map buttons. If you noticed in Julian's signature he has a driver solution of his own right there. I never tried it because I've never had a need but I trust it works well.
https://www.julianloehr.de/educational-w...d-wiimote/

You can also just get a DolphinBar, but the above solution should suffice unless you also need a sensor bar, which is about all I use it for.

If you do end up getting GlovePIE to work, I have some scripts here you can use, if only for examples.