Dolphin, the GameCube and Wii emulator - Forums

I'm not sure where to post, but I'll try here.

I'm running Dolphin 5.0-5667 on Android 7, and when running Metroid Prime (GameCube), the screen will go black when pressing 'Z' during gameplay (which I think opens the map?), as well as at the ends of most cutscenes, and in every save station. When this happens, I repeatedly mash 'A', and am rewarded with a brief flicker of gameplay, more black, and finally full gameplay. Judging by the audio, the game is not hanging, but simply not showing overlays of in-game menus.

Is there a fix or diagnosable problem?

I haven't heard of this problem before. It could probably be caused by the graphics driver.

It's an Adreno 506, OpenGL ES 3.2. I might note that I have to run the game at 0% clock speed to get it going up to half speed in the best case scenario. I'm also using Scaled EFB Copy and Disable Fog.

0% clock speed? That's a typo, right?

No. 0% Clock speed.

The last frame I see landing on Tallon Overworld...

... then everything goes black.
But after walking forward a bit and mashing 'A' like a fiend, a brief flicker, followed by black screen,

... and I'm back!

Note these glorious FPS counters. Typically, they flicker in the range of 12-28 FPS, but I managed to catch 0.91 by pure unwitting luck.

(10-13-2017, 02:49 AM)JosJuice Wrote: [ -> ]0% clock speed? That's a typo, right?

... Wait, that's not a big problem, is it?

Yes it is. I'm not even sure why we allow it to go to 0%. I'm amazed it boots at all at that setting.

Set it back to 100%.

You don't necessarily need to have it at 100%, but... yeah, having it at 0% should make things not run at all.

...huh. So does a decrease in clock speed actually have any effect on game speed, as far as making slow games closer to normal? i.e. is there a balance point between slowing down the emulator and speeding up the phone?

EDIT: Wait. How is it even running at zero percent?