Project

General

Profile

Emulator Issues #9267

Auto-fire ignores loaded savestate's button state

Added by DaTeL237 over 4 years ago. Updated over 4 years 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?

Probably any game, but I was doing: Star Wars: Rogue Leader

Game ID? (right click the game in the game list, properties, info tab)

GSWE64

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

0bf391bee90da09d6042016d23e7a9b1

What's the problem? Describe what went wrong.

I was recording a Tool-Assisted Speedrun (TAS) and used the auto-fire feature. When auto-fire is already enabled for a button and then a save-state is loaded... then auto-fire continues where it was regardless of the save-states. Effectively is means that there are 2 different states that can be reached: one that will release the button in the upcoming frame, another that will press the button in the upcoming frame.
As a user I would expect playback to be consistent every time a save-state is loaded

What steps will reproduce the problem?

  1. Create a save-state at frame 100
  2. Load the save-state
  3. Enable auto-fire for the A button
  4. Advance to frame 110. The display shows that the A button was just pressed.
  5. Advance 1 frame to frame 111
  6. Load the save-state (note that auto-fire is still enabled)
  7. Advance to frame 110. This time the display shows that the A button was just released

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

4.0-8534

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

Intel Core i7 6700HQ
GForce GTX 960M
16GB RAM
Windows 10 Pro 64 bit

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

I think that covers it

History

#1 Updated by DaTeL237 over 4 years ago

I missed the Title field... anyone that can change it please do so :)

There are several Edit buttons but in fact I cannot edit it, I can only leave a new Note

#2 Updated by JosJuice over 4 years ago

What do you want it to be changed to?

#3 Updated by DaTeL237 over 4 years ago

JosJuice wrote:

What do you want it to be changed to?

Not sure exactly how to describe it briefly... if this makes sense to you then consider it my proposed title :)

"When loading a save-state the auto-fire function ignores the save-state's last button presses/releases"

#4 Updated by phire over 4 years ago

  • Subject changed from [Short description of your bug here (~10 words)] to When loading a save-state the auto-fire function ignores the save-state's last button presses/releases

#5 Updated by JosJuice over 4 years ago

  • Subject changed from When loading a save-state the auto-fire function ignores the save-state's last button presses/releases to Auto-fire ignores loaded savestate's button state

Shortened it a bit.

Also available in: Atom PDF