Emulator Issues #8004


Skies of Arcadia experiences extreme performance drops

Added by DanielKim.7C4 over 9 years ago.

% Done:


Operating system:
Issue type:
Relates to usability:
Relates to performance:
Relates to maintainability:
Regression start:
Fixed in:


Game Name?
Skies of Arcadia Legends

Game ID?

What's the problem? Describe what went wrong in few words.
While using rev 4808 and watching the intro for Skies of Arcadia Legends, the emulator's performance drops drastically, with FPS as low as 3 and VPS as low as 10. The computer itself also experiences slowdown, making it difficult to move the mouse or use the keyboard to stop the emulation.

What did you expect to happen instead?
I expected the game to run at normal speeds as experienced with the older builds.

What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]

  1. Start Skies of Arcadia
  2. Don't press any buttons and watch the intro
  3. At some point doing the intro, the performance drop will happen (it can happen multiple times)

Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
4.0-4808 (experiences slowdown)
4.0-4565 (experiences slowdown)
4.0-4424 (does not experience slowdown)

Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
4.0-4424 did not experience this slowdown

What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Windows 7 Professional x64
Radeon 6870 (driver 13.12)
AMD Phenom II x4 955 (3.2 Ghz)

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Near the end of the log is when the performance drop occurs, with a lot of "Unknown BP opcode" messages being printed.

Related issues 1 (0 open1 closed)

Is duplicate of Emulator - Emulator Issues #8011: HW bounding box issues (video driver crash, slowdowns)Fixed

Actions #1

Updated by JMC4789 over 9 years ago

Bisect it further if you can. That'll make it easier to pinpoint any issues.

Actions #2

Updated by DanielKim.7C4 over 9 years ago

I've narrowed down the revisions as best as I can. Build 4.0-4549 runs okay, but the following build (4.0-4555) is when the issue first appears. Looks like that's when the the D3D bounding box was merged into master?

Actions #3

Updated by JMC4789 over 9 years ago

Okay. That's interesting. Thanks your narrowing it down! I'm guessing you're using D3D?

Actions #4

Updated by DanielKim.7C4 over 9 years ago

Shoot, I knew I forgot to add that to the report. I've experienced it both in D3D and OpenGL, though it seems to happen more often and more severely in D3D.

Actions #5

Updated by JMC4789 over 9 years ago

Can you try turning off logging? That may fix your problem, at least temporarily.

Actions #6

Updated by rigation over 9 years ago

I'm on Nvidia gtx650ti - Win 8.1: tried D3D and in the intro I don't have this kind of slowdown (Dolphin 4.0-4828)

Actions #7

Updated by JMC4789 over 9 years ago

I think this is a case of logs killing performance... That's why I'm saying to try turning off logging.

Actions #8

Updated by DanielKim.7C4 over 9 years ago

I believe the logs were off by default when I first encountered the issue. I enabled them only when making the report.

Just to double-check that I actually have them off, in the Log Configuration I have no log types enabled nor any logger outputs enabled.

Anything else I can do to make sure it's not something weird on my machine?

Actions #9

Updated by JMC4789 over 9 years ago

If you go through the downloads page, test around the Bounding Box merges that happened between the builds that you said worked and did not work well.

Actions #10

Updated by DanielKim.7C4 over 9 years ago

Dolphin 4.0-4557 (experiences issue)
Dolphin 4.0-4555 (experiences issue)
Dolphin 4.0-4549 (does not experience issue)
Dolphin 4.0-4547 (does not experience issue)

Checkin log for 4555: Add HW bounding Box support to d3d backend (PR #1657 from Tinob)

That's what led me to believe it was due to the bounding box support to D3D, but without builds between 4555 and 4549, I can't tell whether that's actually the case.

Actions #11

Updated by JMC4789 over 9 years ago

  • Status changed from New to Accepted

That's because the bounding box merge took up 6 commits, I'm guessing. Either way, that's pretty much exactly what I expected, thanks.

Actions #12

Updated by JMC4789 over 9 years ago

  • Status changed from Accepted to Duplicate

Also available in: Atom PDF