Project

General

Profile

Actions

Emulator Issues #8093

closed

WiiMote connects, but games don't react to it

Added by marcus.sentry over 9 years ago. Updated over 3 years ago.

Status:
Working as intended
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

Game Name?
Mario Kart Wii
Puzzle Quest: Challenge of the Warlords

Game ID?
RMCP01
RQWPG9

What's the problem? Describe what went wrong in few words.
My real WiiMote is connected to Dolphin (it says so in the status bar and the yellow overlay in the game, also the blue LED on the WiiMote stopped blinking and the first LED is on), but it won't react in the games.
Only exception so far is Puzzle Quest: Challenge of the Warlords, where the A button works, but nothing else.

What did you expect to happen instead?
It would work ingame, i.e., the game reacts to the WiiMote

What steps will reproduce the problem?

  1. Start Dolphin
  2. Connect the WiiMote (Press 1+2) and start the game (also tried it the other way around, also reconnecting during the game)
  3. Press the A button when prompted during the title screen
  4. Nothing happens, menu should appear. (In PC:COW A works, but I can't select any menu point.)

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-5064, compiled it myself with GCC-4.9.

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Did not try older versions

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Ubuntu 12.04.5, Kernel 3.2.0-75, amd64, Motorola PCS Bluetooth Device, Standard WiiMote RVL-CNT-01

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

I don't know what information will be relevant, but I will provide them if possible

Actions #1

Updated by JMC4789 about 9 years ago

  • Status changed from New to Questionable

Unable to reproduce. Do you have Dolphin set to use Real Wiimotes? Is Continuous scanning on?

Actions #2

Updated by marcus.sentry about 9 years ago

Yes and yes, it is set to Real Wiimotes and I've tried it with and without Continuous scanning.

I might want to add that I just tried it under Windows 7 with version 4.0-5323, same Bluetooth-USB-Adapter, same controller, and it works like a charm out-of-the-box. I'll try that version under Linux, too, but I don't think it will solve anything.

Is there a way to see what signals arrive from the WiiMote at the computer or at Dolphin? A debug compilation option maybe?

Actions #3

Updated by marcus.sentry about 9 years ago

Still no change under Ubuntu 12.04. I can add, that for "Soul Calibur Legends" (RSLPAF) the Home button works, but only to open the Home-menu, can't close it again.

Log says:
24:06:512 .../Source/Core/Core/HW/WiimoteReal/IONix.cpp:136 N[Wiimote]: Found wiimote (00:19:1D:C1:E1:9C).
24:07:890 .../Source/Core/Core/HW/WiimoteReal/WiimoteReal.cpp:689 N[Wiimote]: Connected to Wiimote 1.
24:08:119 .../Source/Core/DolphinWX/Main.cpp:560 N[Wiimote]: Wiimote angeschlossen (Wiimote connected)

It looks like I'll be getting another computer soon which will run Ubuntu 13.04 or 14.04, I kindly ask you to keep this issue open so I can try to narrow down the problem.

Maybe one more question to better my understanding:
I downloaded the windows version from https://dolphin-emu.org/download/, where the newest one says 4.0-5323. But when I fetch the newest version from GitHub and compile it under Linux, it says 4.0-5064. Where does this discrepancy come from and what revision number should I report?

Actions #4

Updated by JMC4789 about 9 years ago

I'll keep this open until whatever is happening is narrowed down.

Actions #5

Updated by Billiard26 about 5 years ago

Just sounds like a combination of bad bluetooth hardware / drivers.

Actions #6

Updated by Billiard26 over 3 years ago

Is this still a problem for you in recent builds?

Actions #7

Updated by marcus.sentry over 3 years ago

Sorry for the very (very) long absence. I'll doubt that I can reproduce it, but I'll put it on my ToDo list for this week.

If you'd rather close this issue after waiting five years for my feedback, I'd totally understand.

Actions #8

Updated by Billiard26 over 3 years ago

  • Status changed from Questionable to Working as intended

Will re-open upon request.

Actions #9

Updated by marcus.sentry over 3 years ago

I just tried it with the latest stable release (5.0) and a proper Bluetooth Dongle that I know possess.
Everything works like a charm.

Thanks again, for your patience and the great work on Dolphin :)

Actions

Also available in: Atom PDF