Emulator Issues #5011 Wii Remote Plus and Some 3Rd-Party Wii Remotes Do Not Work on Windows 11/20/2011 10:57 PM - Greg

Emulator - Emulator Issues #5011 Wii Remote Plus and some 3rd-party Wii Remotes do not work on Windows 11/20/2011 10:57 PM - greg

Status: Fixed % Done: 0% Priority: Normal Assignee: Category: Controls Target version: Operating system: Windows Relates to No performance: Issue type: Bug Easy: No Milestone: Relates to No maintainability: Regression: No Regression start: Relates to usability: No Fixed in: Description New Wii Remote Plus (built in MotionPlus) does not function correctly with Dolphin.

Shows up as "RVL-CNT-01-TR" bluetooth device.

The PID of the new controller is 0x0330, compared to 0x0306 for the old Wiimote. I tried modifying the code, it detects the device but doesn't actually work. Nintendo probably changed the communication protocol slightly.

Latest SVN pull with code changes tried. Related issues: Has duplicate Emulator - Emulator Issues #4833: 3rd party Wiimote do not work... Duplicate Has duplicate Emulator - Emulator Issues #5143: RVL-CNT-01-TR on Linux doesnt... Duplicate Has duplicate Emulator - Emulator Issues #5248: Wiimote with built-in motion ... Duplicate Has duplicate Emulator - Emulator Issues #5820: Wiimotion Plus Inside (Black)... Duplicate Has duplicate Emulator - Emulator Issues #5913: Wiimote plus not connecting a... Duplicate Has duplicate Emulator - Emulator Issues #5961: Wii Motion Plus cant connect Duplicate Has duplicate Emulator - Emulator Issues #6030: Dolphin says wii mote is conn... Duplicate Has duplicate Emulator - Emulator Issues #6314: Wiimote connection issue Duplicate

History #1 - 11/21/2011 04:11 AM - eodeth My Wii Remote Plus works fine... the only problem (with anything it uses, such as Dolphin or GlovePIE) is that the motionplus sometimes isn't detected, specifically if the Wiimote isn't laying flat (The calibration screen for video games never pops up). Not until you restart the program trying to detect it will it start to work again.

#2 - 11/21/2011 04:15 AM - greg I think what I have is a newer generation controller. Does yours say "RVL-CNT-01-TR" and is the VID/PID pair end with 0x330? I bought the controller today.

The old controllers are 0x0306 and "RVL-CNT-01".

#3 - 11/21/2011 04:23 AM - eodeth Mine is RVL-CNT-01, I got my wiimote last month. I'm not sure of how to check the VID/PID. I also live in the USA (it's possible that can change something...)

10/01/2021 1/32 After a short search of the internet, the only four things involving "RVL-CNT-01-TR" are posts you've made...

#4 - 11/21/2011 04:28 AM - greg I am also in the USA. There are few other posts about the "RVL-CNT-01-TR".

Refer here: http://forums.dolphin-emulator.com/showthread.php?tid=19948

This guy got it in Japan, though. Figure it was about time for a newer revision to hit the US.

#5 - 11/21/2011 05:18 AM - lpfaint99 What is the VID of the PID 0x330, Is it 0x057E? try changing the wiimote name here, I don't have one of these wiimotes otherwise i would test, keep in mind that after these changes you should use a new sysconf file just for this test build search "Nintendo RVL-CNT-01" in dolphin source WII_IPC_HLE_Wiimote.cpp m_Name("Nintendo RVL-CNT-01") WII_IPC_HLE_Device_usb.cpp const char * wmName = "Nintendo RVL-CNT-01"; SysConf.cpp, and wiimote_real.cpp

#6 - 11/21/2011 12:37 PM - greg Yes, the VID is the same. I will try these changes after work and report back here.

#7 - 11/22/2011 12:06 AM - greg After trying the changes- Dolphin reports finding a Wiimote but nothing actually works. Fiddling with the Command values produced making the Wiimote rumble, but that's it (changing WM_CMD_RUMBLE to 0x11 makes rumble work). I can't get the LEDs to light up or any input to work.

#8 - 11/27/2011 03:44 AM - zhangping168 I just bought one black wii remote today,Shows up as "RVL-CNT-01-TR" bluetooth device. same issue, I am in Canada, guess this new version is coming fast to north america, please fix it, thanks, I really wanna play the new zelda

#9 - 11/28/2011 02:53 PM - brucespringsteen I really hope someone can fix it and make the new model work, I just sold my Wii and bought a new Wiimote for playing games with Dolphin and now it doesn't work anymore...

#10 - 11/29/2011 07:44 PM - knowitall599 I agree. I live in the USA and it doesn't work.

#11 - 11/30/2011 10:36 PM - javier.ruiz.garcia Got a 2-pack (blue+pink) from Japan, from Play-asia.com. -TR. Not detected by GlovePIE or the Wii Homebrew Channel =(

10/01/2021 2/32 #12 - 11/30/2011 10:37 PM - javier.ruiz.garcia Got a 2-pack (blue+pink) from Japan, from Play-asia.com. -TR. Not detected by GlovePIE or the Wii Homebrew Channel =(

#13 - 12/01/2011 10:56 AM - brucespringsteen I searched all stores nearby and no one seems to have the old ones that work with Doplhin I now bought one RVL-036 (RVL-018A / RVL-022), I dind't open it yet so I can easily return it...wanted to check with you guys if this may be a version that still works

#14 - 12/03/2011 03:32 AM - FungFlex Shit, I have been trying to get my wiimote to work for an hour, and I guess I am in the same boat. I also have a brand new wiimote, purchased today (Nintendo RVL-CNT-01-TR) and I simply can not get it to work.

#15 - 12/03/2011 08:27 PM - sexiiwhiteboy16 Having the same issue. RVL-CNT-01-TR will connect in windows but not in Dolphin. I noticed that if i change the name of the controller to RVL-CNT-01 in bluetooth devices, the device does something.. odd. Now, everytime im in dolphin and repeatedly tap the 1+2 buttons together and click pair up, windows installs new driver software. No matter how many times i do this it always installs new driver software but never pairs.

#16 - 12/03/2011 08:29 PM - sexiiwhiteboy16 Also can anyone tell me how to make the controller at least show up in dolphin?

#17 - 12/03/2011 08:55 PM - greg It doesn't matter if it shows up or not, it's not going to work. Please see this thread: http://forums.dolphin-emulator.com/showthread.php?tid=19948

#18 - 12/03/2011 09:09 PM - sexiiwhiteboy16 I know. I have been tracking all threads. But part of the problem is dolphin not even recognizing the fact that the controller exists. Read comment number 7. By adding the suggested changes in comment number 5 he was able to at least get dolphin to recognize that the controller was there. He was also able to make the wii remote rumble. It is one step closer and if anyone could provide me with the means to make those changes I would be highly gratefull.

#19 - 12/03/2011 09:14 PM - greg I'm the one that posted that. I worked with one of the devs to try and get further and there was nothing else we could do. It's simply not going to work without extensive work + testing. It's a long way off, it seems.

#20 - 12/03/2011 09:22 PM - iJohnnsen I just got one of these too and nothing works. Is there anything we can do to help? I hope this can be fixed.

#21 - 12/03/2011 09:27 PM - sexiiwhiteboy16 Sigh.. Well at least its getting attention. Thats a plus.

#22 - 12/03/2011 09:29 PM - sexiiwhiteboy16 Is there anyway I could have my own copy of the code to make changes to and test?

#23 - 12/03/2011 09:42 PM - greg Here's the changes I made (most are crude and will break original Wiimote support, as this is for testing only):

SysConf.cpp Line 210:

10/01/2021 3/32 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") let us know how you fare.

(edited for spelling)

#24 - 12/03/2011 09:48 PM - sexiiwhiteboy16 Thanks a ton. So I just create a server side clone. Type "Nintendo RVL-CNT-01" in the search trunk?

#25 - 12/03/2011 09:49 PM - greg just clone the latest revision, go into VS2010 and make the modifications i specified.

#26 - 12/03/2011 11:34 PM - sexiiwhiteboy16 By vs2010 you mean visual studio? Also, how do I clone the revision. After I clone it how do I open it and add the changes then recompile it back into the exe i can load and test?

#27 - 12/03/2011 11:42 PM - greg Yes, visual studio. http://code.google.com/p/dolphin-emu/wiki/Windows_Build

#28 - 12/04/2011 01:54 AM - sexiiwhiteboy16 I have a quick question. How did you determine to use 0x11 instead of 0x10? how did you figure that out?

#29 - 12/04/2011 02:21 AM - sexiiwhiteboy16 Btw how do i test it after I make the latest modifications?

#30 - 12/04/2011 03:06 AM - greg I just was trying different stuff. Just recompile it after making modifications? You said you can do coding stuff...are you familiar with Visual Studio at all? lol

#31 - 12/04/2011 04:00 AM - sexiiwhiteboy16 I have. But I realized I needed Windows 7.1SDK. I have 7.0, but i cant seem to get Windows 7.1SDK to install. Infact, the downloader continualy gives me an error saying the instalation failed. Untill I get it installed I cant recompile it.

10/01/2021 4/32 #32 - 12/04/2011 05:34 AM - jahrain.jackson I made those modifications and managed to get the wiimote to connect after clicking Pair Up now. But no input appears to be working.

#33 - 12/04/2011 10:07 PM - Gravedrinker Any news on this issue? Having the same problem.

