Cloud Gaming.Expert
Counterpoint7 min read

Fighting games on cloud — a counter-take

Fighting games are supposed to be the hardest genre for cloud gaming. The conventional take ignores how rollback netcode interacts with the cloud session model. The result is more interesting than the standard verdict.

By Kenji Park
Reviewed

The conventional verdict

Cloud gaming and fighting games: bad fit. The reasoning is straightforward. Fighting games require frame-perfect input — a 1-frame difference in execution distinguishes a successful block from a counter-hit. Cloud gaming adds 30-60 ms of input lag, which is 2-4 frames at 60fps. Frame-tight execution becomes impossible.

This verdict shows up in every cloud-gaming-genre breakdown and is the easiest argument to make. It's also incomplete in a specific way.

What rollback netcode does

Modern fighting games — Street Fighter 6, Tekken 8, Guilty Gear Strive, Mortal Kombat 1 — use rollback netcode for online matches. Rollback predicts your opponent's input, runs the game forward, and corrects when the prediction is wrong by 'rolling back' the simulation a few frames and replaying.

Rollback netcode is designed to mask latency in network conditions where the round-trip is 30-100 ms. The masking is good — modern fighting game players routinely play online matches against opponents on the other side of the country with input feel that's close to local.

How rollback interacts with cloud

Cloud gaming adds latency between the player and the game server. But the game itself is running on the cloud server, and the rollback netcode is running between the cloud-hosted game and the opponent. The rollback is running over a different network path than the player-to-cloud path.

What this means in practice: if you play SF6 on cloud against an opponent on local console, the rollback netcode is masking the opponent-to-cloud latency, not the player-to-cloud latency. The player-to-cloud latency shows up as 'controller lag' but does not affect the in-match interaction with the opponent through the rollback system.

The functional reality is that fighting games on cloud have controller-lag that's noticeable, but the netcode quality is the same as local-vs-cloud-online. Your inputs feel mushy but the matches are otherwise normal.

Where this works in practice

Casual ranked play in fighting games on Game Pass Cloud or GeForce Now is genuinely playable. Tested across SF6, Tekken 8, and Mortal Kombat 1 — match quality is comparable to playing those games online from a local mid-range PC. The controller lag is real but adjustments are quick.

Tournament-level play remains unfit for cloud. The frame-tight execution that distinguishes top players is genuinely degraded by the input lag. But this is true for online tournament play generally, not unique to cloud.

Where the standard verdict is right

Fighting games without rollback (older arcade ports, certain anime fighters, classic 2D titles) suffer on cloud the way the conventional take describes. Without rollback, every frame of input lag stacks linearly and the cloud penalty compounds with the network penalty.

Local-only fighting game scenarios. Two players on the same couch with one playing on cloud is essentially unworkable — the cloud player's input lag is uncorrected and the match feels uneven.

What I'd tell fighting game players

If your fighting game has rollback netcode and you mostly play online, cloud gaming is more workable than the standard verdict suggests. Game Pass Cloud and GeForce Now both run SF6, Tekken 8, and the Mortal Kombat titles well enough for casual-to-mid-tier ranked play.

If your fighting game is older or rollback-less, stick with local hardware. The cloud penalty stacks in a way rollback can't fix.

If you're tournament-tier, you already know what hardware you need and cloud isn't it. But that's true for online tournament play generally, not a cloud-specific limitation.

ShareXRedditHacker News

More from the blog