Fix Input Lag in Zelda II on Emulators & Switch Online

Updated 6 November 2026 · Standard formula, shown below

Input lag in Zelda II: The Adventure of Link can make the game feel unresponsive, especially during combat and the notoriously difficult platforming sections. This guide covers practical fixes for both emulators and the Nintendo Switch Online (NSO) version, helping you reduce delay and improve your reaction time.

What You’ll Need

Access to your emulator’s settings (e.g., RetroArch, Mesen, FCEUX) or the Switch Online app settings.
A controller that supports wired connection (for Switch) or low-latency Bluetooth (for PC).
For NSO: a Nintendo Switch Online subscription and the NES app installed.
Optional: a display with a ‘Game Mode’ or low-latency setting.

Step-by-Step

Enable Game Mode on your TV/monitor. This is the single most effective fix. Go to your display’s settings and turn on ‘Game Mode’ or ‘Low Latency Mode’. This disables most post-processing that adds delay.
Use a wired controller (Switch). On Nintendo Switch, connect your Pro Controller or Joy-Cons via USB cable. Wireless Bluetooth adds about 8-16ms of latency. For emulators on PC, a wired USB controller is also recommended.
Adjust emulator video settings. In RetroArch, go to Settings > Video > Output. Set ‘Video vsync’ to ON (or ‘Adaptive’), and ensure ‘Frame Delay’ is set to 0 or a low value (1-2). In Mesen, go to Options > Video and enable ‘VSync’ and set ‘Frame Delay’ to 0.
Disable ‘Hard GPU Sync’ and ‘Threaded Video’ (RetroArch). These can sometimes add input lag. Go to Settings > Video > Synchronization and turn off ‘Hard GPU Sync’ and ‘Threaded Video’ if you experience stutter or added delay.
Use a low-latency audio driver. In RetroArch, go to Settings > Audio > Output and choose ‘ALSA’ (Linux) or ‘WASAPI’ (Windows) with ‘Audio Latency’ set to 64ms or lower. In Mesen, set ‘Audio Latency’ to 32ms or 64ms.
Enable ‘Run-Ahead’ (RetroArch). This emulator feature predicts and skips frames to reduce input lag. Go to Settings > Latency > Run-Ahead. Enable it and set ‘Number of Frames’ to 1 or 2. Start with 1 and test; 2 may cause audio crackling.
For NSO: Check the app’s ‘Reduce Input Lag’ setting. In the NES app on Switch, press the + button on the controller, go to Settings, and enable ‘Reduce Input Lag’. This is a built-in option that helps.
Use a CRT filter or shader with low latency. Some CRT shaders are heavy and add lag. In RetroArch, use ‘crt-easymode’ or ‘crt-lottes’ instead of ‘crt-royale’. Or disable shaders entirely for minimal lag.
Close background apps on PC. Close web browsers, Discord, or other software that might use CPU/GPU resources and cause frame drops.
Test with a simple action. After each change, press the Start button and see how quickly Link reacts. Use a consistent test like jumping or attacking to feel the difference.

Common Mistakes

Forgetting to enable Game Mode. Many TVs have it off by default, and it adds 30-100ms of lag.
Using wireless controllers on Switch. Even with the ‘Reduce Input Lag’ setting, Bluetooth adds delay.
Setting Run-Ahead too high. More than 2 frames can cause audio glitches and make the game feel ‘too fast’ or unstable.
Enabling ‘Threaded Video’ in RetroArch. This often increases input lag, not decreases it, especially on slower systems.
Ignoring audio latency. Audio lag can make the game feel less responsive even if video is fine.

Tips

Use a wired Ethernet connection for NSO. If you’re playing online (though Zelda II is single-player), a wired connection reduces network lag, but for local play it doesn’t matter.
Set your display’s sharpness to 0. Some TVs add processing that increases lag; turning down sharpness can help.
Try different emulator cores. If you’re using RetroArch, the ‘Mesen’ core is known for accuracy and low latency. The ‘FCEUmm’ core is also good.
Use a controller with a 1000Hz polling rate. Some PC controllers (like the 8BitDo Pro 2 in wired mode) report faster, but any wired controller is fine.
For NSO, use the ‘Rewind’ feature sparingly. Rewinding can cause temporary input lag if you use it too often.

Troubleshooting

If input lag persists:

Check your display’s input. Make sure you’re using the correct HDMI port. Some TVs have a ‘PC’ port that reduces lag.
Try a different controller. Some wireless controllers have higher latency than others. Test with a wired controller to isolate the issue.
Update your emulator. Newer versions often have latency improvements. For RetroArch, update to the latest stable release.
Disable all shaders and overlays. If you have custom shaders, they might be adding processing time. Turn them off temporarily.
Check your system’s performance. If your PC is struggling to run the emulator, frames will drop and cause input lag. Use the emulator’s FPS counter; it should be at 60 FPS consistently.
For NSO, restart the app. Sometimes the app gets into a bad state. Close it completely and reopen.

Frequently Asked Questions

Q: Is input lag worse on Switch Online than on original hardware?
Yes, generally. The NSO emulator adds some latency, and the Switch’s Bluetooth controllers add more. Using the ‘Reduce Input Lag’ setting and wired mode helps, but it may still feel slightly less responsive than original NES hardware.

Q: Does ‘Run-Ahead’ cause any problems?
It can cause audio crackling or visual glitches if set too high. Start with 1 frame and only increase if you feel the game is still laggy. It also requires a powerful CPU to run accurately.

Q: Can I fix input lag on a TV that doesn’t have Game Mode?
Yes, but it’s harder. Try reducing sharpness, turning off motion smoothing, and using a direct HDMI input. You can also try a different TV or monitor if available.

Q: Why does my wireless controller feel laggy even on PC?
Bluetooth adds latency, and some controllers have higher latency than others. Try using a USB cable or a 2.4GHz wireless dongle instead of Bluetooth. Also, ensure your Bluetooth drivers are up to date.

Q: Does the NSO ‘Reduce Input Lag’ setting affect all games?
Yes, it applies to the entire NES app. It’s a global setting, so it will help with all NES games, not just Zelda II.

Q: Is there a way to measure input lag?
You can use a high-speed camera to record your button press and the screen reaction, but it’s not practical. Instead, use your own feel: press a button and see how quickly Link reacts. It’s subjective but effective.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.