Project

General

Profile

Actions

Emulator Issues #296

closed

wiimote broken

Added by buugtdbgt1993 almost 16 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

from revs 1092 to latest rev wiimote is not working at all. its been
getting worse. i press A+B to start a game or press "2"in a game it doesnt
work.

Actions #1

Updated by ChaosCode almost 16 years ago

worked fine for me on R1117. I will test latest when I get home.

Actions #2

Updated by XTra.KrazzY almost 16 years ago

  • Status changed from New to Questionable
Actions #3

Updated by ChaosCode almost 16 years ago

There is something going on with the wiimote but its is working some what. not as
well as before but it is working. I'll get with F|res when he gets on again and see
what he can do.

Actions #4

Updated by thegamefreak0134 almost 16 years ago

I've been doing a lot of testing, and right now the best solution (for the end user)
is just to brute force restarting the game until it gets past the health and safety
warning screen. If it makes it to the title screen of any game without a Wiimote
out-of-sync Error, then it will probably work fine, assuming the game turned on
everything it was going to use on the wiimote during that time.

From what I can tell, Dolphin seems 97% likely to de-sync the wiimote when the game
tries to (A) turn on motion sensing, (B) turn on the IR sensor, or (C) detect whether
or not an extension is plugged in. (IR and Motion sensing seem to happen at the same
time, with Extension controllers happening first.) How far the game gets going down
this list of things before the desync determines how many of these things are going
to work in-game, and for the most part it seems that it turns them all on right after
the initial connection in any given game, which causes the desync to happen right
after a connect. Since Dolphin currently only connects one wiimote, only tries to
connect it once, and does so right after the game starts, the result is that most
wiimote problems occur before the game gets anywhere.

There could be several complete solutions to this (I'd have to be able to sniff the
bluetooth packets to really see what was going on underneath) with the best solution
being obviously to make the initial connect just work the first time every time.
Since that's not likely until Wii emulation is at a much much more stable state, a
better solution would be to allow some keyboard combination to attempt to reconnect
the wiimote, which would emulate a desync in the game and cause the whole handshake
process to start over again.

I'll note that after the first time the game gets through all of this initial setting
up, attaching and removing extension controllers seems to work OK, or at least the
game can detect it in games that require the nunchuck and will yell at you if you
unplug it, and un-yell at you when plugging it back in. It seems to only fail during
the start, and fail consistantly after that.

As a partial fix: it is quite possible to cause the wiimote to turn things on while
the game is running. While Dolphin is using it, simply open the wiiuse example
program and press UP to have wiiuse try to turn on the IR sensor. This for some
reason takes several tries for me, which suggests that the IR sensor issue might be
somewhere in wiiuse and not in dolphin at all. (You can tell that this was successful
when the wiiuse example starts throwing IR dots at the console window when pointing
at a source of IR light, like the sensor bar.)

I'm sure that someone on the dolphin team has already figured all of this out looong
before I posted it, but this way there's an issue attached to it so the general
public has some idea of what (I think) is going on. For the record regarding my
previous issue on this topic, after a certain revision my wiimote just started
working randomly, and will now almost always at least get far enough to light up the
first LED in-game, regardless of which adapter I'm using. So that issue has probably
been resolved.

Actions #5

Updated by ChaosCode almost 16 years ago

The issue seems resolved in R1150

Actions #6

Updated by thegamefreak0134 almost 16 years ago

Indeed, I'm not having any issues anymore. Good work guys! I think Wiimote emulation
through bluetooth is finally almost perfect! All it really needs now is sound, and
I'm fairly certain that's not high on anyone's priority list. Indeed, I can live
without it.

Actions #7

Updated by ChaosCode almost 16 years ago

if someone can close this issue that would be great.

Actions #8

Updated by buugtdbgt1993 almost 16 years ago

i think half of this convo is about wiimote through the acuall wiimote. im talking
about the keyboard and mouse wiimote. it doesnt work and if you guys have proof of it
working open up the latest rev open up sonic secret rings and record a video of you
press the button and the game acully respond to the buttons you press.

Actions #10

Updated by Anonymous over 13 years ago

  • Status changed from Questionable to Fixed

Ignore this...Status:Verified was removed, changing to Fixed

Actions

Also available in: Atom PDF