Someone in the Batocera Discord asked last week why their Street Fighter III netplay session kept dropping frames even though their internet was fine. Fifty down, twenty up, nothing else running. The answer wasn’t the Wi-Fi. It was that they were routing through a lobby host sitting three continents away.
This happens constantly on Steam Deck builds. You flash a fresh v43 image, drop in your ROMs, fire up RetroArch’s netplay lobby, and assume the lag is your hardware’s fault. It usually isn’t. Server location does most of the heavy lifting in whether a match feels tight or feels like wading through syrup, and almost nobody building these front-ends actually reads the server list before connecting.
Let’s get into why that list matters more than your overclock settings ever will.
Why Physical Distance Still Wins in 2026
Netplay in Batocera runs peer-to-peer or through a relay, depending on the core and the lobby settings. Either way, data has to physically travel. Light in fibre moves fast, but it’s not instant, and every router hop between you and your opponent adds a few milliseconds. Cross an ocean and you’re looking at 120 to 180ms round trip before your inputs even register. Fighting games with frame-perfect links fall apart at that point. Even slower-paced shooters start to feel off.
Compare that to a lobby hosted 400 miles away. Ten milliseconds, maybe fifteen. Your Steam Deck’s Van Gogh APU isn’t the bottleneck there. Never was.
This is exactly why the Batocera community obsesses over region-tagged servers the way console fighting game players obsess over ping before ranked matches. A detailed technical breakdown from Ars Technica on the Deck’s hardware notes that the unit handles emulation workloads comfortably even on battery, which confirms the lag people report almost never traces back to the SoC. It’s routing. It’s almost always routing.
The EU Angle Nobody Talks About
Here’s where it gets more interesting than “pick the closer server.” A growing chunk of RetroBat and Batocera builds hosted by European uploaders, BygDick’s recent 1.8TB Game Night release being one example, now list EU-region netplay lobbies specifically, separate from US-East or Asia-Pacific options.
Part of that is straightforward performance. Players in Europe usually get better latency from infrastructure physically hosted in Europe. But regional hosting is also increasingly common because online services often have reasons to keep infrastructure and user data within particular jurisdictions.
IBM’s overview of data residency explains why organisations increasingly localise infrastructure geographically. Factors can include privacy requirements, contractual obligations, latency, resilience and the need to keep certain categories of data within specific regions.
That matters even for relatively lightweight services. A netplay lobby may only be handling session information and connection data, but the infrastructure behind it still lives somewhere, and that physical location affects both performance and how the service is operated.
FDC Servers’ breakdown of latency and physical hosting makes the performance side clear: proximity reduces round-trip time, and fewer long-distance hops generally mean more responsive connections. Retro netplay communities feel that difference every day, even if most players never think about where the host is physically sitting.
Setting Up Your Own EU-Aware Netplay Config
Batocera doesn’t make you guess blind here. Inside RetroArch’s netplay menu, lobby entries display a rough geographic tag next to the host, and picking one within your own region shaves off the bulk of avoidable lag before you’ve touched a single graphics setting.
A few things worth doing on a fresh build:
- Check ping to the lobby host before committing to ranked-style matches, not after three rounds of desync.
- Favour direct connection mode over relay when both players are in the EU, since relay adds a hop even at short distances.
- If you’re running a 1TB or 1.8TB collection like the recent Game Night releases, keep your netplay core versions matched exactly. Mismatched RetroArch cores cause desync that looks identical to lag but isn’t fixable by server choice alone.
- Test with a friend on the same continent before assuming your build is broken.
None of this needs new hardware. It’s a five-minute config check that most builders skip because nobody tells them server geography is doing 80% of the work.
Where This Fits Into Your Build
If you’re deep into a CoinOPS or full RetroBat setup already, you’ve probably spent more time curating ROM art than checking netplay region tags. Fair enough, that’s the fun part. But if fighting games or light gun co-op are part of why you built the thing, region awareness deserves the same five minutes you spend picking a wheel theme.
Frequently Asked Questions
Why does my Steam Deck netplay lag even with fast internet?
Fast internet doesn’t fix distance. Round-trip time between you and the lobby host matters more than raw bandwidth, and a host three continents away will lag even on gigabit fibre. Check the region tag in RetroArch’s lobby list before joining.
Does Batocera support region-specific netplay lobbies?
Yes. RetroArch’s netplay browser, built into Batocera, tags lobbies by rough geographic location. Picking a host in your own region cuts round-trip latency significantly compared to joining whatever lobby appears first on the list.
Is relay mode worse than direct connection for netplay?
Generally, yes. Relay adds an extra hop through a third-party server, which increases latency even between two nearby players. Direct connection mode works better when both players are already close geographically, EU to EU for example.
Do mismatched RetroArch core versions cause the same symptoms as server lag?
Often, yes. Desync from a version mismatch feels identical to network lag: dropped frames, input delay and stutter. Always confirm both players are running the same core build before troubleshooting server distance.
What’s a reasonable ping target for fighting game netplay?
Under 40ms round trip feels close to local play for most fighting games. Between 40 and 80ms is playable but noticeable. Past 100ms, frame-perfect links and punishes become genuinely difficult regardless of skill.
Get your region tags right, match your cores, and half your “my build is broken” threads disappear before you’ve touched a single config file.
Discussion