Dolphin, the GameCube and Wii emulator - Forums

I m using a small usb-bluetooth device to connect my Wii Remote and it sees it. Dolpin also detects it and uses it as Remote 1.

BUT:

- ingame, in the games i tried so far, the pointer does not work, nor do the buttons. Apart from the home menu button Weirdly, the ingame pointer is not even shown anymore (bit.trip / world of goo). It works fine, when using the mouse as an emulated wiimote.

- after i start a game and stop it again - while having a Real Remote connected - the next game i start will hang at a black screen and dolpin seems to lock up

I tried some of the latest versions of dolpin and it's always the same. When using versions that are not patched for the disconnect issue, i also get disconnect-messages half of the time when starting games.

I m using a cheapo wireless led-bar, which might be defective, but it makes me wonder, why the buttons dont work correctly either (apart from the home menu button). Makes me doubt, that its a problem with the bar.

Any suggestions? Do others have similar issues? Could it be the bluetooth thingy or other problems with the hardware?

Disable the default GC controller.
Config/Gamecube/Port1, set it to Nothing.

thanx for the suggestion, but it didnt help. Tested with 2.0 RC1 and a reconnect patched version (5153).

It looks like the wii remote is properly connected, but the same issues like before are there (no button input registered, no pointer). I also tested a game that needs a nunchuck. That isn't detected by the game / Dolphin either.

EDIT: when i hit recording in the Wii Remote plugin, it only updates the battery status. Nothing else is shown. Maybe dolphin is getting no information from the Wii Remote for some unknown reason, although it is shown as connected (in the bluetooth panel and in dolphin) and the first light is lit up (or all four) and it vibrated when entering the plugin?

2nd EDIT: on occasion i can get it to actually display something in the recording window, so it kinda seems to work. Sometimes. I can never start a game though afterwards. Weird really. O.o

Are you using Windows XP ? do a window appears from the OS that tells you that you have to restart your computer in order to make the wiimote to work ? ( EDIT : because It always happens to me and It doesn't let me use the real wiimote if I am not fast enough to close the window first)

quote: "Apart from the home menu button"
sry, but the issue you described was a classic issue, if disabling the default gc controller port doesn't work i don't know.

I ve done some more testing and i was somewhat wrong.

Because actually, the home menu button ONLY works in World of Goo. In all other games, none of the buttons work. =(
And i haven't managed to get any more readings from the recording window either. There must be gremlins in the circuits.

I ve ordered another bluetooth usb connector to test, if it is hardware related and will test the Wii Remote with the proper Wii on monday to check if it is maybe defective (doubt it though)...

EDIT: i guess a lot of people know those two little tools already, but they helped me to check my hardware without having the real Wii here. I used WiimoteConnect to connect the remote and then WiinRemote to check the input. And it seems my sensor bar does not work (or at least somewhat flaky). I m using candles at the moment. It works with WiinRemote that way, BUT still nothing in Dolphin. =(

for those, that don't know the little tools already:

WiimoteConnect
http://www.wiimoteproject.com/bluetooth-and-connectivity-knowledge-center/wiimoteconnect-0-6-%28support-for-autoconnect%29/

WiinRemote
http://onakasuita.org/wii/index-e.html

Dolphin pairs wiimotes by itself properly. The reason for no pointer is because you don't have a sensor bar.

I have found that every time I connect my wiimote, I have to first delete the device and then Scan for a new device again. If I use the previously saved device then it doesn't work properly.

(03-14-2010, 05:40 AM)boogerlad Wrote: [ -> ]Dolphin pairs wiimotes by itself properly. The reason for no pointer is because you don't have a sensor bar.

i do have a sensor bar. But it wasnt working properly. I checked against candles, which are a good workaround for a missing sensor bar and it does not work that way either. So it is definitely something else. I will check again with another sensor bar, when i have one, but i doubt that it ll change the problems i am having.