(12-09-2011, 11:57 AM)gergc Wrote: [ -> ]Something like this is actually the direction that needs to be taken:
http://msdn.microsoft.com/en-us/library/windows/hardware/ff536572(v=vs.85).aspx
The libraries you posted are all incorrect because it contains the same type of communication/protocols that Dolphin currently uses.
So is dolphin communicating with the new wiimotes impossible without a new driver being created? Is that the case for sure? Have we concluded that there is no way to edit the current source to add support?
Since no 3rd party drivers were required for the original wiimotes, is it safe to assume that eventually the new ones will be supported as well in a future Windows update?
I was under the impression that this was a problem with dolphin and not with the actual windows drivers themselves.
Creating a driver is definitely going to be over my head. I'm poking around the WDK but it seems like learning to create a driver, even a simple driver, nevermind a wiimote bluetooth driver, would be quite a ways off if I'm learning how to create drivers from scratch.
I do have an interest in learning how to do this so starting now isn't a bad thing.
darn, seems not able to make it work before xmas
I don't think that a driver need to be created, any non-TR Wiimote will use the default Windows driver for bluetooth HID (the same driver used for Wireless Bluetooth Joysticks or even the Remote Control function of some cell phones). What I mean is that the driver used for the currently working Wiimotes is only a default driver to allow communication, so the protocol must be changed in Dolphin's source to make it work...
I think that Jhonn is right! When we can expect a fix for that? So that i know whether to send it back or not.
I just bought a Wii Motion Plus and it is the TR version. I hope you guys get a fix out soon, I'm very eager to play Skyward Sword.
(12-09-2011, 11:20 PM)Jhonn Wrote: [ -> ]I don't think that a driver need to be created, any non-TR Wiimote will use the default Windows driver for bluetooth HID (the same driver used for Wireless Bluetooth Joysticks or even the Remote Control function of some cell phones). What I mean is that the driver used for the currently working Wiimotes is only a default driver to allow communication, so the protocol must be changed in Dolphin's source to make it work...
I talked with one of the Dolphin dev's and he said that a fix would most likely require that a driver be written because the communication protocol used for the Wiimotes probably has something that's non-standard and might even require modifying the bluetooth driver itself. Similar to why the 3rd party Wiimotes do not work (the TR acts in the same manner). Additionally, having a driver written will decrease controller latency among other things.
Doubt there will be a fix before the end of the year. I'm going to see about getting a driver made that will catch I/O input for the new wiimotes. It'll take a while. I'm still not completely sold on the idea that a whole new driver for the HID device needs to be made since we can get it to pair and rumble. If we had the correct input codes I don't see why it won't work.
I don't think it's been confirmed that it's the bluetooth drivers fault here, since it does in fact pair with windows, then dolphin. It's just the inputs that aren't working. Correct me if I'm wrong here. I'm just starting at the easiest solution. Once this is proven wrong I'll start looking at the possibility of getting an HID driver made.
Note: I can't actually code drivers but I have a friend who may be able to handle this. I just need to find time to meet with him.
I have been and will continue to learn the WDK so that I can at least identify what needs to be done within the driver for HID device. I can't promise anything soon though because I don't have tons and tons of time to pour into this, especially at the start of next year, I'm moving so I'll be wrapped up with that.
Long story short, don't expect a solution from me any time soon, It's up to the dolphin devs or someone else for now.
