Dolphin, the GameCube and Wii emulator - Forums

Sounds...not so great. Bought a new one and returned the TR mote.

i've been trying to look up reports as to why Nintendo changed the remotes to begin with but have not found any info.
Does anyone have any idea?

I'm also interested in knowing how the new Wii remotes work with my Wii, running a FW from like 3 years ago.

Yeah that would be interesting. Maybe it's a rather easy fix, since the old Wii consoles can recognize it without a problem too.

I posted this originally in the other issues thread (http://forums.dolphin-emu.org/showthread.php?tid=20428) but I thought it'd be appropriate here too:

I have posted this on the 5011 issue (http://code.google.com/p/dolphin-emu/iss...l?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

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, 06:41 AM)rgfreek Wrote: [ -> ]I posted this originally in the other issues thread (http://forums.dolphin-emu.org/showthread.php?tid=20428) but I thought it'd be appropriate here too:

I have posted this on the 5011 issue (http://code.google.com/p/dolphin-emu/iss...l?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

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.

Now that's the attitude I want to see here, with that confidence you will make it work kid.
Good luck!!

i'd post up the non tr but I'm not sure where you got that info in the Device Manager... let me know.

Those ID's in the device manager won't really help at all because they changed the protocol that the Wii uses to communicate with the remote. See the other thread where I posted (http://forums.dolphin-emu.org/showthread.php?tid=20428&pid=186328#pid186328)

(12-09-2011, 08:52 AM)gergc Wrote: [ -> ]Those ID's in the device manager won't really help at all because they changed the protocol that the Wii uses to communicate with the remote. See the other thread where I posted (http://forums.dolphin-emu.org/showthread.php?tid=20428&pid=186328#pid186328)

Couldn't they help in the driver creation? Or a hack?

I assume that a new driver is required here too. How is the driver done for the original wiimotes? Was it done by the dolphin devs or elsewhere?

Do we have a source for those?

---

(12-09-2011, 07:31 AM)Integraoligist Wrote: [ -> ]i'd post up the non tr but I'm not sure where you got that info in the Device Manager... let me know.

On Win7 Start -> Devices and Printers -> Your WiiMote should be in here listed as Nintendo RVL-CNT-01.

Double click on it, Hardware tab -> Properties at the bottom

Properties window -> Details tab

There is a dropdown selection with a bunch of info in it. You can just copy the important IDs if you want.

Thanks!

An actual HID driver wasn't written for the old Wiimote's. The numbers you posted probably aren't relevant to fixing the issue unfortunately ...all we need to know is the PID/VID of the new controller which the VID has stayed the same but the PID changed to 0x0330. I've already documented that