#34 - 12/07/2011 10:10 PM - skidau If you can build Win32, use that for testing the wiimote code. It works the same as the x64 version.

#35 - 12/08/2011 05:47 AM - dickjohnpaul I've compiled the 32 bit release version and I can't get the new Wiimote to pair using the above changes. Any ideas? If I can get it paired at least I can start messing with the codes.

#36 - 12/08/2011 06:53 AM - dickjohnpaul I've copied all of the data out of the Device Properties. http://pastebin.com/UTi8H1CK

I don't have an original Wiimote to compare this with but some of the IDs in there might be helpful.

I'll keep poking around in the code and see if I can come up with anything. I still can't even get the damn Wiimote to pair with Dolphin.

#37 - 12/09/2011 11:03 AM - jeroenvanwamelen A warning for this issue on the main wiki page or support page would have been helpful, now I'm in the same boat as you guys :)

#38 - 12/11/2011 09:24 PM - Tom-Reich pls fix this soon! here are additional information: http://forums.dolphin-emulator.com/showthread.php?tid=19948&page=11

#39 - 12/11/2011 10:54 PM - bakatz91 Have the same problem. Bought a new, white Wiimote Plus (motion plus built in) and it was of the dreaded "TR" variety. I can get it to pair up with Windows, but Dolphin can't use it. I also noticed it fails with the latest version of the Homebrew channel.

#40 - 12/12/2011 07:42 PM - sexiiwhiteboy16 I have some new information to share with 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.

#41 - 12/14/2011 06:23 PM - Xtreme2damax Any actual developers working on this?

#42 - 12/17/2011 07:39 PM - Tom-Reich I have also uploaded the details of my Wii-RemotePlus TR vers. http://pastebin.com/gTTVMSmJ

I tried the changes suggested by rgrfreek in the forum but i cannot manage to connect it with dolphin. The only thing which happens is that the driver is being reinstalled when i click on pair-up.

10/01/2021 5/32 #43 - 12/23/2011 07:27 PM - D01000010.hacker We have Piki, the dev from WiimoteController on Android (owner of http://android.ccpcreations.com/) in the below thread who's getting one of the new motes and taking a swing at it. I'll update this thread if any significant progress is made. http://forums.dolphin-emulator.com/showthread.php?tid=19948&pid=189146#pid189146

#44 - 12/24/2011 05:59 PM - xoppabv I can confirm that the following changes work for the Wii Remote Plus (RVL-036 on packaging) identifies as 0330. It should keep "old" controller support, but not tested: IOWin.cpp, line 128: static int VIDLength = 4; static int VID[4] = {0x057E, 0x0001, 0x0002, 0x057E}; static int PID[4] = {0x0306, 0x0002, 0x00F7, 0x0330}; IOWin.cpp, line 460: const std::wregex wiimote_device_name(L"Nintendo RVL-\w{3}-\d{2}(-\w{2})?"); No additional changes needed.

#45 - 12/24/2011 07:17 PM - xoppabv Just checked another Wii Remote, which is RVL-CNT-01 (without TR) and identifies as 0x0306 (both buyed today, same packaging, so that's a bit strange). With above changes both work without any problems.

#46 - 12/24/2011 07:23 PM - rgfreek I'll check this out later today. RVL-CNT-01 is the older version of the Wiimote - it works. Sometimes stores still have a few in stock. It's a crapshoot.

We have made the above changes for the TR and we can get it to pair and rumble. Nothing else works. I'm wondering what your definition of working means? All buttons and LEDs work correctly and you can actually play games with it? Is it in fact a new RVL-CNT-01-TR WiiMote? The 0330 ID sounds correct but RVL-036 on the packaging isn't an indicator of anything.

Thanks for the input and if you have any further findings this thread is where we're discussing too: http://forums.dolphin-emulator.com/showthread.php?tid=19948

#47 - 12/24/2011 08:36 PM - xoppabv I've two motion plus remotes: one 0x0306 RVL-CNT-01 and one 0x0330 RVL-CNT-01-TR Both are working for a few hours now, tested with Wii Sports and Wii Party. I had some trouble pairing the TR (Toshiba stack), but besides that no problems. With working I mean: all buttons, vibration and pointer (using two candles, the sensor bar was sold out today). Speaker not tested yet.

#48 - 12/24/2011 10:09 PM - D01000010.hacker Hm. I'm attempting to compile the changes and getting errors like "source\core\audiocommon\src\xaudio2stream.h(25): fatal error C1083: Cannot open include file: 'xaudio2.h': No such file or directory"

It sounds like I'm missing some of the source, but I'm certainly a neophyte so I'm not sure. I'll attempt to get the source again, but would appreciate some advisement. Thanks guys, good work. :)

10/01/2021 6/32 #49 - 12/24/2011 10:37 PM - xoppabv xaudio2.h is part of the DirectX SDK, make sure to follow the instructions on http://code.google.com/p/dolphin-emu/wiki/Windows_Build. Install the DirectX SDK and set the include paths in the propery manager for both 32 and 64 bit builds.

#50 - 12/25/2011 02:22 AM - D01000010.hacker heh That took some work getting everything together, but I've managed to get it to compile and am testing syncing my TR-mote. Thank you for your help.

For starters, I'm on Win7 64bit. When running the 32bit version I attempt to pair the mote and Windows successfully installs the Bluetooth HID Driver every time. Shortly after, VS tells me that Windows cause a breakpoint in Dolphin. The Output window contains the following:

(There are many messages similar to the one below from the WOW64 directory) 'Dolphin.exe': Loaded 'C:\Windows\SysWOW64\mlang.dll', Cannot find or open the PDB file

HEAP[Dolphin.exe]: HEAP: Free Heap block 9afde0 modified at 9afef0 after it was freed Windows has triggered a breakpoint in Dolphin.exe.

And delivers the following upon continuing:

The output window may have more diagnostic information. The thread 'Win32 Thread' (0x112c) has exited with code 0 (0x0). The thread 'Win32 Thread' (0x19f8) has exited with code 0 (0x0). The thread 'Win32 Thread' (0x1b54) has exited with code 0 (0x0).

Others have had it run smoothly, so I may be doing something wrong. I'll post back with the results of my 64bit test. Let me know if you need anymore information.

#51 - 12/25/2011 02:27 AM - D01000010.hacker The 64bit test went similarly. Maybe I messed up the directories? The instructions were slightly different from the options I had available in VS2010 Pro.

Below is the results of the Output window:

(There were many errors like the one below from the System32 folder) 'Dolphin.exe': Loaded 'C:\Windows\System32\mlang.dll', Cannot find or open the PDB file

HEAP[Dolphin.exe]: HEAP: Free Heap block e93bd0 modified at e93cf0 after it was freed Windows has triggered a breakpoint in Dolphin.exe.

This may be due to a corruption of the heap, which indicates a bug in Dolphin.exe or any of the DLLs it has loaded.

This may also be due to the user pressing F12 while Dolphin.exe has focus.

The output window may have more diagnostic information. The thread 'Win64 Thread' (0xb64) has exited with code 0 (0x0). The thread 'Win64 Thread' (0x187c) has exited with code 0 (0x0). The thread 'Win64 Thread' (0xfcc) has exited with code 0 (0x0). 'Dolphin.exe': Unloaded 'C:\Windows\System32\msftedit.dll' 'Dolphin.exe': Unloaded 'C:\Windows\System32\msimg32.dll' The thread 'Win64 Thread' (0x1120) has exited with code 0 (0x0).

10/01/2021 7/32 The thread 'RPC Callback Thread' (0x10d8) has exited with code 0 (0x0). The thread 'Win64 Thread' (0x1720) has exited with code 0 (0x0). The thread 'Win64 Thread' (0xc2c) has exited with code 0 (0x0). The thread 'Win64 Thread' (0x42c) has exited with code 0 (0x0). The program '[4056] Dolphin.exe: Native' has exited with code 0 (0x0).

#52 - 12/25/2011 05:46 PM - xoppabv For your convenience you might want to check the following files. Only use this if you experience problems compiling and just want to test the changes above. http://www.xoppa.com/download/dolphin-tr-x64.zip http://www.xoppa.com/download/dolphin-tr-x86.zip It are the compiled versions I am currently using.

#53 - 12/25/2011 08:05 PM - D01000010.hacker Thanks, xoppa. I was going to give it another go today, but I had no idea what I was doing wrong. Testing now...

#54 - 12/25/2011 08:11 PM - D01000010.hacker Mine continues to try and install a "new" Bluetooth HID driver. Could you tell us more about your system xoppa? What drivers are your system using for the wiimote? You mentioned that you had some trouble pairing the mote, what exactly did you experience?

#55 - 12/25/2011 08:49 PM - xoppabv If you used the Microsoft stack before and are now trying the Toshiba stack, consider removing/disabling the bluetooth device manually using the Windows 7 device manager. Including the removal of any paired devices using the device manager. Although some paired devices are not visible in the Microsoft bluetooth manager, they might still be in the device manager (using another device name, which can make it hard to find them). After that reinstall the Toshiba stack (if your device is compatible, i'm not sure about the compatibility of the Toshiba stack, mine came with the Toshiba stack) and don't forget to reboot your system. Make sure the bluetooth device is working correctly using the Toshiba stack before you continue.

