Hoppa till huvudinnehåll
JobCannon
Alla kompetenser

Netcode Rollback Fighting

⬢ NIVÅ 3Tekniskt
Hög
Lönepåverkan
4 månader
Tid att lära sig
Svår
Svårighetsgrad
2
Karriärer
I korthet

Rollback netcode predicts opponent's next move, renders it optimistically, then rolls back if prediction wrong. Used in fighting games (Guilty Gear Strive, Street Fighter 6) for responsive feel even on 100ms+ lag. Mastery takes 8-12 weeks. Creates smooth gameplay at any latency; older lock-step netcode = 200+ms perceived lag. Scarcity is very high; only 10-20 game studios implement rollback well. Salaries: rollback specialists earn 50-100% premium.

Vad är Netcode Rollback Fighting

Rollback netcode is a network architecture for fighting games that predicts the opponent's next move and renders it optimistically. When the real input arrives from the network, the game checks if prediction was correct. If wrong, the game state rewinds to a previous frame and re-simulates with the correct input. The rollback happens in <50ms, invisible to the player. Rollback enables responsive gameplay at high latency (100ms+) that feels local (0ms). Without rollback, latency is perceived as input lag: you press button, wait 100ms for opponent state, then act. With rollback: you press button, opponent state predicted instantly, rollback corrects if wrong.

🔧 VERKTYG & EKOSYSTEM
GGPO (rollback library)Custom rollback enginesPhysics simulationInput predictionUnreal Engine / custom engineC++Network testing toolsRecording/playback systems

💰 Lön per region

OmrådeNybörjareMidErfaren
USA$110k$180k$300k
UK£67k£110k£183k
EU€76k€124k€206k
CANADAC$115kC$190kC$315k

🎯 Karriärer som använder Netcode Rollback Fighting

❓ Vanliga frågor

What's the difference between rollback and lock-step netcode?
Lock-step: every frame waits for opponent input (50ms latency = 3 frame delay). Rollback: assumes opponent input, renders, rolls back if wrong (feels instant). Latency invisible to player. Downside: rollback is complex; lock-step is simple. Fighting games need rollback.
How do I predict opponent inputs?
Use previous N frames of opponent's inputs (last 5 frames), train simple model (neutral = 40%, forward = 30%, attack = 30%). Use probability distribution to pick predicted frame. Refresh prediction when real input arrives. 50-80% prediction rate typical.
What if prediction is wrong?
Rewind game state to last known-good frame. Re-simulate with correct input. Happens imperceptibly (<50ms). Player sees character teleport slightly, then correct itself. Trade-off: better than lag, slightly jittery. Acceptable in fighting games.
Can I use rollback in non-fighting games?
Yes, but overkill for most games. Rollback best for frame-perfect, latency-sensitive games (fighters, shooters, MOBAs). RPGs, strategy games: lock-step fine. Rollback complexity not worth it unless latency critical.
How do I handle desynchronization (player A and B see different game state)?
Deterministic simulation is key: same input + same state = always same output. Use fixed-point math (not floats). Avoid randomness (if used, seed RNG with frame number). Test local vs. networked gameplay constantly; divergence = bug.

Osäker på om den här kompetensen passar dig?

Gör Career Match — vi föreslår rätt spår för dig.

Hitta mina bäst passande kompetenser →

Hitta din ideala karriärväg

Kompetensbaserad matchning mot 2 521 karriärer. Gratis, ~3 minuter.

Gör Karriärmatchningen — gratis →