Project

General

Profile

Actions

Emulator Issues #11642

closed

Real Wiimote not always working after loading a save state with recent change also slowing down responsiveness after loading a savestate

Added by jonrico about 5 years ago. Updated about 4 years ago.

Status:
Fixed
Priority:
Low
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-11684

Description

Game Name?

Super Mario Galaxy 2, Xenoblade Chronicles but applies to all games.

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

SB4P01 (SMG2)

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

4765b7e7a547aeaf308dd2dbc3e6f7dd

What's the problem? Describe what went wrong.

When loading save states when using a Real Wiimote (motion plus, official Nintendo) the controls do not always work after loading.

What steps will reproduce the problem?

  1. Start a new instance of Dolphin.
  2. Load Super Mario Galaxy 2 and load a save game using the Wii loading system, not a save state.
  3. Save your game using a save state.
  4. Quit Dolphin.
  5. Start Dolphin and Super Mario Galaxy 2 and load your previous save state.
  6. Play a bit and save a new save state.
  7. Load that new save state as soon as you save it.
  8. Sometimes the controls will not be working after the disconnect/reconnect of the Wiimote that was added in build 5.0-9808

Holding down a button on the Wiimote or a direction on the Nunchuck seems to make the failure more likely.

A secondary problem with the 9808 solution is that time taken to do the disconnect/reconnect is sufficient to make save states less useful in timed or dangerous situations because you dont have control for 1-2 seconds.

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. Latest tested version is 9808.

Is the issue present in the latest stable version?

No because the disconnect/reconnect was not implemented there. There are other issues with this in stable.

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

  1. But again a different issue across Dolphin instances existed before hence the fix in 9808.

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)

Core i7 4770K, Nvidia 1080TI, Windows 10

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

No data I can supply will be useful here I think. Ideally the disconnect/reconnect would only happen when required - i.e not within a single session of Dolphin. It may also be useful to have a config option that we could apply to switch this on and off on a game config level. Ideally this could be changed when the game is running without having to restart.

Actions

Also available in: Atom PDF