Dear Dolphin Community,
I'm currently playing around with the latest Dev Build from Dolphin and the unofficial Ishiiruka-Dolphin Build. Honestly, the Ishiiruka-Dolphin Build runs better than the Dev Build I tested, which is dolphin-master-4.0-6885-x64.
Might be some of the DX11 additions etc.
The major difference is less stuttering with Ishiiruka-Dolphin.
Anyway,
I know, that my AMD APU isn't the best, but is there a way to squeeze more performance config-wise out of Dolphin, so that Metroid: Other M runs better? (Lowering resolution does nothing, tried it).
Specifically the issue seems to be the Shader Compiling Process. (If I am TOTALLY wrong, correct me please. I have no clue how the GC and Wii work internally and if this is specific to Shader Compiling)
Doing stuff, which requires Shaders to be built, like using a (Power) Bomb, Charge Beam or just morphing into the Morph Ball causes parts of the scenery to disappear and the FPS drops down to around 30 - 40 FPS for a second or 2 while it compiles the shaders.
Somehow Dolphin is not showing as much debug info as Ishiiruka-Dolphin, so I'm posting a screenshot from this one with additional debug info.
https://drive.google.com/file/d/0ByZy8Wi...sp=sharing
Another thing I noticed in Metroid: Other M is, if I remain inside the opened door between 2 rooms, the FPS drops to 40 until I either turn back or go on, so that the door closes.
My AMD A8-5600K Black Edition is currently at stock speed, which is 3.6 Ghz.
Cheers,
Maxunit
I'm currently playing around with the latest Dev Build from Dolphin and the unofficial Ishiiruka-Dolphin Build. Honestly, the Ishiiruka-Dolphin Build runs better than the Dev Build I tested, which is dolphin-master-4.0-6885-x64.
Might be some of the DX11 additions etc.
The major difference is less stuttering with Ishiiruka-Dolphin.
Anyway,
I know, that my AMD APU isn't the best, but is there a way to squeeze more performance config-wise out of Dolphin, so that Metroid: Other M runs better? (Lowering resolution does nothing, tried it).
Specifically the issue seems to be the Shader Compiling Process. (If I am TOTALLY wrong, correct me please. I have no clue how the GC and Wii work internally and if this is specific to Shader Compiling)
Doing stuff, which requires Shaders to be built, like using a (Power) Bomb, Charge Beam or just morphing into the Morph Ball causes parts of the scenery to disappear and the FPS drops down to around 30 - 40 FPS for a second or 2 while it compiles the shaders.
Somehow Dolphin is not showing as much debug info as Ishiiruka-Dolphin, so I'm posting a screenshot from this one with additional debug info.
https://drive.google.com/file/d/0ByZy8Wi...sp=sharing
Another thing I noticed in Metroid: Other M is, if I remain inside the opened door between 2 rooms, the FPS drops to 40 until I either turn back or go on, so that the door closes.
My AMD A8-5600K Black Edition is currently at stock speed, which is 3.6 Ghz.
Cheers,
Maxunit