(02-14-2013, 02:42 AM)LordVador Wrote: [ -> ]@Billiard26: can this branch solve controller issues in some games?
Games such as Red Steel, Far Cry Vengeance, Shaun White Road Trip have controller issues: controls don't respond any more, you can't select anything, perpetual disconnections...
So I just wondered if this "continuous scanning" could solve these issues
I was not aware of any issues like that. Make an issue report.
And this branch isn't going to fix something like that.
I used leetminiwheat's AVX build of the 3.5-428 with real-wiimote-scanning and it worked great with my Bluetooth adapter. I'm using the Windows stack for Bluetooth.
The only game I saw that had problems was Donkey Kong Country Returns. After the instructions to use the wiimote horizontally it says the wiimote disconnects.
I just tested revision 478 and continuous scanning is working great with my standard orgininal wiimote and the mircrosoft bluetooth stack.
But: My "Wii MotionPlus inside wiimote" is making problems. I can get it connected by pressing the connect button (Button 1 and 2 won't work) but all that I get are four flashing lights. Dolphin reports a connected wiimote and if I connect a second normal wiimote after that the second one becomes a registered wiimote number 2. Still, the motion+ remote keeps on flashing forever and is not usable. Any ideas?
(02-28-2013, 03:50 AM)Silver83 Wrote: [ -> ]I just tested revision 478 and continuous scanning is working great with my standard orgininal wiimote and the mircrosoft bluetooth stack.
But: My "Wii MotionPlus inside wiimote" is making problems. I can get it connected by pressing the connect button (Button 1 and 2 won't work) but all that I get are four flashing lights. Dolphin reports a connected wiimote and if I connect a second normal wiimote after that the second one becomes a registered wiimote number 2. Still, the motion+ remote keeps on flashing forever and is not usable. Any ideas?
Wait for Microsoft to fix their broken bluetooth stack:
https://code.google.com/p/dolphin-emu/issues/detail?id=5011
Funny...sort of.
I always made a connection with the Toshiba Bluetooth stack (works great with Motion Plus Inside) but sadly it isn't supported by the continuous scanning.
I don't really think Microsoft will fix anything anytime soon, so is there a chance of working scanning with other stacks?
My TR-Wiimote, connected with Toshiba Stack by just pressing the A-Button (1+2 does not work with Toshiba Stack), completely stopped working after merging this branch to master. There is no way to get it recognized by Dolphin. Formerly I had to use the refresh button to get it recognized but now it seems to be completely dead, it does not matter if the new scanning option is enabled or not. With older builds than 3.5-471 everything works fine. 3.5-432 therefore is the last revision allowing me to connect my only Wiimote.
Microsoft Stack might never get fixed as the missing compatibility of TR-Wiimotes might be intended by Nintendo. The implementation of "real-wiimote-scanning" should be redone in a way that TR-Wiimotes and Toshiba Stack will not be affected. Maybe installing Toshiba Stack on a developer PC might be beneficial to find a solution.
Ok, it's not working with me. I run Windows 8 and have a bluetooth dongle by HAMA which uses Blusoleil but although Windows detected it,
Dolphin says that it didn't found any bluetooth device. What exactly do I have to do right now? Before the branch merge, everything was fine!
Also having issues post 471, using a official TR wiimote and the toshiba stack. Connecting the wiimote now requires to press refresh before loading any game up as it doesn't automatically detect like previously. Also seems to randomly lose connection to both the nunchuck/wiimote at random points.
Edit: Correction, was the mote playing up started doing it on the wii as well, no issues on another wiimote.
Tested with OS X 10.8.1 and 10.6.8, 3.5-430 of the real-wiimote-scanning branch, using an official Wiimote.
I am not able to connect the Wiimote to Dolphin using the continuous scanning. When playing Wii Sports, I see the message Connecting... but no connection is made.
Currently, the only way I can connect the Wiimote in the stable 3.5 release, is to press the sync button on the Wiimote then startup Dolphin, then select the Wiimote menu. At that point the Wiimote will buzz and a single light will appear, then I get the message Wiimote connected. Sometimes I have to repeat the process before it connects.
However, if I try this same process with the current build of the real-wiimote-scanning branch, the Wiimote will buzz, a single light will appear, but, I still get the message Connecting... and then the light will go out.
i'm also having a problem with the changes in the wiimote-handling incorporated into dolphin since 3.5-471.
i'm using WiiPair to establish a permanent pairing with MS bluetooth-stack. this way before 471 i just had to press a single button on the wiimote and start up dolphin, and the wiimote was usable instantly. closing dolphin kept the wiimote online and paired, waiting to be used again by dolphin or any other tool (e.g. glovepie or wiimouse).
now with 471 the behaviour is the same up until exiting dolphin. now when i exit dolphin, the wiimote gets completely removed from the bluetooth devices (and thus unpaired) and the HID-device gets removed. now i would have to create a new permanent pairing with WiiPair, etc. well actually it completely negates the meaning of the permanent pairing.
imho dolphin shouldn't mess with die bluetooth devices or remove them, if it is not intended by the user. or please at least implement an option "do not unpair/remove wiimotes on exiting dolphin" or something like that.