Shameless cry for help

[degasus]

The GPU handles the graphics stuff, but all kind of API validation overhead is handled by the CPU. Emulators tend to abuse the GPU in different ways which are light for the GPU but hard for the CPU. So the used API has a big impact on CPU overhead. However, higher resolution only increase the GPU load.

[mstreurman]

(02-22-2018, 12:39 AM)debeant Wrote: Yeah, that works really good.

Now I'm curious, why does that work as well as it does? I thought all the graphics stuff was handled by the GPU.

I'm not saying you don't know what you're talking about, I'm asking a genuine question because it doesn't mesh with my personal knowledge base.

Dolphin stable is basically a snapshot where most regressions from before that version have been fixed. Usually the development versions are a lot more stable because any issues found will be ironed out in the PR that makes the changes.

[Nintendo Maniac 64]

Unfortunately it seems the OS installation on my Phenom II PC may be slighty borked due to a bunch of stability testing I was doing. On the surface the OS seems fine and I can run all my CPU and GPU stability tests without issue, but when I try to launch Dolphin I get a DLL missing error, and installing the according C runtime update to fix the error also fails.

So yeah, I'm not going to be able to confirm/deny whether 37fps on Sand Ocean in Dolphin 5.0 is accurate. However, I myself remember getting around 33fps or so on a nearly 3GHz Athlon 64 x2 on Sand Ocean around 5 years ago, so 37fps on a 2.7GHz Phenom II with Dolphin 5.0 sounds about right.


And with regards to how to make F-Zero GX run at 30fps and possibly even 45fps without any reduction in game speed, I believe you can just lower the value on the "CPU clock override" setting to something like 375MHz or 250MHz － just don't be surprised if that setting causes other issues.

[debeant]

(02-22-2018, 11:15 AM)Nintendo Maniac 64 Wrote: Unfortunately it seems the OS installation on my Phenom II PC may be slighty borked due to a bunch of stability testing I was doing.  On the surface the OS seems fine and I can run all my CPU and GPU stability tests without issue, but when I try to launch Dolphin I get a DLL missing error, and installing the according C runtime update to fix the error also fails.

So yeah, I'm not going to be able to confirm/deny whether 37fps on Sand Ocean in Dolphin 5.0 is accurate.  However, I myself remember getting around 33fps or so on a nearly 3GHz Athlon 64 x2 on Sand Ocean around 5 years ago, so 37fps on a 2.7GHz Phenom II with Dolphin 5.0 sounds about right.


And with regards to how to make F-Zero GX run at 30fps and possibly even 45fps without any reduction in game speed, I believe you can just lower the value on the "CPU clock override" setting to something like 375MHz or 250MHz － just don't be surprised if that setting causes other issues.

Thanks, but the Vulkan thing seems to have fixed the vast majority of my speed issues. I've got a feeling once I get my new motherboard and CPU in I won't have any issues with speed for a long time, though I'll be the first to admit that I plan on upgrading to a more powerful CPU after a year or two, and a more powerful graphics card in the same time frame.

Not just for emulation.