Project

General

Profile

Actions

Emulator Issues #13263

open

Input polling issue on MHTri

Added by Peppo 11 months ago. Updated 10 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?

Monster Hunter Tri

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

RMHE08 (00010000524d4845)

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

bf0f07f29cc653b8440acdba0de719c7

What's the problem? Describe what went wrong.

When pressing 2 buttons simultaneously (A+X) after an R input, sometimes the game only reads one of the 2 inputs, resulting in a different action.
I only tested this with a weapon, the Long Sword: typically, A+X buttons give you a fade slash, while if you use your L-stick to the right or the left and press A+X you get a lateral moving slash. This last move can't consistently be reproduced after a Spirit attack has been performed (R input). I'll leave a link to the clips I recorded to better understand this issue, also showing the emulator correctly reading both inputs but actually registering only one of them.

What steps will reproduce the problem?

Connecting a controller, and setting the Classic Style 1 in the options menu in the main menu. With a Keyboard, this issue is still replicable, but it's a bit more consistent to perform the lateral moving slash after a Spirit attack, especially if you spam X+A.

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

The issue is present in the latest development build 5.0 - 19385

Is the issue present in the latest stable version?

Yes, version 5.0 - 18498

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

Many frames (<100) need to be recorded to show this issue, and with a max size of 5MB I can't attach anything. I uploaded the Fifo Log in Google Drive, this is the link: https://drive.google.com/file/d/1Q4Ne3aweLZcanWwPtxe2yUL3o4bjwRIb/view?usp=share_link

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

AMD Ryzen 5 5600X
RTX 3070
Windows 10

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

Please check the clip I recorded showing the gameplay and the input reading from Dolphin Emulator on the side:
https://drive.google.com/file/d/1riLMMGRuuyFZy__m-YuZ7dkeb7jzyK6F/view?usp=share_link

Actions

Also available in: Atom PDF