RVL-CNT-01-TR

[gergc]

A side note about the input: Before the Wiimote is put into continuous reporting mode it actually reports back the inputs. Like, "a1 30 00 00" for no buttons pressed "a1 30 11 00" for a few of the buttons pressed (it's a bitfield, see the wiimote wiki for more on that). After you try and put it into continuous reporting mode it actually responds with error messages.

Pairing to windows isn't part of the problem, dolphin recognizing it isn't either because we can get it to recognize a bluetooth keyboard if we wanted to (just by simply changing the strings dolphin looks for in the bluetooth device list)

[skid]

To turn off continuous reporting mode (maybe this mode has been disabled in the new Wiimotes), change this line in WiimoteReal.cpp:

Code:

unsigned char buffer[2] = {0x04, 0x30};

to

Code:

unsigned char buffer[2] = {0x00, 0x30};

Dolphin will probably also need to be changed so that it expects reports only when the data changes. Try uncommenting these lines:

Code:

//if (WM_REPORT_MODE == ((u8*)data)[1])
//{
//    // also delete the last data report
//    if (m_last_data_report.first)
//    {
//        delete[] m_last_data_report.first;
//        m_last_data_report.first = NULL;
//    }

//    // nice var names :p, this seems to be this one
//    ((wm_report_mode*)(rpt.first + 2))->all_the_time = false;
//    //((wm_report_mode*)(data + 2))->continuous = false;
//}

This line might also need to be uncommented:

Code:

//((wm_report_mode*)(data + 2))->continuous = false;

Let us know how you go.

[gergc]

I attempted those modifications - I am outputting the read buffer from the wiimote and there are no changes from when I was testing before. The LEDs aren't being set either (which they never were able to be set). It might also be noteworthy that if I plug a nunchuck into the Wiimote while it is connected the Wiimote enters error mode

[Tetdoss]

Hello world !
I'm french and speak a little english and I think I have the same issue as you.
Recently I bought the new Wiimote Plus Black RVL-CNT-01-TR and it doesn't work with Dolphin but it works with Windows 7.

Is there a way without buy an old Wiimote Plus ? I find nothing in french forums and in english forums too[/align]...

Thanks a lot.

[Xtreme2damax]

How is reverse engineering of the Wiimote/Bluetooth protocol done? I find it hard to believe that the new Wiimotes changed that much yet work fine on the actual Wii, I don't think it should be that hard to fix. If it requires a driver then those of us with Windows 7 x64 are SOL due to certification being required which costs money.

[gergc]

You can run unsigned drivers on x64 by turning off driver signature verification.

Either way, this is how far I got: http://quasared.net/dolphin1.png

Input doesn't seem to be detected at all inside of dolphin. This is with continuous reporting off (although that doesn't seem to matter at this point). I am holding the A and B buttons (you can see that Buffer3 swaps between c, 8, and 0. (c being A and B held down, 8 being just A held down, and 0 being no buttons held down). Input only updates when you press a button (hence, continuous reporting off). I got this far 2 weeks ago and then gave up.

[mbc07]

(12-11-2011, 09:00 AM)Xtreme2damax Wrote: How is reverse engineering of the Wiimote/Bluetooth protocol done? I find it hard to believe that the new Wiimotes changed that much yet work fine on the actual Wii, I don't think it should be that hard to fix. If it requires a driver then those of us with Windows 7 x64 are SOL due to certification being required which costs money.

Also, if we creata a driver, how will it be ported to the other platforms (linux, mac, etc)?

[gergc]

I should probably specify, I meant that input wasn't detected inside of any games (I am testing Twilight Princess and Skyward Sword). Obviously Dolphin is communicating with the Wiimote as per my screenshot

[tekiek]

(12-11-2011, 09:11 AM)gergc Wrote: I should probably specify, I meant that input wasn't detected inside of any games (I am testing Twilight Princess and Skyward Sword). Obviously Dolphin is communicating with the Wiimote as per my screenshot

Any update on this?

New user as well, went out and bought everything to only find out it does not work .

[Xtreme2damax]

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.

---

(12-11-2011, 09:07 AM)gergc Wrote: You can run unsigned drivers on x64 by turning off driver signature verification.

Either way, this is how far I got: http://quasared.net/dolphin1.png

Input doesn't seem to be detected at all inside of dolphin. This is with continuous reporting off (although that doesn't seem to matter at this point). I am holding the A and B buttons (you can see that Buffer3 swaps between c, 8, and 0. (c being A and B held down, 8 being just A held down, and 0 being no buttons held down). Input only updates when you press a button (hence, continuous reporting off). I got this far 2 weeks ago and then gave up.

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.