RVL-CNT-01-TR controller support bounty

[isaacwaller]

I'm sure everyone is familiar with the unfortunate state of RVL-CNT-01-TR support on Windows. Since all new Wiimotes being produced are of the RVL-CNT-01-TR variety, I think this is a real shame and something that really should be fixed. Unfortunately I don't have enough time to fix it myself, I am not very familiar with the Win32 Bluetooth API and do not have much time to devote to open source projects. For this reason I would like to create a small bounty of $400 for any developer who is able to fix RVL-CNT-01-TR support on the Microsoft Bluetooth stack.

I pledge to send $400 USD to any developer who can make pairing and connecting to a RVL-CNT-01-TR Wiimote just as simple as it is to connect to a standard Wiimote. The user should not have to install any other bluetooth stack - it should work with the built-in Microsoft Bluetooth stack and drivers. I can send the money through bitcoin or PayPal, whichever is easier for you.

I hope this is not against the forum rules, please let me know and I will remove the post immediately. But I really hope someone takes me up on this offer

Thanks again to all Dolphin contributors who have created an amazing piece of software.

[DJBarry004]

In my opinion, that problem sould be solved by Microsoft since it´s the one who develops Windows´ BT stack. Meanwhile, try Toshiba´s instead since it gives better results... for now.

[mbc07]

As far as I know, the -TR Wiimotes enforce authentication now (compared to the non-TR ones) and MS stack just can't pair them correctly, so they don't work. Someone in the issue 5011 also said that a real solution would be writing a Wiimote driver to get Dolphin communicating with it directly, but I'm unsure if a driver would fix this...

[MayImilae]

The problem is that the MS bluetooth is crappy: it doesn't support all of the bluetooth spec. And something in the bit that MS excluded is used by the -TR wiimotes (this was likely deliberate by Nintendo). The Toshiba, Linux, and OSX bluetooth stacks support the full bluetooth spec, and so they work just fine right out of the box. Only the MS bluetooth stack that has this problem.

Billiard is the definitive answer on all this of course (this information came to what I remember from talking to him about it), but from what I understand there is no way to make the MS bluetooth stack support this. The only answer is some sort of driver or alternate bluetooth stack. Considering that it's only the MS bluetooth stack that has this issue, currently the Dolphin devs believe this really isn't Dolphin's problem, and aren't looking for a fix.

[tueidj]

Nintendo didn't do it deliberately, a wii communicates with -TR wiimotes in exactly the same way as it always did with non -TR wiimotes. It was other software (wiimote libraries, wii homebrew) that was doing things wrong all along... and they still don't behave the same as official software, for example libogc doesn't force authentication which means pressing the power button on a wiimote doesn't trigger a hardware power button press like it should.

[velo]

I think this is good thread / idea because the whole issue downgrades the worth of dolphin and emulation in general really hard.

-.-.-