Project

General

Profile

Actions

Emulator Issues #12898

open

Dolphinbar connected wii remotes do not respond to pointing controls

Added by StevusPrimus about 2 years ago. Updated about 1 month ago.

Status:
Questionable
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?

WarioWare: Smooth Moves -> does not work
Super Smash ros. Brawl -> does work
Actually all games work that do not utilize something else than the keys.

Game ID? (right click the game in the game list, Properties, Info tab)

RODP01
RSBP01 (0001000052534250)

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

[Put MD5 Hash here]

What's the problem? Describe what went wrong.

On my MacBook Pro M1 Pro (MacOS 12.3.1) as well as on my PC Tower with Windows 11 the Original Wiimotes do only work on games which utilize keys only.
Furthermore I experience creates on MacOS, when the Wiimote is already connected when starting any game.

What steps will reproduce the problem?

Use a DolphinBar on the above mentioned systems, then connect a Wiimote, afterwards start e.g. WarioWare. No control is possible. It works fine in other games like Smash Bros.. The Mouse emulation modes also work on both systems. So I do not assume it is a problem with the bar itself.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-16350

Is the issue present in the latest stable version?
I cannot test it on MacOS as the latest stable version does not run anymore. In Beta 5.0-16101 the bug is present.

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

[First broken version number here (if applicable)]

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

What are your PC specifications? (CPU, GPU, Operating System, more)

[PC specs here]

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[Anything else here]


Files

wiimotebug01.png (3.71 MB) wiimotebug01.png StevusPrimus, 04/25/2022 08:00 PM
dolphin.log (805 KB) dolphin.log Log from Win11 all Info except IOS_DI StevusPrimus, 04/26/2022 05:38 AM
Actions

Also available in: Atom PDF