WiiLi.org

[jaku]

I have 4 wiimotes, and have been unable to get all 4 to connect with GlovePIE. I can get them all connected with Bluetooth, but GlovePie only works with 3 of them. I have 3 different bluetooth interfaces, 2 usb, 1 internal. I have tried it with BlueSoleil, WidComm, and the Microsoft stack. I have tried connecting 2 remotes to 1 USB bluetooth device, and 2 to the other using both BlueSoleil and WidComm. I tried a bunch of other stuff as well, such as running 2 instances of GlovePie to control 2 remotes each, and still only 3 respond. I have tried Wiimote1-20 in the code, just incase it was 1-4 and none of them respond. I have tried 3 different computers as well. Any help would be great, thanks.

[CarlKenner]

Hmmm.... That's bizarre.
GlovePIE supports 8 wiimotes. But sometimes it detects fake ones which take up spaces of real ones. It numbers the wiimotes backwards going from last being 1 to first being 8, so that the fake ones tend to end up near the end.

What does Wiimote.Count say? That is how many wiimotes it thinks you have.

I have no idea what the problem is. I only have one wiimote to test it with.

[jaku]

debug = wiimote.count says 4. Even when only 2 controllers are connected. Anything that GlovePie remembers maybe that I can clear? Rebooting it still shows 4.

[Naxan]

Just to start with my situation:
-I have one USB bluetooth adapter
-I use BlueSoleil for my drivers
-I can connect all 5 of my Wiimotes with the one USB adapter on BlueSoleil
Now, some things I have noticed. When BlueSoleil encounters a new Wiimote, I assume it assigns it a unique number (#1-5 for me) that GlovePIE reads. So when I connect a Wiimote (lets say Wiimote assigned #2) and even though it is the one and only Wiimote connected, GlovePIE will only work with it as #2, ie "wiimote2". So for me every time I grab a random Wiimote, I have to load a test PIE file and figure out what number that Wiimote is assigned.
This is my wiimote test PIE (I did base this on a Wiibrator PIE):

// Naxans Wiimote Tester
// D pad up turns it on
// D pad down turns it off
if wiimote1.Up
wiimote1.Rumble = 1
var.w1 = "Wiimote #1: On"
endif
if wiimote1.Down
wiimote1.Rumble = 0
var.w1 = "Wiimote #1: Off"
endif
if wiimote2.Up
wiimote2.Rumble = 1
var.w2 = "Wiimote #2: On"
endif
if wiimote2.Down
wiimote2.Rumble = 0
var.w2 = "Wiimote #2: Off"
endif
if wiimote3.Up
wiimote3.Rumble = 1
var.w3 = "Wiimote #3: On"
endif
if wiimote3.Down
wiimote3.Rumble = 0
var.w3 = "Wiimote #3: Off"
endif
if wiimote4.Up
wiimote4.Rumble = 1
var.w4 = "Wiimote #4: On"
endif
if wiimote4.Down
wiimote4.Rumble = 0
var.w4 = "Wiimote #4: Off"
endif
debug = var.w1+', '+var.w2+', '+var.w3+', '+var.w4

So to test your Wiimotes you press up on it and the debug will tell you if it is Wiimote #1-4. Hopefully this helps. Also, pre-Nunchuk support I had a PIE written that would allow all 4 Wiimotes to be run at the same time with all keys mapped. Any info you need, feel free to ask.

[jaku]

I figured out the problem, it wasn't the bluetooth or the program at all. It was windows, I just went to the device manager and removed all the HID Controllers and then added the controllers back one by one and got all 4 to work.