Project

General

Profile

Emulator Issues #12088

Classic Controller Pro sticks don't work for Emulated Controllers

Added by lemon-sherbet 2 months ago. Updated about 11 hours 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:
5.0-12290

Description

Game Name?

Any

What's the problem? Describe what went wrong.

Trying to map the left or right stick from a classic controller (pro) connected to a wiimote as an emulated controller doesn't work, dolphin doesn't read the values correctly. The same controller works through bluetooth passthrough however.

What steps will reproduce the problem?

Connect a Wiimote with a classic controller pro plugged in following the instructions here: https://dolphin-emu.org/blog/2020/04/05/dolphin-progress-report-february-2020/#50-11684-add-support-for-wii-remotes-over-inputcommon-by-billiard ; then open any input configuration dialog (for example, standard gamecube controller) and select device Bluetooth/#/Wii Remote. When attempting to map a stick directly by left clicking an input button and moving the stick in any direction, it does nothing (eventually it times out). Opening the menu for any input item with right click and scrolling down to the classic controller section reveals that dolphin isn't reading the inputs correctly: axis values under a certain unknown threshold display inf or 0 and values over that unknown value display nan. I have attached screenshots and a video demonstration.

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

Yes (Dolphin 5.0-12015; Revision: 1bedbdf3c07999f8a9fb88f64e19107e6f59b3b7).

Is the issue present in the latest stable version?

N/A

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.)

The issue is present in the first version which introduces the wiimote over InputCommon feature (5.0-11684, revision 2b6a1ee4d87a80418ade913e15745d78309f7f67).

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

CPU: Intel i3-6100
GPU: NVIDIA GeForce GTX 1050
OS: Fedora 31 (Workstation Edition) x86_64 (Linux 5.6.7)

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

Sticks in neutral position: Sticks in neutral position

Moving sticks in a clockwise motion (first left stick, then right stick): Moving sticks in a clockwise motion (first left stick, then right stick)

Using xwiishow to show input values outside of dolphin shows that the sticks do work as intended, however there's a calibration issue with the left stick (when left neutral it produces a significant input in the Y+ direction), which is probably not the source of the issue. This behaviour is also shown by using the device through bluetooth passthrough in dolphin.

NeutralSticks.png (21.7 KB) NeutralSticks.png Sticks in neutral position lemon-sherbet, 05/05/2020 02:41 PM
ClockwiseMotion.gif (369 KB) ClockwiseMotion.gif Moving sticks in a clockwise motion (first left stick, then right stick) lemon-sherbet, 05/05/2020 02:51 PM
nunchuk_neutral_stick.png (14.4 KB) nunchuk_neutral_stick.png Nunchuk analog stick in neutral position musicalmitten, 05/05/2020 06:53 PM
7786
7788
7790

Related issues

Related to Emulator - Emulator Issues #12054: Nunchuk giving X+ and Y+ axis reading as X- and Y-Duplicate

History

#1 Updated by musicalmitten 2 months ago

7790

This isn't just an issue with the Classic Controller. I ran into the same problem with the analog stick on a regular Nunchuk when trying to configure InputCommon.

#2 Updated by Billiard26 2 months ago

#3 Updated by Billiard26 2 months ago

  • Assignee set to Billiard26

It looks like your extensions have faulty calibration data. We'll have to look out for this to provide fallbacks.

#4 Updated by lemon-sherbet 2 months ago

musicalmitten wrote:

This isn't just an issue with the Classic Controller. I ran into the same problem with the analog stick on a regular Nunchuk when trying to configure InputCommon.

Interesting. I tested it with my Nunchuk and it works as intended, for me it's only the classic controller that is an issue. Seems like Billiard26 says it only occurs with specific devices.

#5 Updated by Billiard26 8 days ago

  • Status changed from New to Fix pending

#6 Updated by Billiard26 about 11 hours ago

  • Fixed in set to 5.0-12290
  • Status changed from Fix pending to Fixed

Also available in: Atom PDF