Project

General

Profile

Actions

Emulator Issues #13585

open

TAS Input IR is not mapped 1:1

Added by InputEvelution 3 months ago. Updated 3 months 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?

Any Wii game using IR.

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

Any Wii game using IR.

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

Any Wii game using IR.

What's the problem? Describe what went wrong.

WiiMote IR in TAS Input does not give the player total control over their movements. The IR values inputted do not match those that the WiiMote actually performs - for instance, 512,384 will put the cursor at 580,452 - and when changing the values, the cursor will smoothly move to the new position over a number of frames instead of snapping to it.

What steps will reproduce the problem?

  1. Open TAS Input and tick "Show Input Display" in the Movie tab.
  2. Open a Wii game that uses the IR cursor - for instance, Wii Party.
  3. Reach a point where the player's cursor appears on screen.
  4. Observe the value of the IR in the input display, and the value of the IR in TAS Input. They should be the same, but are not due to this issue.
  5. Pause the game.
  6. Change IR to a different value in TAS Input.
  7. Frame advance forwards while watching the value of the IR in the input display. The IR should change to a new position immediately and stay there, but it instead gradually moves to the new position over a number of frames due to this issue.

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

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

Yes. Dolphin 2407.

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

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

Windows 10. i7-8750H CPU. GTX 1060 6GB.

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

JosJuice tells me this is a side effect of a rewrite she made of how TAS input passes inputs to the emulator core.

Actions #1

Updated by JosJuice 3 months ago

  • Subject changed from TAS Input IR does not work correctly to TAS Input IR is not mapped 1:1

The PR I've theorized is the cause is: https://github.com/dolphin-emu/dolphin/pull/9624

The old code had a lot of comments about things being broken in certain situations, so I don't think a simple revert would be desirable. But it is desirable to let TASers move the pointer without any added interpolation.

Actions

Also available in: Atom PDF