Project

General

Profile

Actions

Emulator Issues #12697

open

Super Monkey Ball 2 performance regression with debug code

Added by MandL27 over 2 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
Yes
Relates to usability:
No
Relates to performance:
Yes
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Super Monkey Ball 2

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

GM2E8P

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

29dd871cf4a00b2455c9d03e9328e7bd

What's the problem? Describe what went wrong.

With the debug AR code enabled, the game runs exceedingly slow (35-37fps) regardless of video backend. This slowdown didn't happen on earlier Dolphin versions, nor does it lag console to my knowledge.

What steps will reproduce the problem?

Add the following Action Replay code to GM2E8P:

185BC473 00000003
005BC473 00000003```
Launch the game and enter the debug menu (Test Mode in the ascii menu over the title screen, or press Start within userland menus). Framerate should hover around 35-37fps.

**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, this lag occurs on 5.0-15255

**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 is 5.0-14581

**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**

N/A, not a graphics-related issue

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

Windows 10 21H1
Intel Core i7-10750H CPU, 2.6GHz
NVidia GeForce GTX 1660 Ti GPU
16 GB RAM

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

Logs, config, and saves were identical across all versions tested.
Actions #1

Updated by JosJuice over 2 years ago

  • Milestone set to Current
  • Regression changed from No to Yes
  • Relates to performance changed from No to Yes
  • Regression start set to 5.0-14581
Actions #2

Updated by AdmiralCurtiss over 2 years ago

I suspect the bisect is wrong, and it just happened to look fixed between 5.0-14562 and 5.0-14581 due to a bug in https://github.com/dolphin-emu/dolphin/pull/9522 -- maybe check if it lags in 5.0-14559 too.

Actions #3

Updated by MandL27 over 2 years ago

Yep, lags on 5.0-14559 as well.

On a whim, I fired up 5.0-10879 since I was noticing small in-game bits of lag I hadn't seen before and got even better performance there. Even the most demanding backgrounds (Space Colony is a big offender) were hitting 65-70fps minimum with speed set to unlimited. I tried bisecting that one, but Git didn't like something with the submodules so most of the build attempts failed due to undefined QTDIR.

Actions #4

Updated by JosJuice over 2 years ago

  • Regression start deleted (5.0-14581)
Actions #5

Updated by JMC4789 over 1 year ago

  • Milestone deleted (Current)

Try git submodule update --init on builds with submodule issues. Without a bisect this issue will be invalidated eventually. I'll leave it open now, but removing milestone.

Actions

Also available in: Atom PDF