Project

General

Profile

Actions

Emulator Issues #13833

open

Dolphin XInput devices (and potentially other controllers) produce different coordinates with the same input if TAS Input window is open

Added by Motobug 21 days ago.

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

Super Smash Bros Brawl (Project+, though this is likely a universal issue)

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

RSBE01

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

d18726e6dfdc8bdbdad540b561051087

What's the problem? Describe what went wrong.

When using XInput controllers (most notably all-digital ones), pressing the same button will send the "stick" to a different coordinate depending on whether the TAS Input window is open or not. This issue was found while testing a fork of Dolphin for usage with Project+. Oddly, the default behavior isn't the correct one - the proper coordinates for things such as shield drops and wavedashes are only accessible with the TAS window open, so the normal input processing should be made to match the TAS window, not the other way around.

With further testing, coordinates appear to be offset by one when the TAS window is open; with the TAS window open, Dolphin's input viewer outputs 58, 94 for the wavedash angle, and when it's closed it outputs 59, 95.

What steps will reproduce the problem?

  1. Configure an XInput device within Dolphin's controller settings for a GameCube controller
  2. Boot into any game and note the coordinates of an input (easiest to replicate if using a digital input, such as a D-Pad, in place of an analog stick)
  3. Open the TAS Input window; the coordinates will now be off by one.

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, 2506-123.

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

Yes, 2506a.

If the issue isn't present in the latest release, 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.)

N/A

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

N/A

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

CPU: i5-13600K
GPU: AMD Radeon RX 6800
OS: Windows 11
RAM: 32 GB

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

Here is a video showcasing the issue; with the window open, the coordinates change, despite the same two digital buttons being pressed: https://streamable.com/58aqar


Related issues 1 (1 open0 closed)

Related to Emulator - Emulator Issues #12927: Unwanted analog input scaling in Dolphin 5.0-16380New

Actions
Actions #1

Updated by Billiard26 20 days ago

Actions

Also available in: Atom PDF