Emulator

Disbale wiimote speaker. I told them to make that the default.:)

Search and utilize the forums before posting known issues.

How can i disable the wiimote speaker?

Changing the Speaker Volume to min, it doesn't help.
I check the logs when i open a game, ant this is the last in 3.0 and r7225: WiimoteIOWrite[MSBT_STACK_MS]: Unable to send data to wiimote

right click the game go to properties

Thanks for answer. But it doesn't help, i already had it turned off (the speaker).

Artur: look, it works for me on both Linux {Ubuntu 11.04 x64] and Windows 7 x64.

What exact operating system are you using [you say r7225]? What exact game, PAL or NTSC? Are you sure you have no other bluetooth programs open and talking to the Wii remote?

I wonder if you have some other program like PieGlove or such talking to your remote and interfering with Dolphin...

System: Win 7 x64, Games: PAL: Wii Sports Resort, New Super Mario Bros. I checked in Blusolei and Toshiba Bluetooth Stack, but in there i can't pair my wiimote (i mean i pair it, but after this the wiimote automatically turned off, and i can't it turn on, it doesn't work in Dolphin). Actually i use the builded in Windows bluetooth drivers. The bluetooth is from Cambridge Silicon Radio. I dont have PieGlove, only WiinRemote, to chck the wiimote (it recognize all buttons and IR). But it is deleted now.

Generally on latest (post 3.0) builds, on Win 7 x64... I get this kind of behavior: "(i mean i pair it, but after this the wiimote automatically turned off, and i can't it turn on, it doesn't work in Dolphin)" sometimes.

Here is how it works for me, generally:

1. I boot system into Windows 7
2. I startup Dolphin
3. I PRESS 1+2 on my Wiimote to get it flashing
4. I click on the Wiimote icon in Dolphin
5. I hit the [Pair[ button on Dolphin
6. Windows 7 notification bars says detects new hardware and installs a driver [despite already being previously installed]
7. Windows 7 notification bar says "Bluetooth HID Device; Device driver software installed successfully"
8. The wiimote is still blinking all 4 LED's, Dolphin says "Connected to 0 Wiimotes". I have let it sit here for several minutes and the wiimote stays blinking.
9. I press [Refresh] button in Dolphin and it now vibrates the remote, the LED then changes to just 1 solid to indicate #1 remote. DOlphin now shows "Connected to 1 Wiimotes".
10. When I hit Play in Dolphin to start a game, wiimote vibrates again. Works fine.

Now after loading, unloading, changing between versions of Dolphin.... sometimes the pair in Windows 7 refuses to work. The Windows 7 driver fails to load... exiting Dolphin does not fix it. Nothing seems to fix it, I have to reboot Windows 7. I haven't figured out that problem, it seems Windows and wiimote in a mismatched state.

stephen: have you tried manually removing the wiimote device from the win7 devices list? Try that and/or hard resetting the wiimote (most extreme way is to take out batteries and hold the red button for a few seconds).

Let's be clear, IT WORKS for me. My procedure is 100% working. My mention of a secondary issue is minor (experimenting with opening/closing various versions of Dolphin seems to put the wiimote and Win 7 at odds). I haven't bothered yet to delve further into that problem, it seems outside of Dolphin...

It is OP (Artur) that says for him it isn't working AT ALL. That was the reason I spelled out my procedure, just to establish some kind of known working procedure...

Geez, why do I even bother...

why do you concern yourself with what hasn't even been established with a bug? I know you are trying to be helpful, but I'm just trying to point out the obvious to Artur - that it DOES work. I have two different systems and both Linux and Windows 7 I'm testing with... it clearly is not failing 100% like he implies.

It's likely some system-specific or environment issue...

From strictly an operating system perspective, a lot of the advice on Dolphin seems obsolete to me on newer Windows 7 and Linux systems. As far as I can tell, there is no need for these alternate bluetooth software stacks. It's analogous to using a third-party brand-specific WiFi interface manager when the one in Windows 7 is consistent across all hardware, it seem to introduce more problems than solve anything. In the old Windows XP days, these alternate tools had more place...

WAIT A MINUTE... rereading this, I see I overlooked a huge aspect.

Artur said... "The remote model: SpeedLink MeMote Plus"

Well, until you try with a genuine Nintendo remote... we aren't sure that the problem isn't specific to that remote.

Stephen, thanks for the tips. I do this it in the same way, but in point 10) when i hit the play button, my wiimote doesn't vibrate again. I bought a ganiuine remote, is in the way to me. When i recive it, i will say, if it works.

FYI: another brand of third-party remote, Memorex, has problems too. See issue: https://code.google.com/p/dolphin-emu/issues/detail?id=4560

Hi, I have this problem under Ubuntu 11.04 64bit.

The same wiimote+nunchuk + bluetooth dongle work perfectly under Windows Seven 32bits.

I tried r7258 r7271 r7687 r7690 r7695 and version 3.0 64bits, either compiled from source or from glenrric ppa.

The problem is the same: the wiimote vibrates once when the "refresh" button is pressed, and it never works in game.
Sometimes the four LEDs go on blinking while sometimes, only one stays on.
If I power off the wiimote while the game is running, I see "wiimote disconnected" in the game window and in the log.

Disabling or enabling the wiimote speaker, or sound doesn't change anything.
On Windows, it works with wiimote speaker on or off. On Ubuntu, it doesn't work whatever the setting.

lswm / wmgui see the wiimote correctly and gets sensors data.
lswm output:
[ 01:1A:19:03:DE:15 ]
Name = Nintendo RVL-CNT-01
Paired = 0
LegacyPairing = 1
Alias = Nintendo RVL-CNT-01
Address = 01:1A:19:03:DE:15
RSSI = -76
Class = 0x002504
Icon = input-gaming

It doesn't seem like a hardware problem to me.

Any idea ?