Project

General

Profile

Actions

Emulator Issues #5242

closed

sending wiimote commands on the interrupt channel breaks older nintendo wiimotes

Added by brian almost 13 years ago.

Status:
Duplicate
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

  1. Game Name and ID (as it appears in right click > properties: "GZ2P01",
    "RSBE01", etc):

All games (core dolphin issue)

2) What is the expected output? What do you see instead?

I have an original Wiimote from a launch-day US Wii system, reported as RVL-CNT-01. Using this Wiimote with Dolphin on OS X broke with 3.0-418. There are a few threads about this already, see for example http://forums.dolphin-emulator.com/showthread.php?tid=21780

I was able to fix this by downloading the source, and changing back to sending commands over the control channel, rather than the interrupt channel, in Wiimote::IOWrite in IOdarwin.mm.

This change to the interrupt channel is mentioned In the release notes: "Send commands on the interrupt channel, not the control channel. The new Wii Remotes require this; old ones are compatible with this. Note: 3rd party Wii Remots are untested with this change; the hope is they are still functional."

It appears that very old wiimotes are not compatible with this change. Probably the correct solution is to detect what version wiimote it is, and change channels accordingly.

3) Did the game ever work correctly (i.e. not have this problem) on an
earlier version of dolphin? Please specify the exact revision when the
problem began.

Yes, before 3.0-418

4) What steps will reproduce the problem?

  1. Load any dolphin 3.0-418 or later, and try to connect an original US wiimote.

5) What version of dolphin are you using (32bit/64bit along with the
version as it appears in the title bar, etc)?
On what operating system, drivers, and hardware? Be sure to list OS,
graphics driver information, and video card model if you are having
graphics problems, for example.

3.0-427
Mac OS X Lion 10.7.3
iMac 27", early 2010


Related issues 1 (0 open1 closed)

Is duplicate of Emulator - Emulator Issues #5249: Should detect Wii Remotes by string name, not vendor id/product idFixedadlr

Actions
Actions #1

Updated by parlane almost 13 years ago

I'm curious, does your wii remote work with NEW homebrew on your wii? As they changed libogc to handle these new remotes, I am wondering if they broke crappy third party ones.

Actions #2

Updated by brian almost 13 years ago

I don't have homebrew, unfortunately, so I can't test that out. Note this isn't a third party wiimote, it's an official wiimote that we got with our wii the day the wii launched in the U.S. I have two of these launch day wiimotes, both exhibited the same problem and my code change fixed them in both cases.

Actions #3

Updated by parlane almost 13 years ago

Do you have HBC/bootmii installed?

Actions #4

Updated by brian almost 13 years ago

no, I don't have any mods or custom software installed on my physical wii, unfortunately. would it be helpful to try the Windows version of Dolphin, and see if my wiimote works there?

Actions #5

Updated by parlane almost 13 years ago

Your wiimote should work on windows as we can't seem to use the interrupt channel :\ I hate bluetooth would be a good summary.

Actions #6

Updated by brian almost 13 years ago

lol I had to deal with the bluetooth stack back in the early days of Windows Mobile, I know your pain ;)

Actions #7

Updated by parlane almost 13 years ago

  • Status changed from New to Duplicate

The change to fix this bug is in issue 5249

This should provide a solution for your older wiimotes once implemented.

Actions

Also available in: Atom PDF