RVL-CNT-01-TR

[tuscland]

I would like to trade a shiny brand new Wiimote (2 Wiimotes actually red or pink, tested and working) against an incompatible Wiimote TR. I am leaving in Paris france, it would be much appreciated to make trade in the area.

Please PM me to arrange something.


Thanks,
Cam

[Skullkid24]

I have some new information for everyone. Its not much but I hope it helps. The new Wii remote plus controllers will only handle output reports that begin with 0xA2, not 0x52. This means that under Windows, "HidD_SetOutputReport()" will not work. We may have more success using "WriteFile()". I hope this helps.
By the way, I have been able to finally pair the controller in Dolphin by editing the source code. None of the imputs work, and the leds dont light up. But it does vibrate when you click "refresh". Its a start.

[gergc]

What does it do differently for you between 0x52 and 0xA2? It's returning an error status no matter what, for me

[Skullkid24]

Honestly I do not have the slightest clue as to what it means. I received the tip in an anynomous email as a "hint"... It may have absolutely no value. I have done as much as I can with the code myself, and it's not much more than what you suggested... I can't see this issue persisting for more than two months. Maybe by then it will be fixed, if not it's totally understandable. I am getting a Wii for christmas anyways lol. As much as I would like to play skyward sword or any game for that matter in 1920x1080 with a real wii remote I may just have to stick to 480p with component cables on a 720p tv. For now at least.. I will continue to search through the code and tinker with it, trying different values and such, but I can't guarantee any success. At this point I'm doing it more for the rest of you and out of curiosity than anything.

[gergc]

Okay, well without additional information I don't think it'll help much right now. :\

[DeviltheorY]

Damn I wish I found this thread sooner... I just bought myself a sexy new black Wii-mote only to find out it's one of these crappy TR versions... now I have to hunt down an older black one somehow, bleh. I borrowed my sisters older remote (which has motion inbuilt, but is the non TR version) and it works perfectly, I might have to trade with her.

[mbc07]

(12-13-2011, 11:18 AM)gergc Wrote: What does it do differently for you between 0x52 and 0xA2? It's returning an error status no matter what, for me

Apparently, when Dolphin was having issues with third-party Wiimotes, was because the use of output reports that starts with 0xA2. When the devs changed the output reports to 0x52, third-party Wiimotes started to work without breaking compatibility with genuine ones (until the arrive of TR ones)...

[KTroopA]

I have the Zelda SS golden wiimote which works and also recently purchased a Black wiimote plus which is the problematic TR version. Please let me know what i can copy and paste from various logs and il do my best to assist in finding a 'TR' fix

[rgfreek]

(12-14-2011, 11:42 AM)Skullkid24 Wrote: At this point I'm doing it more for the rest of you and out of curiosity than anything.

We're in the same boat man. I wish I had more time to give to this project, I really want to see this thing working.

(12-15-2011, 12:53 AM)KTroopA Wrote: I have the Zelda SS golden wiimote which works and also recently purchased a Black wiimote plus which is the problematic TR version. Please let me know what i can copy and paste from various logs and il do my best to assist in finding a 'TR' fix

You'll need to have some basic understanding of Visual Studio (or learn as you go like I did)

Here ya go:

Code:

SysConf.cpp Line 210:
memcpy(&items[0].data[7 + 70 * i], "Nintendo RVL-CNT-01-TR", 22);

IOWin.cpp Line 130:
static int PID[3] = {0x0330, 0x0002, 0x00F7};

IOWin.cpp Line 460:
const std::wregex wiimote_device_name(L"Nintendo RVL-\\w{3}-\\d{2}-TR");

WII_IPC_HLE_Device_usb.cpp Line 65:
const char * wmName = "Nintendo RVL-CNT-01-TR";

WII_IPC_HLE_WiiMote.cpp Line 47:
, m_Name("Nintendo RVL-CNT-01-TR")

WiiMote_HID_Attr.cpp Line 57:
u8 ServiceName[] = { 0x25, 0x13, 'N','i','n','t','e','n','d','o',' ','R','V','L','-','C','N','T','-','0','1','-','T','R' };

WiiMote_HID_Attr.cpp Line 59:
u8 ServiceDescription[] = { 0x25, 0x13, 'N','i','n','t','e','n','d','o',' ','R','V','L','-','C','N','T','-','0','1','-','T','R' };

WiimoteRealBase.h Line 38:
#define WM_CMD_RUMBLE                0x11

Those are where old remote values are that we know of. Changing these as above results in the Wiimote pairing and rumble working.

Again, I wish I had more time to sink into this. I had time and then I took on a few projects that turned into nightmares so it's crunch time at work for me with no clear end in sight. I'll continue to do what I can when I can though!

---

KTroopa - Sorry if that's not what you were asking. I posted and then realized that might not be what you were getting at.

If you want you could pull the device properties one by one and put them into a text doc and post it up like this:

http://pastebin.com/UTi8H1CK (This is the TR version)

TO access this info, pair the WiiMote with windows first, then go Start -> Devices and Printer -> Right-Click on the WiiMote and select Properties -> Hardware tab -> Properties (at the bottom) -> Details tab. Here there is a drop down that allows you to see all the properties of the device.

I copied every property out which isn't completely necessary.

[Xtreme2damax]

It would be nice for the actual developers to look into this issue and fix it for some of us that bothered to spend money on actual hardware unlike others that are able to play with emulated controls. Are any of the developers working on this issues? I think those that posted in this thread so far aren't developers so guesswork isn't going to fix this, the developers are the only ones that have the tools and skill to investigate and fix this issue. I keep checking back hoping for a solution as I'd like to play with the real controls, the emulated controls while manageable just isn't practical and requires a lot of patience.