
Hello people of the dolphin forums!
I'd like to discuss with you an unusual finding that I came across;
I've tried many times to run NFS Nitro on my emulator, but usually with poor results; I've tried almost any possible option and tweak, but sadly, framerate was always fluctuating between 42 and 56 FPS.
Today I decided to try to lower the internal render resolution (I usually play with 2X native) to see if I could squeeze some more frames, but even after setting the internal res to native, performance was unchanged, or even lower.
It was then that i decided to try something that I never did before: try to override the emulated Wii CPU clock; I set it to 130% increase, about 865 MHz, but still no change. I then tried to rise it to 200%, nearly 1500 MHz, but the result was a sharp decrease in framerate, usually 30-35 fps.
I said to myself: "But what if I decrease the emulated wii cpu clock then? And it actually worked! I put it at around 72% (523 MHz) and the result was 60 FPS capped, even with 2x native resolution!
My question is, how did that happen?
Has something like this ever happened to you before?
I'd love to hear your opinion
I'd like to discuss with you an unusual finding that I came across;
I've tried many times to run NFS Nitro on my emulator, but usually with poor results; I've tried almost any possible option and tweak, but sadly, framerate was always fluctuating between 42 and 56 FPS.
Today I decided to try to lower the internal render resolution (I usually play with 2X native) to see if I could squeeze some more frames, but even after setting the internal res to native, performance was unchanged, or even lower.
It was then that i decided to try something that I never did before: try to override the emulated Wii CPU clock; I set it to 130% increase, about 865 MHz, but still no change. I then tried to rise it to 200%, nearly 1500 MHz, but the result was a sharp decrease in framerate, usually 30-35 fps.
I said to myself: "But what if I decrease the emulated wii cpu clock then? And it actually worked! I put it at around 72% (523 MHz) and the result was 60 FPS capped, even with 2x native resolution!
My question is, how did that happen?

I'd love to hear your opinion
