Emulator Issues #10080
closed
System Interrupts increase over time
0%
Description
Game Name?
Testing with Wind Waker, but occurs with all Gamecube games
Game ID? (right click the game in the game list, properties, info tab)
GZLE01
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
d8e4d45af2032a081a0f446384e9261b
What's the problem? Describe what went wrong.
Gradually increasing FPS fluctuations over time with System Interrupts spiking to well in excess of 10 to 20% after a few hours. Occurs only with Xinput enabled and Wiimote set to real.
What steps will reproduce the problem?
Start a Gamecube game with XInput configured and Real Wii Remote set for emulated Bluetooth. Then play for a few hours without allowing the controller to be disconnected. Can also catch a glimpse of the issue after half an hour by pausing the emu and opening task manager and observe System Interrupts while rapidly moving both sticks.
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?
5.0-2178, but occurs with all versions starting with 5.0-881. Does not occur with earlier versions, nor with current versions with DInput in use or Wiimote set to emulated or none.
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel 4790k overclocked @ 4.7Ghz, Nvidia GTX Titan (Maxwell), Windows 10 Pro AU, Samsung 950 Pro NVMe
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Log and configuration files attached with RAR5 compression.
Issue #9893 a possible duplicate.
Files
Updated by ichee about 8 years ago
Using Wireless Xbox One Controller, but have tested with a Wired 360 Controller.
Updated by leoetlino about 8 years ago
- Status changed from New to Questionable
A somewhat dubious issue, because the relative IR code only runs for emulated Wii remotes and for Wii games. You are using a real Wii remote in a GC game.
Are you sure about your bisect result?
Updated by ichee about 8 years ago
Yes, and I'm not using a Real Wiimote for GameCube games. It's just set to real for Wii games so I don't have to configure again, although the issue doesn't occur if set to emulated or none. I'm using a Wireless Xbox One controller.
Updated by ichee about 8 years ago
ichee wrote:
Yes, and I'm not using a Real Wiimote for GameCube games. It's just set to real for Wii games so I don't have to configure again, although the issue doesn't occur if set to emulated or none. I'm using a Wireless Xbox One controller.
5.0-876 is a possible source of the issue, but there is no windows build to test.
Updated by ichee about 8 years ago
5.0-876 is the cause of the issue but only with continuous scanning enabled with wiimote set to real. Can be a tricky issue to reproduce, but does not occur with 5.0-867 or earlier. Seems an unusual issue given a wiimote would not be in use with a Gamecube game. Maybe a possible conflict with the wiimote changes in that build and the current xinput implementation for Gamecube controls. Might also be a Windows only issue.
Updated by ichee about 8 years ago
Curiously, starting Dolphin with the Qt interface does not seem to cause the issue, regardless of settings.
Updated by JosJuice over 7 years ago
- Milestone set to Current
- Regression changed from No to Yes
- Regression start set to 5.0-876
Updated by JosJuice over 7 years ago
- Status changed from Questionable to Accepted
Updated by JosJuice over 7 years ago
- Status changed from Accepted to Fixed
- Fixed in set to 5.0-5326
- Operating system Windows added
- Operating system deleted (
N/A)