Project

General

Profile

Actions

Emulator Issues #10912

closed

Savestates cause real wiimote extensions to malfunction

Added by NarryG almost 7 years ago. Updated over 5 years 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-9808

Description

Game Name?
Not Applicable

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

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

What's the problem? Describe what went wrong.

If you create a savestate in "Real Wiimote" mode with a nunchuck attached, that savestate works fine for the current session. If you restart Dolphin or reconnect your Bluetooth adapter then load that same savestate, the control stick no longer responds properly. This appears to be an issue with the neutral position of the stick.

What steps will reproduce the problem?

  1. Set Dolphin to use a "Real Wiimote"
  2. Connect your Wiimote and Nunchuck
  3. Launch a game that uses the nunchuck
  4. Create a savestate
  5. Restart Dolphin
  6. Load that savestate
  7. The control stick no longer properly responds (neutral position is wrong)

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
5.0-6378

Is the issue present in the latest stable version?

Yes, 5.0 Stable

What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10, Fall Creator's Update
GTX 1080
i7-6700k

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

"Nintendo games calibrate the center position of the Analog Stick upon power-up or insertion of the Nunchuk. The mechanism for that is unknown."
https://wiibrew.org/wiki/Wiimote/Extension_Controllers/Nunchuck


Related issues 1 (0 open1 closed)

Related to Emulator - Emulator Issues #8440: Wii MotionPlus does not always work with savestatesFixedBilliard26

Actions
Actions #1

Updated by leoetlino almost 7 years ago

  • Status changed from New to Accepted
Actions #2

Updated by NarryG almost 7 years ago

Turns out there's an error in this issue. It applies to more than just the stick. Buttons on the nunchuck can be in the wrong state. That is, Z can be stuck pressed down on load and pressing it acts as if it was released. When you release the button it then goes back into the pushed state.

I'm going to create a new issue as there's no way for me to edit the title/description of the original post.

Actions #3

Updated by NarryG almost 7 years ago

As you said on IRC you could just update the main post, scratch that and this one can just be updated by someone, apologies. When I say "can", I mean that it wasn't happening every single time which is a bit odd. All savestates were made with no buttons pressed

Actions #4

Updated by Helios almost 7 years ago

  • Subject changed from When loading a savestate made in "Real Wiimote" mode with a nunchuck attached, the neutral position of the analog stick is improperly set if the controller interface has been re-initialized (emulator restarted or adapter reconnected) to Savestates breaking analog neutral states
Actions #5

Updated by BadFlo over 6 years ago

I have the same issue, very problematic on games with very few savepoints xD

Actions #6

Updated by BadFlo over 6 years ago

BadFlo wrote:

I have the same issue, very problematic on games with very few savepoints xD

Small workaround: Unplugging/Replugging the Nunchuk after Loading the SaveState solves the issue for this load, not next ones.

Actions #7

Updated by Billiard26 about 6 years ago

Actions #8

Updated by Billiard26 about 6 years ago

  • Subject changed from Savestates breaking analog neutral states to Savestates cause real wiimote extensions to malfunction

Not syncing the extension encryption key in particular is the exact cause of this issue. We really make no attempt to save/load the state of real wiimotes. An attempt to do this is going to be fairly hacky and I'd vote for a forced disconnect/reconnect instead.

Actions #9

Updated by Billiard26 almost 6 years ago

  • Status changed from Accepted to Fix pending
  • Assignee set to Billiard26
Actions #10

Updated by Billiard26 over 5 years ago

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

Also available in: Atom PDF