Wiimote Problem - disconnect

[odd29]

Today was the first day i tried Dolphin!!
its working very well.. but now i got some problems witht he wiimotes!
there are 2 original Nintendo wiimotes, both are connected and when i want to try to play "Mysims Party" the second controller is losing connection after a few seconds!

then there is a problem to connect the controller again with the bluetooth dongle!
in english the error message is something like "an error with the devicedriver..."
i´ve read about some problems with the dolphin and the real wiimote connection and i´ve also tried a different revision but still same Problem..

any suggestions?
sorry for my bad english!

[odd29]

ohh, still no answere :-(

i´m using the hama nano usb 2.0 stick!
i´ve tried Bluesoleil, the Toshiba stack, windows stack.
i´ve also tried older dolphin revisions like 7271 but no luck

everytime i start to play a game one controller is disconnecting after a few seconds :-(

---

it seems that controller 1 stays connected and controller 2 is the one who is disconnected after a few seconds!!

[odd29]

bump bump

[fidoboy]

it seems to be an issue with the emulator, cause this doesn't hapened with previous versions (v2). Let's hope that they could solve it soon, i think that this a major issue and it deserves to be considered at first place. Right now, there are a lot of playable games, but there is many problems using remotes (as i've exposed in other thread, DK Country Returns is unplayable because of remote is being disconnected all the time)

regards,

[opoch]

(10-09-2011, 09:48 PM)fidoboy Wrote: it seems to be an issue with the emulator, cause this doesn't hapened with previous versions (v2). Let's hope that they could solve it soon, i think that this a major issue and it deserves to be considered at first place. Right now, there are a lot of playable games, but there is many problems using remotes (as i've exposed in other thread, DK Country Returns is unplayable because of remote is being disconnected all the time)

regards,

100% Agree with you. Should be located as Number one thing to fix. I hope in some way this issue will be solved. *Fingers crossed*