To use the TR remote follow these instructions: 1. Click to pair a new device, follow the instructions and press the 1 and 2 button on the TR remote enter discovery mode. The remote should now be listed as paired device. 2. Right click the TR and select connect, a dialog pops up. 3. Press the A button on the remote and click OK on the dialog. 4. The remote should be connected now, but no leds. Check this by pressing the A button, no leds should blink. If leds start to blink restart from 2. 5. Open Dolphin (first close if it was still open), make sure it has the code changes stated above, hit the Wiimote button and press refresh. 6. One led on the TR should light up indicating it's number and the TR rumbles. If not hit refresh again or restart from 2. The TR should now be fully functional.

The bluetooth adapter I use is the cheapest one available in the local shop: http://www.sitecom.com/micro-adapter-bluetooth-2-1-usb/p/658 The only drivers I used (besides the default Microsoft (update) drivers ofcourse): http://www.sitecom.com/download/4791/toshiba_8.htm

I had trouble pairing the TR the first few times. Using the above instructions I found it to be working. The problems I experienced ranged from the device not being listed (Microsoft stack) to pairing but no communication (Toshiba stack). Therefor in my experience you should make sure that your bluetooth device is working correctly and that the remote is paired and connected (which might be a problem) before even trying Dolphin. If unsure, use another Wii Remote tool to test (I used WiiYourself!_1.15.zip, although not thorough, use google if needed)

10/01/2021 8/32 #56 - 12/25/2011 10:16 PM - ollierohn Hi xoppa, tried your build and the toshiba drivers but I get:

SetupWiiMem: Can't find setting file

Error: Compiling at 0. LR=00000000 CTR=00000000.

I can connect both wiimotes though so cheers.

#57 - 12/25/2011 10:30 PM - xoppabv The files are not a complete installation. Copy the files over an existing installation, as the other files might be required as well.

#58 - 12/25/2011 10:35 PM - ollierohn I'm a dumbass but I worked it out, both motes working in game thanks!

#59 - 12/25/2011 11:39 PM - xoppabv Consider posting in http://forums.dolphin-emulator.com/showthread.php?tid=19948 as this issue might get out of scope. As for this issue, the developers of Dolphin might consider implementing the changes purposed by Greg in #24, perhaps slightly changed as in #50.

#60 - 12/26/2011 02:41 AM - greg I can confirm that the TR works with the Toshiba bluetooth stack.

#61 - 01/02/2012 10:48 AM - arcticzero Tried Xoppa's x64 build for Skyward Sword (from 297-dirty and r7719) so my new TR Wiimote would work. However my FPS has plummeted to the teens with this revision. Maxed out on the following hardware: i7 930 @ 4ghz Radeon 6990 @ 900/1375 12GB Dominator GT 1600's Corsair Force 3 120GB SSD

Used to be a constant 30fps on the old revisions, but back then I was only borrowing a Wiimote from a friend. Had no idea about the whole TR problem when I purchased my own. Any clues?

#62 - 01/10/2012 08:18 PM - jacobo.tarragon I've been messing with the Darwin code [1], and got Dolphin to find the new wiimote plus.

The change is really naive:

In Core/Core/Src/HW/WiimoteReal.mm :130, change

[bti setSearchCriteria: kBluetoothServiceClassMajorAny majorDeviceClass: kBluetoothDeviceClassMajorPeripheral minorDeviceClass: kBluetoothDeviceClassMinorPeripheral2Joystick ];

10/01/2021 9/32

with

[bti setSearchCriteria: kBluetoothServiceClassMajorAny majorDeviceClass: kBluetoothDeviceClassMajorPeripheral minorDeviceClass: kBluetoothDeviceClassMinorAny ];

That way the wiimote is recognized. However, the connection is dropped seconds after for no apparent reason. The output log is

52:50:647 Source/Core/Core/Src/HW/WiimoteReal/IOdarwin.mm:26 N[Wiimote]: Discovered bluetooth device at 58-bd-a3-41-a5-0d: Nintendo RVL-CNT-01-TR 52:50:658 Source/Core/Core/Src/HW/WiimoteReal/IOdarwin.mm:149 N[Wiimote]: Found 1 bluetooth device 52:51:158 Source/Core/Core/Src/HW/WiimoteReal/IOdarwin.mm:194 N[Wiimote]: Connected to wiimote 1 at 58-bd-a3-41-a5-0d 53:12:227 Source/Core/Core/Src/HW/WiimoteReal/IOdarwin.mm:214 N[Wiimote]: Disconnecting wiimote 1

Maybe the original IODarwin developers should take a look at this.

[1] http://code.google.com/p/dolphin-emu/source/browse/Source/Core/Core/Src/HW/WiimoteReal/IOdarwin.mm

#63 - 01/10/2012 08:49 PM - hatarumoroboshi The merge of the branch "Wiimote" (revision ebca41e78be5) wasn't supposed to fix this issue? Is it still valid?

#64 - 01/10/2012 08:56 PM - jacobo.tarragon #70 as far as I see in the commits, only the windows version has been addressed.

#65 - 01/14/2012 05:55 AM - enki1711 I've made a similar change on Mac Lion. The Wiimote reports as kBluetoothDeviceClassMinorPeripheral2Gamepad. It reports connected, this quickly disconnects. I've also experimented with darwiinremote. I've made similar changes and again it connects, however in that case it fails when attempting to open l2cap, openL2CAPChannelWithPSM, it fails with connection not open error.

Is there a resource which describes the protocol for the old wiimote?

#66 - 01/14/2012 09:49 AM - kitsunenomen Bought new Black Wiimote Motion Plus tonight, still doesn't work AT ALL on version 3.0-371.

#67 - 01/15/2012 04:45 PM - dannzen With this Build from [email protected]

10/01/2021 10/32 http://code.google.com/p/dolphin-emu/issues/detail?id=5011#c58 and the Toshiba Stack i got this Wiimote to work http://forums.dolphin-emulator.com/showthread.php?tid=20702 without the Toshiba Stack there was no respond in Dolphin...

#68 - 01/15/2012 07:37 PM - kitsunenomen I can confirm that you NEED Toshiba Stack to get it to work, since my new TR model motion plus only works on build 3.0-371 with Toshiba Stack.

#69 - 01/15/2012 07:39 PM - jacobo.tarragon Good enough for windows users… This issue should be marked as confirmed.

#70 - 01/17/2012 03:36 AM - parlane issue 5143 has been merged into this issue.

#71 - 01/17/2012 03:20 PM - hoydor24 not good enough, not every bluetooth works with toshiba stack

#72 - 01/17/2012 03:44 PM - rgfreek @78 You could always spend the 20 bucks on a new dongle? If this isn't a good enough fix for you then fix the program yourself or wait for the devs to do it.

This is an open source, freeware project. No one is getting paid and no one owes you anything, it's up to all of us to come up with these fixes and workarounds. We aren't the devs of this software, just users with ideas.

So this IS good enough for the time being.

I moved across the country and my Wiimote is being shipped to me. I need to get a new BT adapter that will work with the Toshiba stack too. I'll report back with some in depth instructions on how I personally got it working whenever I get my Wiimote and the new BT adapter. I know using a separate BT stack can be challenging for inexperienced Windows users stuck with the default drivers. I just want to verify for myself this all works, which from what I'm reading it does.

#73 - 01/17/2012 04:18 PM - D01000010.hacker @79, it does. I use it constantly. I'm still trying to learn enough C to help, but haven't had much time. I have yet to try the change that suggests the Windows stack might be able to work too. Since I have a trial of the Toshiba stack, I'll probably be testing that soon and will post back.

Cheers!

#74 - 01/17/2012 04:46 PM - rgfreek @80 Unfortunately I think making the Windows drivers work will require an update from MS. We've done a lot of hacking as you are aware of and it seems that the Windows drivers just aren't gonna cut it with these new WiiMotes. We'll see though.

Good on you for diving into C and trying to help with this. That's how these things get fixed. Thank you.

I'm excited to hear your results. I don't get my Wiimote until next week, maybe later so I can't test yet. :(

10/01/2021 11/32 I'd also like to thank xopp for the major headway he's made so far in this. I feel like he's responsible for the fix we currently have. I NEED MY DAMN WIIMOTE!

#75 - 01/17/2012 07:42 PM - enki1711 FYI, regarding getting this wiimote to work on Mac. I have been able to modify the darwiinremote framework to talk to this wiimote by changing the minor device class to 2 vs. 1. I tried the same thing with Dolphin and it still would NOT connect, but it does connect with darwiinremote framework. I haven't investigated the differences. There are some intentional delays inserted intot he darwiinremote code. In the dolphin code I modified, it was able to find the wiimote, but when attempting to open the first l2cap channel, it fails saying the connection isn't open. This same call works in darwiinremote. I'm able to open both l2cap channels. It works reading the state of all buttons on the wiimote. I have NOT been able to get the accelerorometer to report. I also cannot get lights to work. Pretty much only the buttons report correctly. I've also seen that some commands sent out starting with 0x52 work fine. I had seen someone reporting that they didn't work with this wiimote.

#76 - 01/17/2012 11:39 PM - hoydor24 @79 what you are implying is uncalled for. I am just saying its too early to mark this as confirmed. please stop judging people, you know nothing about me, thanks. cheers.

#77 - 01/17/2012 11:44 PM - skidau "Confirmed" as in an acknowledged issue, not as a confirmed fix.

#78 - 01/18/2012 12:35 AM - hoydor24 oh, then it seems that i have misunderstood @76. The status naming is a bit different from where i work at, my bad.

#79 - 01/19/2012 08:09 PM - basi.onur Hello guys :) Managed to connect the RVL-CNT-01-TR with Dolphin 3.0.373 , running under Ubuntu 12.04 (64bit) (using 3.2.0.9 kernel) just changed following class numbers in /HW/wiimote Real/IONnix.cpp

