Emulator Issues #9178
closedMetroid Prime 2 menu slowdown on first run only
0%
Description
Game Name?
Metroid Prime 2 (Gamecube version)
Game ID?
G2ME01
MD5 Hash?
ce781ad1452311ca86667cf8dbd7d112
What's the problem? Describe what went wrong.
When it is run immediately once Dolphin starts, Metroid Prime 2's title screen and menu run at a little under half speed (~25 FPS / 25 VPS / 40%). This effect will go away if the run is stopped and Metroid Prime 2 is run again. Then the menu and title run at full screen.
What steps will reproduce the problem?
- IMPORTANT: This may only appear on Dolphin for Mac. I have not confirmed this.
- Launch Dolphin.
- Launch Metroid Prime 2. The menu screen and title screen will be slow.
- Close Metroid Prime 2.
- Launch Metroid Prime 2 again. The menu screen and title screen will be full speed.
Note: You can launch Twilight Princess, and I suspect any game will work, instead in step 3 and the menu will be full speed in Step 5 anyway.
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?
I have tested this on 4.0-8258, -8396, -7528, and also the old 5.0-rc-27. All exhibit this behavior.
What are your PC specifications? (CPU, GPU, Operating System, more)
Late 2011 MacBook Pro
2.4 Intel Core i7 (Sandy Bridge), AMD Radeon HD 6770M (1024 MB), 8 GB RAM
Mac OS X 10.9
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
The following steps have NO EFFECT on the first-run slowdown:
• Changing the Internal Resolution, EFB, XFB, Antialiasing, Vsync, Anisotropic filtering, or other graphics settings.
• Disabling system Vsync.
Updated by SoItBegins almost 9 years ago
Did I really say 'full screen' in the bug description? I meant 'full speed'.
Updated by rancourttommylee almost 9 years ago
this bug it's since dolphin 4.0-7864
Updated by JMC4789 about 7 years ago
- Status changed from New to Working as intended
The change probably made the menu harder to run. The second time I'm wondering if a cache is hit or something. Either way, it works fine for me so I can't really do much. There's not even a performance drop, and no one else has reported anything at all.
I'll notify the change's creator though regardless to see if there's any potential reason to keep this open.