

Let me know what you think if you’ve tried it.RetroArch Android is a very special emulator that, instead of focusing on a single console, such as Playstation or SuperNintendo, attempts to include all kinds of consoles and games, thus being able to emulate thousands of game titles to perfection. Have anyone also tried playing around with this? For me it’s a nice tweak with some real potential, since some games appears to run better with it, at least with more uniform fps. Since then, I’ve let the clock speed stand at 45 in my settings. Setting it too low would trigger a glitch (Spidey falls into the pit instead of landing on the next platform when he gets out of the office building), thus rendering the game practically unplayable. One time I was tinkering with the value while playing the chase between Spidey and Venom, and I found out that the lower the value, the more ahead in the chase Spidey would be in the cutscene when they crash into and ran though the office building. Both SM and MoH become noticeably more stable (and enjoyable, for me personally) when the value is lowered.īut you cannot set it too low either. In MGS, the introductory cutscene (with the submarine) runs much more smoothly and has much less significant dips when the value is lowered on the other hand, Snake seems like in slo-mo in in-game segments. I’ve been testing three games regularly, among others, which are Metal Gear Solid, Spider Man and Medal of Honor. Though, by lowering the value, another result might be that real speed in in-game segments (for example when you really get to control the character) might also become lowered, making it feel like as if the game was running in slo-mo, though the count still say 60 fps. This is not just a superficial change in fps number, I’ve noticed real change in speed.

But on a lower value, though the game might feel a tad laggier (though the count still say 60) in those same less demanding areas, it would only go to 50-55 when changing to more demanding areas.

Thus, overall, the experience feels a lot smoother, since the overall fps is much more uniform.Ī typical example might be like this: on the default clock speed (50), a certain game might run at 60 fps in less demanding areas and could dip right into the 30s or 40s when there’s a lot of stuff to render. By lowering the clock speed value, I’ve noticed that it feels like some games seem to run at a slightly lower fps (like a couple of frames slower, even though the count still says 60), but the result of that is (I guess) noticeable dips also stop being that noticeable. Most of the games I’ve been testing are 3D heavy games, so those dips happen frequently enough and are quite easy to spot. I once accidentally found out that by lowering the clock speed some games seemed to run smoother, meaning less noticeable dips in fps. It concerns lowering the PSX clock speed value. I’ve never seen anyone mention this tweak, so I want to discuss it here.