// Identify the wiimote device by its class #define WM_DEV_CLASS_0 0x08 #define WM_DEV_CLASS_1 0x05 #define WM_DEV_CLASS_2 0x00 only problem is its disconnects after ~10 Seconds, no rumble and no Leds workin, any idea? can anyone try this with a stable kernel release??

#80 - 01/25/2012 01:32 AM - cloud1250000 come on, anyone can compile it with these class?

#81 - 01/25/2012 09:34 AM - basi.onur Replaced the Nintendo RVL-CNT-01 strings in the source with Nintendo RVL-CNT-01_TR. Changed device class like above and tried with -> ubuntu 10.04 - 2.6.xx Kernel with Bluez 4.97 /96/95/94. 4.98 reports error while compiling. here is the Dump, maybe a Bluez problem?

10/01/2021 12/32 < HCI Command: Inquiry (0x01|0x0001) plen 5

HCI Event: Command Status (0x0f) plen 4 HCI Event: Inquiry Complete (0x01) plen 1 < HCI Command: Inquiry (0x01|0x0001) plen 5 HCI Event: Command Status (0x0f) plen 4 HCI Event: Inquiry Result (0x02) plen 15 HCI Event: Inquiry Complete (0x01) plen 1 < HCI Command: Create Connection (0x01|0x0005) plen 13 HCI Event: Command Status (0x0f) plen 4 HCI Event: Connect Complete (0x03) plen 11 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 HCI Event: Command Status (0x0f) plen 4 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 HCI Event: Read Remote Supported Features (0x0b) plen 11 < ACL data: handle 1 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 HCI Event: Command Status (0x0f) plen 4 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 1 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x0000 < ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 17 scid 0x0040 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 1 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x5040 scid 0x0040 result 1 status 2 Connection pending - Authorization pending ACL data: handle 1 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x5040 scid 0x0040 result 0 status 0 Connection successful < ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x5040 flags 0x00 clen 0 ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0 < ACL data: handle 1 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x5040 flags 0x00 result 0 clen 4 MTU 672 HCI Event: Remote Name Req Complete (0x07) plen 255 ACL data: handle 1 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0 Success < ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 19 scid 0x0041 HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 1 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x5801 scid 0x0041 result 1 status 2 Connection pending - Authorization pending ACL data: handle 1 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x5801 scid 0x0041 result 0 status 0 Connection successful < ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x5801 flags 0x00 clen 0 ACL data: handle 1 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0 < ACL data: handle 1 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x5801 flags 0x00 result 0 clen 4 MTU 672 HCI Event: Number of Completed Packets (0x13) plen 5 ACL data: handle 1 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0 Success < ACL data: handle 1 flags 0x02 dlen 8 L2CAP(d): cid 0x5040 len 4 [psm 17] HIDP: Set report: Output report < ACL data: handle 1 flags 0x02 dlen 7 L2CAP(d): cid 0x5040 len 3 [psm 17] HIDP: Set report: Output report HCI Event: Number of Completed Packets (0x13) plen 5 < ACL data: handle 1 flags 0x02 dlen 7 L2CAP(d): cid 0x5040 len 3 [psm 17] HIDP: Set report: Output report HCI Event: Number of Completed Packets (0x13) plen 5

10/01/2021 13/32 HCI Event: Number of Completed Packets (0x13) plen 5 < ACL data: handle 1 flags 0x02 dlen 7 L2CAP(d): cid 0x5040 len 3 [psm 17] HIDP: Set report: Output report < ACL data: handle 1 flags 0x02 dlen 8 L2CAP(d): cid 0x5040 len 4 [psm 17] HIDP: Data: Input report HCI Event: Disconn Complete (0x05) plen 4

#82 - 01/29/2012 12:03 AM - adlr basi.onur: Can you try sending commands on in_sock (rather than out_sock; change is at the end of IONix.cpp inside Wiimote::IOWrite()) and in WiimoteReal.cpp, change all (I think there are two) instance of "0x52" to "0xa2"

I don't have a machine to try it on, but that may get it working.

#83 - 01/29/2012 01:52 PM - basi.onur sorry selled my device yesterday and bought me the golden one with the zelda pack!

This one works fine with my 3.2 kernel and ubuntu 12.04..

Sorry again, maybe i can borrow me the 01-Tr from a friend.

#84 - 01/29/2012 03:38 PM - enki1711 I tried a2 vs 52 on a Mac with darwiinremote framework. It did not work with a2, 52 still seemed to work better indicating that earlier reports that 52 commands didn't work is inaccurate. With darwiinremote framework I have been able to get buttons to be recognized, but so far tracking isn't working. I haven't focused on it much since I bought an old wii remote that I've been able to get working with dolphin.

#85 - 01/31/2012 04:13 AM - adlr enki1711:

I was able to get darwiinremote working w/ the new wiimote. There are a few changes you need to make in WiiRemoteFramework:

in WiiRemoteDiscovery.m, look for "minorDeviceClass". It's currently set to 0x01. Change it to 0x02. That will make it find the new wiimote. Same file, look for "[_inquiry setInquiryLength:" and set the length to 4 (I think it was 20 before). This is how many seconds it will scan for the wiimote. 20 was way too long which caused the wiimote to timeout. Next, in WiiRemote.m, look for "[_cchan writeSync:buf length:length]" and change _cchan to _ichan . This is because the new wii remote needs to have commands sent on the interrupt channel, not the control channel. Finally, same file, look for "buf[0] = 0x52;" and change 0x52 to 0xa2. This is because the new wiimote require 0xa2 as the first byte in each command; it won't work with 0x52 like the older model did.

Good luck! When you run the app, press the red button on the wiimote, then click "Find Wiimote" button in the mac app.

10/01/2021 14/32 #86 - 02/09/2012 07:57 PM - adlr - Status changed from New to Accepted

This issue is fixed for Mac OS X on the master branch. Linux and Windows still have the issue.

#87 - 02/09/2012 11:08 PM - enki1711 I just cloned the current source tree, built and tested on Mac OS X. It doesn't seem fixed to me. What change was made?

The wiimote is detected, but nothing works.

#88 - 02/09/2012 11:19 PM - adlr The specific change was: http://code.google.com/p/dolphin-emu/source/detail?r=c9dfcf8cf7d500d58cd8f2b375be123f5b99bb52

Did you use the red button on the back of the wiimote? Did you make sure it was configured to use a real wiimote?

#89 - 02/10/2012 12:23 AM - enki1711 I verified the code I have does include that change. I've never (successfully) used a wiimote on Dolphin.

Steps I'm doing are: - Select Wiimote on the toolbar. - On the dialog, selected "Real Wiimote". - I then hit the red button on the back of the wiimote, then press the "Refresh" button in the dialog. - Dolphin reports 1 connected (sounds good so far). - the wiimote keeps flashing all lights. It doesn't connect as any particular wiimote. - I start an app (channel), potc. - If I press the A button, all lights flash. Nothing happens on the channel (app) in dolphin. - Wiimote menu still reports 1 connected.

#90 - 02/10/2012 12:26 AM - parlane enk, what wii remote do you have? Is it even a TR model ?

#91 - 02/10/2012 12:34 AM - enki1711 Z-C4 Complete label says LMA-RVL-WR/Z-C4 007WWCUL0716 RVL-036

Its a white wii remote plus from Walmart.

Bluetooth preferences identifies it as Nintendo RVL-CNT-01-TR Major class 0x5 Minor class 0x2 Product id 0x0330 Vendor id 0x057e

10/01/2021 15/32 #92 - 02/10/2012 12:40 AM - adlr enki1711: I can help debug this tonight (california time). For reference, if you go into your source tree, what is the output of: git log -n 1 --pretty=short

Thanks, -andrew

#93 - 02/10/2012 12:44 AM - enki1711 commit c9dfcf8cf7d500d58cd8f2b375be123f5b99bb52 Author: Andrew de los Reyes <...>

Add Support for Wii Motion Plus INSIDE Wii Remotes on Mac OS X.

#94 - 02/10/2012 12:58 AM - adlr Thanks. I'll be on gchat tonight and try to work on this. My gchat acct is "adlr". Ping me if you can help.

Thanks

#95 - 02/10/2012 06:15 AM - adlr I talked w/ enki1711 tonight. By making the changes in comment 93, he was able to get darwiinremote to work, provided that he removed the Wiimote from the bluetooth prefs pane in the System Prefs.

He was able to get Dolphin work once out of many times, and we're not sure exactly why it was sometimes working, sometimes failing.

While he is on 10.7 (Lion) and I'm on 10.6, I tried my 10.7 system and it worked reliably, so OS version here doesn't seem to be the issue.

#96 - 02/10/2012 09:37 PM - sorogoli Hey guys i think i have a issue here, my wiiremote does have the wii motion plus insite, but it's code is RVL-003, is that possible, i have a lot of problem with it on game that use the motion plus feature, but other like metroid prime 3 run like a breeze, can anyone help me with that?

#97 - 02/11/2012 05:24 AM - adlr sorogoli: Unfortunately that looks like a 3rd party Wii Remote, which is distinct from the official ones this Issue is about.

#98 - 02/18/2012 03:41 AM - audvare Have the RVL-036 and trying to use on Linux with latest revision.

It blinks, then pairs, but the first player LED goes on at random. 9 times out of ten the controller rumbles to indicate connection but the first player LED does not turn on.

