Fixing a Game That Runs Too Fast or Too Slow in an Emulator

A game can appear too fast because fast-forward or an unthrottled mode is active, too slow because the host misses real-time deadlines, or merely unfamiliar because a PAL and NTSC release has different intended timing. Display cadence can create judder without changing simulation speed, and original hardware itself could slow down under load.

Those are different diagnoses. Establish a clean baseline and measure audio, emulation speed, and frame time before modifying CPU clocks or synchronization.

Step 1: remove accidental speed controls

Release the fast-forward hotkey and check Settings → Frame Throttle for fast-forward rate, slow-motion ratio, and related controls. Disable rewind, run-ahead, frame advance, recording, netplay, and cheats for the test. A stuck controller binding or conflicting keyboard hotkey can repeatedly activate throttle controls.

Restart the frontend and launch normally, not from a save state created under altered speed. Observe whether music pitch, game timers, and animation all change together. If only motion cadence looks uneven while audio and timers remain correct, investigate refresh-rate stutter rather than emulation speed.

Step 2: read the core’s reported rate and region

Enable RetroArch’s frame-rate display and record the core’s target and observed rate. “60 FPS” is not universal: PAL, NTSC, arcade, handheld, and computer systems can use different rates, including fractional values.

Settings → On-Screen Display → On-Screen Notifications
         → Display Framerate

Check Quick Menu → Core Options for an automatic/NTSC/PAL/region choice only if the core documents one. Most maintained cores detect ordinary content correctly; do not force a region merely because a generic guide says PAL equals 50 and NTSC equals 60. Verify the content region and revision by hash or trusted metadata.

Step 3: distinguish intended regional timing

A PAL release may be designed, converted, or optimized differently from its NTSC counterpart. Running each at its documented native timing is not an emulator fault even when side-by-side speed differs. Conversely, forcing PAL content into NTSC timing can alter music, physics, or cutscene synchronization.

Use the region intended by the specific dump and game. Do not download a different ROM or disc image to test speed; use your own lawful copies and record hashes. If comparing releases, treat them as distinct content revisions.

Step 4: confirm the host reaches full speed

If audio breaks up and the reported rate falls below target, return internal resolution, antialiasing, shaders, texture packs, and enhancement options to defaults. Close background recording and heavy workloads. Test on AC power and check thermal throttling and system power mode.

The emulator’s default CPU engine is usually selected for a balance of speed and compatibility. Do not blindly switch to a JIT or unsafe recompiler mode based on another emulator’s menu. Read the exact core documentation; some systems have no user-facing engine choice, and interpreter modes may exist for debugging or compatibility.

Dolphin’s performance guide warns that lowering Emulated CPU Clock Rate below 100% can make the game itself lag and may break titles. Return clock overrides to default before diagnosing host performance. Raising the clock can also make emulation more demanding and changes emulated behavior.

Step 5: separate original hardware slowdown

Some games intentionally drop rendered frames or slow simulation when the emulated console is overloaded. Accurate emulation can reproduce that behavior while the host emulator remains at 100% speed. An FPS overlay showing full video timing alongside in-game slowdown is a clue.

Compare with authoritative hardware captures or the emulator’s compatibility documentation. CPU overclock hacks may reduce original slowdown but create a modified experience and can break timing. Label such an enhancement rather than calling it a repair.

Step 6: restore audio/video synchronization defaults

RetroArch uses dynamic rate control to reconcile small differences between content and display clocks. Its official troubleshooting guide says proper video/audio synchronization is difficult without it. Turning dynamic rate control off is not a general fix for “wrong speed”; it can exchange a tiny correction for drift, crackling, or repeated frames.

Restore Settings → Audio → Synchronization and Settings → Video → Synchronization defaults, set a conservative audio latency, and verify the display-reported refresh. Small resampling correction should not be confused with a 50-versus-60 region error or a core running at 80% speed.

Step 7: test VSync without misdiagnosing cadence

VSync normally controls presentation, not the console’s intended CPU clock. However, Dolphin documents a case where VSync with a display limited to 30 Hz can cause exact half speed. If speed is precisely halved, check the active display mode, dock, cable, television, and compositor.

Temporarily toggling VSync can isolate that specific interaction, but tearing during the test is expected. Restore a documented synchronized setup afterward. Do not disable VSync globally to hide periodic judder.

Step 8: verify refresh and variable-refresh modes

Compare the core’s actual rate with the display mode. A fixed 60.00 Hz panel and content near 59.94 Hz can require occasional cadence correction while the game still runs at correct speed. RetroArch’s Sync to Exact Content Framerate may help on a compatible variable-refresh display, but only when the rate lies inside the supported VRR range and the full display path supports it.

Do not force the emulated machine to a convenient display rate. Choose an appropriate display mode or a small documented resampling correction.

Step 9: inspect overrides and per-game hacks

A content or core override can silently reapply region, frameskip, clock, renderer, or throttle settings after global defaults are restored. Inspect Quick Menu → Overrides and Manage Core Options. Back up files before removing them, then test with a clean configuration.

Frameskip can make motion look faster or jerkier while game logic runs normally. Speed hacks may be game-specific. Change one setting at a time and restart content when required.

Step 10: document the success criteria

Use a known timer, music passage, or fixed gameplay sequence. Record wall-clock duration, reported core rate, emulation-speed percentage if exposed, frame-time graph, audio stability, region, core version, content hash, CPU engine, clock override, VSync, display refresh, and shaders.

Run the test after restart and with a second title from the same system. A global correction that fixes one PAL conversion but breaks native NTSC content belongs in a content override.

Correct speed means game timers and audio match the intended release, the core sustains real time, and display presentation is even. It does not mean every counter rounds to 60 or every instance of original-hardware slowdown disappears.

Related:

Sources: