Are you still working on it? Any progress/hope?
The New Wii Remote Plus Pairing Issue
|
12-09-2011, 05:16 AM
Just so everyone knows... I have added the changes into a server side copy on google code. Feel free to download the source and compile and test. Also feel free to send me emails regarding any new news on the support of this controller. Thanks.
http://code.google.com/r/sexiiwhiteboy16...e/checkout At this point, the controller should only pair with dolphin, and possibly rumble upon pairing. I am still working on the imputs, but its better than nothing. I am sure this issue will be fixed very soon. If not by me then by someone else. 12-09-2011, 06:39 AM
I have posted this on the 5011 issue (http://code.google.com/p/dolphin-emu/iss...il?id=5011) as well but I figured I'd get it circulating the forums too.
This is all the properties copied out of Device Manager for the RVL-CNT-01-TR model Wiimotes. I don't have an older wiimote, just this one to compare anything with. If someone could copy and paste all the data from an older working wiimote we might be able to see which values have changed and could be important to adding support. http://pastebin.com/UTi8H1CK Sexii - I'm going to try your source and see if I can at least get the wiimote to pair. I haven't even been able to pair it with any of the source file changes on my own for some reason. If I can just get it pairing I can mess around with the values. I just want to get to a good base point where the wiimote is pairing. I've spent the past 2 nights working at this. Failure is not an option . I spent 90 bucks on a new controller, nunchuck, and sensor bar and damnit I'm going to make it work. 12-09-2011, 08:41 AM
Hi, I'm the one who originally posted issue 5011 and posted the code changes which I assume made it to Skullkid's repo.
Myself and shuffle2 have discussed potential solutions to these problems with the new "TR" remote. I was able to sniff the bluetooth traffic between my Linux PC and the Wiimote using the same methods that the "dumps" in the source tree were made. Based on some poking around I think one of the main problems is when Dolphin attempts to bring the remote into continuous reporting mode. Either way, shuffle2 recommends that a proper bluetooth HID driver be made for the new Wiimote. I do not have the skill to do this. I also do not know if shuffle2 is going to do it, or do it anytime soon if he is. So, for those of you who are waiting for a fix honestly I would not stick around waiting for it if you're banking on it being fixed in the VERY near future. Do you guys want to set up a separate IRC channel or another form of communication to see if we can fix this issue? (At least a form of communication that is instant) 12-09-2011, 11:00 AM
Honestly, what would be best . Im assuming a seperate IRC channel would be easier, but I have no clue.
12-09-2011, 11:56 AM
Some of this might be helpful for creating a driver.
http://wiibrew.org/wiki/Wiimote/Library http://wiimotelib.codeplex.com/ http://wiiyourself.gl.tter.org/ I don't care about the IRC, I'm game either way but posting the same thing between two threads is annoying lol. 12-10-2011, 01:20 PM
12-10-2011, 01:26 PM
Linux distros has some available utilities that can do it, look in the wiimote dumps directory: http://code.google.com/p/dolphin-emu/sou...te%2FDumps
Some of the files there have the exact commands used to sniff the traffic, but unfortunately this doesn't tell us exactly how we should communicate with the wiimote as far as the problem we're having goes. 12-13-2011, 05:33 AM
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.
|
« Next Oldest | Next Newest »
|
Users browsing this thread: 1 Guest(s)