One way I've gotten the first player LED to stay on is to pair it at the same time as my regular Wiimote (RVL-003). But this does not mean it works. Once I start a game, the buttons on the remote do nothing.

Zelda thinks there is nothing connected.

10/01/2021 16/32 #99 - 02/20/2012 05:48 AM - Todd.Elvers Ok, so I got this to work with the RVL-CNT-01-TR wiimote and Dolphin x64, but there was a bit of work involved. This is just a summary of what I did, and since I was unable to find one post with most of the relevant facts about this issue, I figured I'd share what I found.

I'm fairly sure that inability to use RVL-CNT-01-TR, in my case and possibly most cases, was due to two main issues: 1.) Dolphin's inability to recognize the RVL-CNT-01-TR wiimote 2.) Microsoft stack's inability to recognize/receive input from the RVL-CNT-01-TR wiimote

Summary of what I did: 1.) Installed the Toshiba bluetooth stack.

If you've been trying to get your RVL-CNT-01-TR wiimote to work for a while, chances are you've tried installing the Toshiba stack. If you were successful, then you've already completed this step. If not, chances are your device is not supported by the Toshiba bluetooth stack software. The good thing is, "compatible" here just means whether or not the device in question is listed in the tosfrusb.inf or not. So, if you haven't guessed it already, you can simply modify this file to make your device compatible.

Tutorial here: http://forums.dolphin-emulator.com/showthread.php?tid=19948&page=22

2.) Downloaded & modified the Dolphin source code.

This isn't trivial, and you'll need Microsoft Visual Studio 2010, the DirectX SDK, and the Windows SDK. (I recommend, though I haven't tried, to use xoppa's builds first. People have claimed his builds have the necessary files changed for the TR wiimotes to work. If you can connect your wiimote like I did in step 3, then simply download the binaries and run Dolphin. If you've connected your wiimote successfully, and if xoppa's build work, going to the Wiimote menu in Dolphin and pressing "Refresh" should make the wiimotes vibrate. If this works, you're good to go!) After downloading the source and setting up Microsoft Visual Studio 2010 to use the downloaded SDKs, I search all the files for the string "RVL-CNT-01" and, where I found it, changed it to "RVL-CNT-01-TR", then recompiled. Downloading and configuring Dolphin source: http://code.google.com/p/dolphin-emu/wiki/Windows_Build Xoppa's modified Dolphin binaries: http://code.google.com/p/dolphin-emu/issues/detail?id=5011#c58

3.) Paired the wiimotes.

This step is relatively straight forward if you have the Toshiba bluetooth stack installed: - Open "Bluetooth Settings" and click "New Connection" - Choose express -> press next, press 1+2 on wiimote while the bluetooth software searches for the wiimote - Once it detects your wiimote, just hit next till the connection wizard closes (if it asks, choose to connect without a passkey) - Now "Nintendo RVL-CNT-01-TR" should appear in your "Bluetooth Settings" window - Right-click "Nintendo RVL-CNT-01-TR" and press connect, but do NOT press the OK button on the following prompt - Press A on your wiimote (the lights will begin to flash) and right after you press A, click OK on the prompt - If you connected it correctly, the wiimote lights will stop flashing and the prompt will disappear. - Open Dolphin -> Options -> Wiimote Settings, click "refresh" and the wiimote(s) should vibrate + light up indicating which player the wiimote is tied to

Note1: I never used the "Pair Up" button in the Wiimote Settings to get my wiimotes to work and actually when I do press it, it yaps about being incompatible with anything but the Microsoft bluetooth stack (which is obviously not true) Note2: To connect multiple wiimotes, just preform step 3 multiple times. Note3: I'm using Windows 7 x64, two TR wiimotes with nunchucks, a duracell wireless wii sensor bar, and the bluetooth adapter listed in the forum post link from my first step. Note4: Since you modified the driver yourself, when you have your bluetooth adapter plugged in and your computer goes to sleep and then wakes up, it will think the bluetooth adapter isn't installed right for a second. You can ignore this (and the respective error in device manager) because the Toshiba bluetooth software will still function fine.

10/01/2021 17/32 #100 - 02/20/2012 05:57 AM - Todd.Elvers I haven't read the posts that were made since I did my initial research into this topic and found this thread, so I my have posted redundant information.

I'll check back in a few days, please post any questions/comments and I'll try and respond as best I can. Otherwise, good luck on your Wii efforts and thanks to the Dolphin team for creating such an amazing piece of software. Truly inspiring.

#101 - 02/22/2012 10:56 PM - scientificraver Method in Comment 107 is perfectly working with Dell XPS17 Intel(R) Centrino(R) Advanced-N 6230 Bluetooth, Toshiba Stack and RVL-CNT-01-TR.

Step 2.) Downloaded & modified the Dolphin source code. is not required as normal unchanged 424 build also works without any problems.

#102 - 02/28/2012 03:35 PM - scientificraver 4 clicks (maximize - Wii-Menu - Refresh - Close) needed could be saved by letting Dolphin automatically refresh all real remotes on program startup.

If this is not done, Wiimote will not work.

#103 - 03/08/2012 06:31 AM - PMJames2010 My problem isn't with Dolphin, it's solely a Bluetooth issue.

I have a Cirago BTA-6210 V2.1. Link here: http://cirago.com/wordpress/products/bluetoothadapters/bta6210/

It worked great at first with the Toshiba stack, and then it started losing sync while playing a game. After that it got worse and worse, until now it only syncs for 1 or 2 seconds before losing sync again, if it even syncs at all. A few days ago, I tried it, and it worked for an entire gaming session. The next time I tried, it was right back to the same problem again. If I try deleting it from the stack and re-pairing, it will detect the wiimote, but fail registration several times. After many attempts it will randomly decide to add it. But being added and connected are two different things. Also, the bluetooth assistant auto-search will not work at all.

This adapter works perfect with phones and laptops. I tried the Microsoft stack, and versions 7, 8, and 9 of the Toshiba stack. (The dongle came with Toshiba stack 7) Version 9 FOUND HERE: http://www.station-drivers.com/page/Toshiba.htm

The Widcomm stack wouldn't install at all. I tried manually adding the dongle's hardware ID during install with the guide found in Comment 107. I tried the custom compile of Dolphin also found in Comment 107, but I'm sure my problem lies with the Bluetooth stack and not Dolphin. I searched and searched and tried everything I can think of except different dongles.

So, I ordered 2 additional dongles that should be here soon. Both were declared working on win 7 64 by the compatibility list. This list is for wiibrew, and it's outdated, but it's the best we have. List here: http://wiibrew.org/wiki/List_of_Working_Bluetooth_Devices

If I find a dongle that works with the new remote I'll update here.

I posted on the Official Nintendo forums and got this response: http://techforums.nintendo.com/message/61496#61496

10/01/2021 18/32 #104 - 03/08/2012 06:52 AM - PMJames2010 Amazon is currently selling both versions of the wiimote. Look at the buttons that say, EDITION: Previous Model / Newer Model. Newer Model is RVL-CNT-01-TR.

Amazon link: http://www.amazon.com/gp/product/B0045FCKVI/ref=oh_o00_s00_i02_details

#105 - 03/08/2012 05:58 PM - alucryd Works perfectly fine here on Windows 7 & 8 x64 with the Toshiba stack, however still no luck on Linux (ArchLinux x64). When you say you don't support the way new kernels handle wiimotes, does it mean you will never support it or are you planning to work on it? the new userspace driver xf86-input-xwiimote seems to be going well, only problem, I still haven't found a way to pair my wiimote without a code (bluez and blueman don't allow that).

#106 - 03/09/2012 03:17 AM - PMJames2010 It would be helpful if everyone who has a confirmed working RVL-CNT-01-TR posted which bluetooth dongle, stack, and OS they are using. Many of the issues lie purely with bluetooth.

#107 - 03/09/2012 12:12 PM - scientificraver TR-Version works fine with Toshiba stack (I use 8.00.02 but 8.00.14 is the latest) in Win7x64. You maybe have to mod the stack to recognize your bloototh dongle using the link provided above. Intel integrated Dongles are recognized without any changes.

Afterwards you just need to pair the devices within Toshiba stack connection manager on every boot-up. In Dolphin you then just need to click on Refresh within the wii menu. The Connect button does not work and is not required for TR Wiimotes.

You do not need a modified Dolphin, 424 or newer dev build should do it. The developers are currently discussing to revert TR-Support on MacOS and replace it with a newer version, windows version might also be affected by this change.

#108 - 03/09/2012 12:24 PM - scientificraver Update on how to reconnect a TR remote using Bloototh stack in Windows.

1. Open Toshiba Bluetooth settings. 2. Right-click on Nintendo TR Wiimote -> Connect 3. Press the A-Button on Wiimote (not sync button) 4. Click on OK 5. Open Dolphin real Wiimote settings and click on Refresh

#109 - 03/09/2012 03:59 PM - adlr As far as Mac/Linux are concerned, the current state of the world is:

Mac: -TR Wii Remotes should work, but older ones don't. The fix I'm considering is the top 3 patches from: http://code.google.com/r/adlr-mplus/source/detail?r=c274d71a3fe427fabead45df10eb021715d9844e&name=wiimotenix . Unfortunately, there are build/toolchain issues to resolve on the Mac platform first, which I'm actively working through (please discuss in a separate Issue from here). Linux: -TR Wii Remotes do not work, but those same top 3 patches from the link above /should/ get them to work, but I haven't tested.

10/01/2021 19/32 #110 - 03/10/2012 06:42 PM - jesusmgh Ubuntu 11.10 amd64 here.

