Fixing Emulator Netplay Desyncs Without Guessing
A deterministic checklist for core versions, content hashes, firmware, settings, saves, latency, and rollback state when peers diverge.
A desync means peers no longer compute the same emulated state from the same input timeline. More bandwidth rarely fixes it. Start by making the simulation identical.
Establish identical inputs
Record the frontend and core/emulator versions, platform, content hash, firmware hash, region, patches, cheats, controller type, and per-game overrides. Disable run-ahead, rewind, nondeterministic hacks, and unverified enhancements. Start from the same save data or a clean state; do not exchange version-sensitive save states as a shortcut.
Separate latency from determinism
Packet loss or jitter causes stalls and rollback pressure, but a deterministic engine can usually recover within its window. If the game diverges at the same event every time, investigate emulation settings or unsupported determinism. If divergence follows network bursts, reduce rollback frames, improve the path, and avoid Wi-Fi congestion.
Reproduce and document
Test a short sequence with hashes/logs enabled where supported. Add one enhancement at a time after a stable baseline. When reporting a bug, include exact builds, hashes, settings, host roles, and the earliest repeatable divergence point. “Same ROM name” is not evidence of identical bytes.
Sources: RetroArch netplay documentation, Dolphin netplay guide