Dolphin, the GameCube and Wii emulator - Forums

(12-11-2011, 10:33 AM)Xtreme2damax Wrote: [ -> ]It seems to be an issue with the blutooth stack or something that is not pairing the Wiimote correctly. When pairing it appears to not pair correctly, if you right click and select properties the Wiimote information such as the Wiimote address is missing. Is there any way to pair Wiimotes using a pairing code, not sure if that would cause issues pairing without a code but the new Wiimotes could be using a secure bluetooth connection which requires a pairing code.

---

I don't think this is correct, because it is pairing just fine for me and it wouldn't be communicating with Dolphin otherwise. The new controller pairs with a different type of HID identifier than the old Wiimotes. The Wiimote isn't DESIGNED to work with a system that's not the Wii, so it's not sending all of the identifying information that the standard bluetooth protocol would normally transfer.

(12-11-2011, 10:33 AM)Xtreme2damax Wrote: [ -> ]The Wiimote code in Dolphin probably needs to be updated to detect the input for the new Wiimotes. Probably going to require finding what the new Wiimotes are doing different and writing the code for it. This is my understanding from reading around but I don't think it's as complicated as needing to write a driver for it.

Yes, this is exactly what needs to be done. However: a custom HID driver would make it easier, because it is theorized that the Wiimote now uses some sort of non-standard protocol (not just screwing around with HID commands) to communicate. It would also decrease latency of the controls. Shuffle2 has confirmed this.

Hey guys i bought a wii remote with WiiMotionPlusINSIDE. I also can't make it work. The problem is my system shows the device name Nintendo RVL-CNT-01 instead of the RVL-CNT-01-TR.

I bought it from the internet from - what people told me - a reliable store. The controller came with two boxes. A nunchuck and the other with the wiimote. There was a manual in some oriental language my guess would be either mandarin or Japanese.


Could it be another version? Of the WiiMotionPlusINSIDE or is it not original?

Any help would be greatly appreciated!

It sounds like you bought a bootleg controller, which is known not to work (similarly to the TR)

Can it work with Dolphin without needing a driver coded? If so, it would make sense to get it working with Dolphin, a driver can be coded later.

It's not a problem that this Unkown BT stack is being used?

I wish I had a normal working wiimote so I could compare this stuff.

http://i.imgur.com/Nrgwr.png

---

Here is another file with some old controller code in it although it's if0 commented. I'm not sure if the info is still being used or not though.

Specifically lines 57 and 59:


WiiMote_HID_Attr.cpp is where this along with a lot of other IDs are at. Like I said though, the code is commented out so I don't know how relevant this is. adding TR to the end of the above didn't seem to do much for me but there might be more in there worth looking at.

And if we make a homebrew application (to run in a real Wii) that log input/outputs from the TR Wiimote during the pair up process? This should help in discovering what was changed, probably not much, since one of my friends bought a TR Wiimote and sucessfuly paired it up with his 4 years old Wii (that still running firmware 2.2U)...

I change in IOWin.cpp to new PID of wiimote TR
In log of dolphin I got "IOWrite[MSBT_STACK_UNKNOWN]" msg (line ~411):

Quote: dw = GetLastError();
// Checking for 121 = timeout on semaphore/device off/disconnected to
// avoid trouble with other stacks toshiba/widcomm
// 995 = The I/O operation has been aborted because of a thread exit or
// an application request.

if ( (dw == 121) || (dw == 995) )
{
NOTICE_LOG(WIIMOTE, "IOWrite[MSBT_STACK_UNKNOWN]");
RealDisconnect();
}

It seems we got a timeout of the new wiimote...

Keep trying, it'll eventually connect. You have to change more than just the lines with the PID, though. See what I posted on the issue tracker. (issue 5011)

Hoping there is some progress soon.. I wonder if the developers are working on this, I don't think that much has changed that there shouldn't be a patch at least within the next week or so. Someone mentioned that the Wiimotes aren't working with the Homebrew channel on a real Wii so maybe it's just a simple case of updating the code to support the new Wiimotes.

Based on what I have seen so far, we believe the write commands are just not being accepted at all by the Wiimote. It could be a bad handshake with the device.