It works with your latest code (from your above comment, ALL patches, not only the first 3) and adding the correct device class to IONix.cpp as stated some comments above:

// Identify the wiimote device by its class #define WM_DEV_CLASS_0 0x08 #define WM_DEV_CLASS_1 0x05 #define WM_DEV_CLASS_2 0x00

Haven't tested very thoroughly though.

#111 - 03/13/2012 04:19 PM - LTHoneycutt3 I've been trying to get a direct answer with all of this. Does the RVL-CNT-01-TR work out of the box with Dolphin? Or does it require:

1) A certain bluetooth adapter (I have Anycom USB-200 as verified on WiiBrew) 2) A hack of bluetooth drivers/software? 3) A specially compiled Dolphin to communicate with the new device?

Windows 7 Ultimate 64-Bit

#112 - 03/13/2012 04:22 PM - PMJames2010 Most of the dolphin issues have been worked out. BUT, the TR wiimote DOES NOT WORK with all bluetooth adapters. I've been looking for a list of confirmed working adapters as well, but there it doesn't exist yet.

#113 - 03/13/2012 04:25 PM - PMJames2010 @scientif, what bluetooth adapter are you using? I've tried the toshiba stack and every other stack there is. My adapter just won't cooperate.

#114 - 03/13/2012 04:49 PM - D01000010.hacker There is a lot of documentation of this issue on the forums and in this very thread. You should be able to find what you need to get it working by simply reading it all. Please read the whole thread and any link in it. If you have Win7x64 and a dongle that works with the Toshiba stack, it should work fine once you make the proper changes to the source code.

Please stop posting for help here. If you have input on the workings (or lack of) on the issue, feel free to post.

#115 - 03/13/2012 04:56 PM - goodrichj Changes to source code are NOT necessary using recent versions of Dolphin.

#116 - 03/14/2012 12:01 PM - scientificraver on Windows:

1) A certain bluetooth adapter Is not required, any adapter should work. But not all adapters will be compatible with Toshiba stack by default, you maybe have to mod the drivers to

10/01/2021 20/32 make it compatible (which should be easy to do)

2) A hack of bluetooth drivers/software? If your adapter is not compatible by default you have to mod (update setup configuration files to integrate your adapter) Toshiba stack as stated above.

3) A specially compiled Dolphin to communicate with the new device? is not required, but you should use a current development build, such as 424 or above

#117 - 03/15/2012 01:05 PM - scientificraver Can anyone confirm that multiple real TR-Wiimotes are also working?

I'd like to be sure before buying a 2nd one since currently the connect button does not work with TR-remotes. And can Bluetooth handle more than 1 devices being paired at the same time?

#118 - 03/17/2012 06:17 AM - adlr jesusmgh and mac/linux users: can you test this commit? http://code.google.com/r/adlr-mplus/source/detail?r=8fac488c591377e1381cec529824f5c53c588bbf&name=macbuild_wiimotefix

It should get both types of wiimote working on Mac and Linux.

To build: mkdir output && cd output && cmake .. && make -j2

Thanks,

#119 - 03/17/2012 05:22 PM - AFGsviMz I tried macbuild_wiimotefix branch. After pairing, dolphin tells me there is a connected wiimote. However the wiimote does not buzz and does not seam to be connected, since all four channel buttons are still flashing. After a short moment dolphin crashes.

Ubuntu 11.10 3.0.0-16-generic #29-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

IONix.cpp:123 N[Wiimote]: Found wiimote 1, (2C:10:C1:54:F0:41). IONix.cpp:171 N[Wiimote]: Connected to wiimote 1.

IONix.cpp:192 N[Wiimote]: Disconnecting wiimote 1. terminate called after throwing an instance of 'std::system_error' what(): Resource deadlock avoided Aborted

10/01/2021 21/32 #120 - 03/18/2012 10:14 PM - mhecher how did you managed it to connect the tr to the pc? when using windows, it can be done with the toshiba stack, but what did you use in linux? i can't even connect. so "connected to wiimote 1" would never appear. thanks

#121 - 03/21/2012 09:21 PM - scientificraver Here is the log output from build 484 with real TR-Wiimote on win64. As mentioned before everything works perfectly fine using the Toshiba stack method and refreh button from wiimote menu. The connect button does not work but is not required for a single wiimote.

11:33:755 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000001 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000001 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000017 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000017 11:33:755 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 11:33:795 Src\HW\WiimoteReal\IOWin.cpp:276 N[Wiimote]: Connected to wiimote 1.

#122 - 03/22/2012 05:26 PM - scientificraver With "connect button", the "pair up" button was meant. When I click on pair up, I get the following log entry because of using Toshiba stack:

21:30:537 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000001 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000001 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000017 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:390 E[Wiimote]: IOWrite[MSBT_STACK_UNKNOWN]: ERROR: 00000017 21:30:537 Src\HW\WiimoteReal\IOWin.cpp:217 E[Wiimote]: Unable to connect to wiimote 1. 21:30:547 Src\HW\WiimoteReal\IOWin.cpp:276 N[Wiimote]: Connected to wiimote 1. 21:45:687 Src\MsgHandler.cpp:92 E[*]: Warning: A supported bluetooth device was not found! (Only the Microsoft bluetooth stack is supported.)

#123 - 04/11/2012 01:54 PM - Grose.MatthewF Hey all wandering if there's an update on windows for the integration with dolphin for the natural sync and putting the tr's into sleep mode without using the toshiba connect then A button and then disconnecting to sleep remote? Or does anyone know how to set tr's to sleep after x amount of inactivity in toshiba bt?

#124 - 04/15/2012 04:41 AM - smilingphoenix2012 so when I did the kind of dumb thing and just tried to use the xoppa build it was able to connect to the controller, but when I went and copied the Xoppa build over the current build of Dolphin I still get the not compatible with toshiba stack problem

10/01/2021 22/32 #125 - 04/15/2012 05:39 AM - smilingphoenix2012 wait I figured it out, I hadn't set the dang thing to real wiimote. Feel worst about that one than about the entire not copying the xoppa build over a current build thing

#126 - 07/04/2012 02:23 PM - john.has.come I'm not really sure what the status of all the people's project here are, but I hope I have a lot to share.

I first bought a Belkin F8T017ng USB Bluetooth Adapter and was testing on Windows & (SP1) with a new Wii Remote Plus. I could detect the Wiimote with the standard Windows Bluetooth software, without trying any other stacks. It came up as "RVL-CNT-01-TR". I have been haunted by "TR" since. I thought my main problem was with the Bluetooth Adapter, because I noticed that no information other than the physical address of the Wiimote was detected (I expected manufacturer ID and product ID because that's what WiimoteLib.dll checks for). So, I tried several stacks and driver until I deemed it impossible. Then, I finally bought a cheaper Bluetooth Adapter by Hama. It's quite cheap.

On Windows 7, I received the exact same results as the previous Bluetooth Adapter. Damn.

So, I switched to using ArchLinux. Now I have tested the connection with lswm and wmgui. I can connect to the Wiimote just as successfully as ever with a Bluetooth manager called Blueman, however, lswm cannot detect the Wii Remote Plus and wmgui seg faults with a socket error even while handshaking with hcitool cc .

This has been quite the difficulty, and I am going to resort to one of my final ideas.

Just buy or order one of the older Wii Remotes, without MotionPlus.

Thanks everyone, I'll be around.

#127 - 07/04/2012 03:17 PM - alucryd john: My Wiimote Plus has been working using a Belkin F8T016ng with the Toshiba Stack since half a year now with no problem under Windows 7 and now Windows 8, both x64. Have you tried the Toshiba stack? My bluetooth key is the same as yours, only cheapest, so I don't see why it wouldn't work. However I have never been able to make it work under ArchLinux x86_64, which is my main OS, and that is quite a shame. The gnome bluetooth manager won't connect to the wiimote since it can't connect without pairing, and blueman can connect but won't pair without a code. And of course, dolphin doesn't see the Wimmote either way.

#128 - 07/05/2012 06:12 AM - john.has.come Well, my trouble has in-fact never been that of connecting to the Wiimote. I have used several different stacks and even two different dongle's with the same results. Using Blueman and Bluez for Arch, I have also gotten a connection.

My problem lies in using any of the already created libraries. None of them can detect Wiimotes, even when they can connect via Bluetooth perfectly fine. WiimoteLib cannot, WiimotePresenter cannot, WiimoteJ cannot, and cwiid for arch cannot.

I have gotten cwiid to connect once, with wmgui, but I received a socket error. I am quite sure that such a socket error was due to the altered structure of the Bluetooth "reports" that the new Wii Remote Plus sends. See: http://wiibrew.org/wiki/Wiimote#Control_Registers

I tried to buy an older Wiimote, with no avail. They neither carry nor produce them any longer.

10/01/2021 23/32 For today, I am going to keep searching for updated libraries. If I really need to, I will hard-code a small library of my own in C, for Linux, which shouldn't be too hard. There is a lot more documentation regarding the data the Wiimote will send and can receive compared to support for the damned Motion Plus libraries.

Thanks.

#129 - 07/05/2012 08:41 AM - john.has.come Update: Delving into the reverse engineering of the Wiimote will prove to be an overly difficult problem.

I am going to resort to one of two C-based libraries I have found. WiiC and CWiid.

Still figuring which will suit my needs better. Things are looking much brighter!

Thanks.

#130 - 09/07/2012 08:05 PM - mani.sabri Just a question for the guys who are trying to solve the problem by modifying the dolphin source or Wiimote Libs. Are you tackling the right end of the problem? Obviously the problem is solvable by installing Toshiba BlueTooth Stack so logically nothing must be wrong in the Dolphin/Wiimote libs. May be the new Wiimotes use bluetooth in a way not completely supported by the Microsoft/Bluez stack. I don't know who were the guy(s) who initially found out the problem can be solved by changing the BlueTooth stack but may be they can provide a more technical analysis of the problem.

#131 - 09/07/2012 08:08 PM - audvare I agree. The solution for Windows is not even good anyway considering it requires 3rd party libraries and could never be officially supported as I see it.

But as for other systems, I still haven't seen any solutions yet. I'm willing to try anything with my Wiimote Plus. I still just continue using my old Wiimote (and no I will not give it away for anything!)

#132 - 09/15/2012 08:23 PM - PMJames2010 After a long and exhaustive effort to get my TR Wiimotes to work,(4 different stacks, 3 different dongles, custom code, etc.) the only thing that fixed it was exchanging them for the older Wiimotes.

#133 - 11/01/2012 07:45 PM - gilles.dupeyrou Hi all, I've tested this http://code.google.com/r/adlr-mplus/source/detail?r=8fac488c591377e1381cec529824f5c53c588bbf&name=macbuild_wiimotefix as Andrew mentionned in comment 130. On Ubuntu 12.04 x86_64: The pairing is working but only with the sync button (others: A or 1+2 button does nothing) Randomly, synchronization lost after some time ( around one hour) but it is possible to play with. When synchronization lost, dolphin crash after some seconds. Hope this help, Regards

10/01/2021 24/32 #134 - 11/02/2012 09:51 AM - gilles.dupeyrou Hi again, I've tested with defautl which already contain the detect by name patch. I've just had to patch the interrupt handler for linux as made for MacOS in order to have a working RVL-CNT-01-TR under linux. regards

#135 - 12/09/2012 07:44 AM - cookiecaper ArchLinux x64, kernel 3.6.9.

It's not working here. The find-by-name patch is not mainlined; it was reverted with "incorrect logic", but I think that must have applied to another part of the patch. adlr only implemented a final working version for OS X it seems.

Trying to get this to work. The find by name allows the remote to connect here (taken out of the reverted patch). I also manually found by new dev_class ids and that also allowed connections. However, on connection there are no LEDs and no rumble. Dolphin will sometimes crash.

Dolphin seems to be crashing with a BadAlloc X error every time I start a game, so troubleshooting is difficult right now. If anyone has significant progress on this ticket, please let me know -- it'd be greatly appreciated. I am determined to get my -TR remotes working.

#136 - 12/10/2012 06:27 AM - gilles.dupeyrou Hi, I'm using this patch since weeks and no problem with but you need to pair the wiimote with the sync button, other methods leed in a crash exactely as you mentionned (withoud leds)

#137 - 12/10/2012 06:52 PM - alucryd Hi, I'm also on Archlinux x86_64, same kernel. I tried the patch and now Dolphin detects my TR wiimote. However, whenever I start a game (no crashes here) the LEDs keep flashing, there is no vibration and buttons do not work. I connected it with the sync button. I've built dolphin against this wiiuse: https://github.com/rpavlik/wiiuse, maybe that's the problem. The old unmaintained wiiuse failed to build for me, but I might look into making it work. Which wiiuse are you using ?

#138 - 12/10/2012 07:56 PM - gilles.dupeyrou As far as I know, I don't use wiiuse at all. As I said in comment 147, I've started to try the adlr branch according to comment 130. After fixing a small compilation issue (don't remember exactly but just a missing header...) the build worked fine and I was able to synchronize my wiimote and use it. In order to be closed to the official branch, I've looked into it and found that (on november the 2nd) the find-by-name patch was partially applied and made a checkout on changeset d032c40a58b84b01a98dd34a86bbff2e02dc27f2. Started with this changeset, I had to adapt source code to use the interrupt handler as done for Mac (was only for Mac). here are the files modified with my modifications: modified: Source/Core/Core/Src/HW/WiimoteReal/IONix.cpp modified: Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.cpp modified: Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.h modified: Source/Core/Core/Src/HW/WiimoteReal/WiimoteRealBase.h following the diffs:

10/01/2021 25/32 diff Source/Core/Core/Src/HW/WiimoteReal/IONix.cpp Source/Core/Core/Src/HW/WiimoteReal/IONix.cpp.orig 150,151c150,151 < if ((cmd_sock = socket(AF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP)) == -1 ||

< connect(cmd_sock, (struct sockaddr*)&addr, sizeof(addr)) < 0)

if ((out_sock = socket(AF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP)) == -1 || connect(out_sock, (struct sockaddr*)&addr, sizeof(addr)) < 0)

154,155c154,155 < close(cmd_sock);

< cmd_sock = -1;

close(out_sock); out_sock = -1;

161,162c161,162 < if ((int_sock = socket(AF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP)) == -1 ||

< connect(int_sock, (struct sockaddr*)&addr, sizeof(addr)) < 0)

if ((in_sock = socket(AF_BLUETOOTH, SOCK_SEQPACKET, BTPROTO_L2CAP)) == -1 || connect(in_sock, (struct sockaddr*)&addr, sizeof(addr)) < 0)

165,167c165,167 < close(int_sock); < close(cmd_sock);

< int_sock = cmd_sock = -1;

close(in_sock); close(out_sock); in_sock = out_sock = -1;

201,202c201,202 < close(cmd_sock);

< close(int_sock);

close(out_sock); close(in_sock);

204,205c204,205 < cmd_sock = -1;

< int_sock = -1;

out_sock = -1; in_sock = -1;

222c222

< FD_SET(int_sock, &fds);

10/01/2021 26/32 FD_SET(in_sock, &fds);

224c224

< if (select(int_sock + 1, &fds, NULL, NULL, &tv) == -1)

if (select(in_sock + 1, &fds, NULL, NULL, &tv) == -1)

230c230

< if (!FD_ISSET(int_sock, &fds))

if (!FD_ISSET(in_sock, &fds))

234c234

< r = read(int_sock, buf, MAX_PAYLOAD);

r = read(in_sock, buf, MAX_PAYLOAD);

261c261

< return write(int_sock, buf, len);

return write(out_sock, buf, len);

and: diff Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.cpp Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.cpp.orig 47c47

< , cmd_sock(-1), int_sock(-1)

, out_sock(-1), in_sock(-1)

153c153

< if (rpt.first[0] == (WM_SET_REPORT | WM_BT_OUTPUT) &&

if (rpt.first[0] == (WM_SET_REPORT | WM_BT_OUTPUT) &&

and: diff Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.h Source/Core/Core/Src/HW/WiimoteReal/WiimoteReal.h.orig 73,74c73,74 < int cmd_sock; // Command socket

< int int_sock; // Interrupt socket

int out_sock; // Output socket int in_sock; // Input socket

10/01/2021 27/32

and : diff Source/Core/Core/Src/HW/WiimoteReal/WiimoteRealBase.h Source/Core/Core/Src/HW/WiimoteReal/WiimoteRealBase.h.orig 37,38c37,38 < // channel. On Mac and Linux we use interrupt channel; on Windows, command.

< #ifdef _WIN32

// channel. On Mac we use interrupt channel; on Windows/Linux, command. #ifndef APPLE

please note that I didn't change the comment which is now wrong hope this helps

#139 - 12/10/2012 11:14 PM - alucryd You're right it seems wiiuse isn't used anymore. I've tried replacing every in_sock with int_sock and out_sock with cmd_sock (except for the last out_sock in IONix.cpp which becomes int_sock), as well as changing that ifndef in the latest git but my wiimote isn't even detected. So I tried building once again with the files from the adlr repo, but turns out it won't detect my wiimote anymore. Guess it was a once in a lifetime connection... I know nothing about this, and this is just a wild guess, but if the connect by name patch was implemented (except for the motion plus boolean it seems), shoudln't my wiimote be detected even without modifying these sockets?

#140 - 12/19/2012 07:18 AM - cookiecaper Could you post as a unified diff? Would make it a bit easier to read. To me, it seemed most of those changes were no longer necessary, but I must have missed something.

#141 - 12/31/2012 03:23 PM - atomium1 I used the information given in the foregoing posts to create the attached patch which can be applied to the current head of the master branch. This patch allows me to use the RVL-CNT-01-TR Wiimote under Linux. Already mentioned restrictions apply like having to use the small red sync button instead of just pressing buttons 1 + 2 simultaneously to get a connection. When the controller is used continuously the connection stay alive. If you don't use it it will disconnect after a few minutes. Pressing the sync button again after automatic disconnection will make dolphin-emu crash.

#142 - 01/01/2013 02:39 AM - audvare Thanks for the patch. It works well. Unfortunately I do not have a sensor bar so I could not test a game like Zelda Skyward Sword totally (but I finally got past the screen demanding a WiiMotion Plus controller; got stuck at centering the cursor due to no sensor bar).

I have included your patch in my ebuild for Dolphin. Thanks a lot. https://github.com/Tatsh/tatsh-overlay/commit/31cd845aaf50dc59999e3ee609cebaca873d1930

10/01/2021 28/32 #143 - 01/01/2013 07:30 PM - alucryd Thx a lot for the patch, works flawlessly for me. I can even connect using the 1+2 buttons. Tried Zelda SS, everything works.

#144 - 01/03/2013 05:28 PM - tylerortiz09 how do I apply the patch to my dolphin?

#145 - 01/08/2013 03:00 PM - atomium1 audvare: you can use 2 tea candles as a sensor bar replacement for testing (no joke, it only needs the IR Source). For more safety you can buy a wireless sensor bar for around €10.00. It's only IR LEDs and batteries. @tyleort...: you have to apply the patch to the source code and then compile it by yourself. The easiest way would be using Gentoo Linux and audvare's overlay :)

#146 - 01/08/2013 06:45 PM - sykopomp Applied the patch to the latest git version. Could not sync using 1+2, but the sync button method worked flawlessly. Didn't get a chance to test whether dolphin/wiimote could recover from sleeping. Successfully played skyward sword for ~2hours with no hiccups that I could see.

Will do more testing during the week and see if I can trigger any crashes.

Thanks for the awesome work! :)

#147 - 01/13/2013 12:39 AM - Billiard26 issue 5248 has been merged into this issue.

#148 - 01/17/2013 02:37 AM - joshua.baranski I would really like to use my new MotionPlus Wiimote (RVL-036) but I can't even get Windows to see it as a device, let alone get it to work with Dolphin. Any suggestions?

#149 - 01/17/2013 02:51 AM - pauldacheez Use Toshiba's Bluetooth stack (you can use this on non-Toshiba computers too). Currently it doesn't work under Windows's stack but the devs certainly have plans to fix that.

#150 - 01/17/2013 07:15 AM - smuckola This patch was essentially integrated into the main branch approximately yesterday. I checked out the subsequent git version, and tested it with essentially the same results as are listed above. I'm surprised by the person claiming to have 1+2 functionality, since nobody else seems to have that, but that's cool!

#151 - 01/17/2013 08:54 AM - Billiard26 - Issue type set to Bug - Category set to controls - Operating system Windows added

#152 - 01/17/2013 08:54 AM - Billiard26 issue 4833 has been merged into this issue.

#153 - 01/18/2013 05:05 AM - michael.brew789 I believe this illustrates the issue rather well:

10/01/2021 29/32 http://www.youtube.com/watch?v=Wkkfw7HDX8M

I recommend registered brands for testing: http://www.nyko.com/products/product-detail/?name=Wand%2B http://www.amazon.com/Wii-Remote-Controller-Black-Nintendo/dp/B001LNN3CM http://www.pdp.com/p-1151-afterglow-motion-controller-for-wii-with-motion-plus.aspx http://www.powera.com/Products/CPFA091186 http://www.memorex.com/en-us/Gaming/Gaming-Accessories/Game-Controller-for-Wii/ ebay/chinese models may not comply to quality testing

#154 - 01/18/2013 08:41 AM - Billiard26 issue 5913 has been merged into this issue.

#155 - 01/18/2013 08:47 AM - Billiard26 issue 5820 has been merged into this issue.

#156 - 01/27/2013 02:39 PM - alucryd No need for the patch anymore, seems to have been merge upstream. I can still confirm my TR Wiimote succesfully connects using 1+2 on Linux.

#157 - 01/29/2013 12:45 AM - eats777 any news on a working windows version?

#158 - 01/29/2013 02:02 AM - believeinangels88 I downloaded the Toshiba Stack and connected by bluetooth with a dongle, not the onboard on my laptop. You might have to press the sync button on the back of the remote and the 1 and 2 buttons and try once or twice but once it's connected (the icon in the Toshiba stack program will change slightly), start Dolphin and go to the controller settings. It should register the remote immediately if it is connected with Toshiba Stack and a single light should stay on instead of four flashing and the controller will vibrate.

#159 - 01/29/2013 02:52 AM - scientificraver I still can just use the A button to connect with a 100% success rate. You only need to select connect on the TR-wiimote device from within Toshibs stack first and then quickliy press A once before the time runs out.

#160 - 01/29/2013 05:23 AM - eats777 So the only way to get this to work is with toshiba's software? ugh. quite odd tho that it only works with that lol

#161 - 01/29/2013 06:39 AM - believeinangels88 Yeah, it should work though...just google Toshiba Stack and download that and it will put an icon down where the clock is on your desktop. Click on that and add the controller as a device and after, start Dolphin and register the controller and you're good.

#162 - 01/29/2013 08:14 AM - Anonymous Let's close comments until the MS bluetooth stack bugs are fixed. Toshiba is a workaround, go to the forums if you have anymore questions, this isn't a support topic.

#163 - 01/31/2013 02:45 PM - Sonicadvance1 issue 5961 has been merged into this issue.

10/01/2021 30/32 #164 - 02/02/2013 08:10 PM - ekortal_xp Someone Work for wiiremoteplus with dolphin???, because no connection :-(

#165 - 02/02/2013 11:37 PM - believeinangels88 Look up at the past few comments man...download the Toshiba stack program and connect with that...sorry mod...

#166 - 02/21/2013 09:31 PM - Billiard26 issue 6030 has been merged into this issue.

#167 - 02/24/2013 05:40 AM - npeterson5068 This issue also affects many new, official Wii controllers (e.g. Nintendo brand) most notably the ones that have motion plus built-in, all have the TR suffix. In combination with MS Bluetooth stack shipped with Windows 8, this could affect many newcomers of Dolphin using it for the first time with their next generation PC, which you'd think would run Dolphin well, but not with this problem. It think it would be worthwhile to get this fixed, as more people will begin seeing this issue with new hardware. This bug has been around since 2011 and hasn't been fully addressed.

#168 - 02/24/2013 11:59 AM - scientificraver But it is not a Dolphin issue so the developers can do nothing about it. And installing Toshiba Stack is a easy and working solution. If you read through the above text and earlier discussions you will see that communication with the TR-Wiimote seems to be blocked by Microsoft Stack, so please complain at M$.

#169 - 02/24/2013 06:31 PM - believeinangels88 It's as easy as Googling Toshiba Stack, downloading, connecting your remote with that instead of the MS bluetooth program, then connecting with Dolphin. Then play your game and be happy.

#170 - 02/24/2013 10:38 PM - arthurnunesq Toshiba stack isn't free.

#171 - 02/24/2013 11:55 PM - Anonymous It's not that easy on Win8. You need to disable signed driver checking using the boot menu, then manually install the driver through device manager, pick the inf file after you patched it.

It's not an ideal solution, but it works for now.

#172 - 02/25/2013 12:10 AM - scientificraver I wonder if someone tested Broadcom Bluetooth Stack http://www.broadcom.com/support/bluetooth/update.php or BlueSoleil, they might work with Windows 8 as well (untested).

#173 - 02/25/2013 12:20 AM - adlr Hey all,

I think the -TR Wii remotes can be made to work with the standard Windows bluetooth stack. The reason it's not working currently is because the -TR Wii Remotes require bluetooth authentication if they're to be used with normal HID messaging (as opposed to direct L2CAP messaging). The older Wii Remotes didn't require auth, so Dolphin and many other projects didn't bother with it. Other platforms besides Windows can use L2CAP easily, so they took that route to use the new Wii Remotes. Windows seems to really require HID messaging, so for Windows, I think BT auth is going to be necessary.

Authenticating isn't that complex: the password (as I recall) is the MAC address of the Remote. So someone needs to write software to perform this authentication. I am not a Windows programmer, else I'd have a go at it.

For an example of how this was solved on other platforms, you can look at OpenEmu for Mac, which does the BT auth that Dolphin needs to do. OpenEmu uses normal HID messaging (as opposed to L2CAP messaging), so it's a great example of what needs to happen in Dolphin.

10/01/2021 31/32 -andrew

#174 - 02/25/2013 07:57 AM - Anonymous I actually just tried the broadcom drivers, doesn't connect with dolphon either. My toshiba trial expired so I cleaned the toshiba drivers out and installed the broadcom.

Dolphin will at one point say it's connected in the wiimote settings, but on refresh it changes back to 0.

#175 - 02/25/2013 08:00 AM - Anonymous What about this? http://www.richlynch.com/code/wiipair

#176 - 02/27/2013 11:34 PM - ExtremeDude2 Dolphin used to use that XD

#178 - 05/12/2013 10:28 AM - skidau issue 6314 has been merged into this issue.

#179 - 12/09/2013 03:19 PM - NeoBrainX - Status changed from Accepted to Accepted

OnHold=>Accepted.

Should this be closed as WontFix maybe?

#180 - 09/21/2014 09:55 AM - JMC4789 - Status changed from Accepted to Fixed

The DolphinBar makes this easy. Toshiba stack makes this work.

Some Third Party Wiimotes aren't compatible with Dolphin, but it's unknown what the reason is for them. If someone wants to make a separate issue for them, they can.

Counting as fixed due to the fact a chance was implemented on Dolphin to make the DolphinBar work, which greatly eases Wiimotion+ Wiimotes.

#181 - 01/24/2015 10:31 PM - Firedefender1 This problem is still persisting for me in version 4.0.2 and version 4.0-5267. I bought this wiimote 4 days ago. I says "Nintendo RVL-CNT-01-TR" in bluetooth. This is no third party controller. It also says "RVL-036" on the bottom.

#182 - 01/24/2015 10:37 PM - Firedefender1 update: 4.0-5285 also not working. specs: Windows 8.1 64bit, Intel Xenon CPU E3-1240 V2 (4x3.40GHz), Nvidia GTX 750Ti

#183 - 01/25/2015 03:54 AM - Anonymous You have the Wii motion plus. You need to use the Toshiba drivers, info on forum

10/01/2021 32/32