Most lag in Soldier of Fortune II comes from one of three things: dial-up network settings, a server too far away, or packet loss on your connection. Fix the first by setting rate 25000, snaps 40 and cl_maxpackets 100. For the other two, turn on the lagometer with /cg_lagometer 1: it shows whether the problem is your settings, your connection or the server, so you know what to change.
What kind of lag do you have?
| What you see | Likely cause | Fix |
|---|---|---|
| Enemies jitter or jump, mostly in big fights | Network settings too low | Raise rate, snaps and cl_maxpackets |
| Everything is a little late, but smooth | High ping: the server is far away | Choose a nearer server |
| Freezes, then players teleport | Packet loss | Use a cable instead of Wi-Fi, stop downloads, try another server |
| “Connection Interrupted” on screen | No data from the server for a moment | Check your connection; if everyone sees it, the server is struggling |
| The whole screen stutters, even alone | Low frame rate, not lag | See make SoF2 run faster |
Step 1: fix the network settings
The default settings ask the server for a trickle of data, which made sense for 2002 modems. On a modern connection they cause most of the “lag” players complain about. Open the console with ~ and type:
rate 25000
snaps 40
cl_maxpackets 100Each setting is explained in rate, snaps and cl_maxpackets.
Step 2: read the lagometer
Type /cg_lagometer 1. A small graph appears near the corner of the screen. In Quake III engine games like SoF2 it has two parts.
The top line: smoothing
- Blue is normal: your game is smoothing movement between snapshots.
- Yellow means your game ran out of snapshots and had to guess where players are. Short yellow spikes are harmless. Lots of yellow means snapshots are arriving late or not at all.
The bottom line: snapshots
- Green bars are snapshots arriving. The height of the bar is your ping. Low and flat is ideal.
- Yellow bars mean the server held a snapshot back because your
rateis too low. Raiserate. - Red bars are lost snapshots: packet loss between you and the server.
Step 3: choose a server near you
Ping is the round trip from you to the server and back. Under 60 ms feels instant, under 120 ms is fine, and above 200 ms you’ll notice. Distance sets the minimum: a UK player on a server in the eastern US will rarely see below about 80 ms.
- The in-game browser shows each server’s ping. You can hide far-away servers with cl_maxPing, for example
/cl_maxPing 150. - SOF2MP.com’s live server list shows each server’s country, so you can find busy servers near you.
Step 4: fix packet loss
Red on the lagometer means packets are being lost. Usually that’s on your side:
- Use a cable. Wi-Fi drops packets when the signal is weak or busy. An Ethernet cable is the single best fix.
- Stop big downloads and uploads on your network while you play: game updates, cloud backups, video streams.
- Keep
cl_packetdup 1, or try2on a poor connection. It resends your recent commands so a lost packet doesn’t lose your input. - Restart your router if it hasn’t been restarted in weeks.
- Try another server. If you lose packets only on one server, the problem is on its route or its host, not your side.
Settings that change how lag feels
These don’t fix a bad connection, but they change how your game handles it:
| CVAR | What it does | Default | Recommended |
|---|---|---|---|
cg_antiLag | Enables the anti-lag hit compensation system. | 1 | 1 |
cg_smoothClients | Applies client-side interpolation to smooth other players' movement. | 0 | — |
cg_predictItems | Predicts item pickups on the client before server confirmation. | 1 | 1 |
cg_impactPrediction | Predicts bullet impact effects client-side for immediate visual feedback before server confirmation. | 1 | 1 |
Leave cg_antiLag on. It lets the server account for your ping when it checks whether your shots hit, so you aim at what you see.
When it’s the server, not you
If everyone on a server sees “Connection Interrupted” or lag at the same moments, the server itself is overloaded or its connection is poor. There’s nothing to fix on your side. Tell the server admin, and play somewhere else meanwhile. If you run the server, see server bandwidth and performance.
Frequently asked questions
Why is SoF2 so laggy on fast internet?
Because the default network settings are dial-up values. Set rate 25000, snaps 40 and cl_maxpackets 100.
How do I show my ping in SoF2?
Hold the scores key (Tab) to see every player’s ping, or turn on the lagometer with /cg_lagometer 1.
What does “Connection Interrupted” mean?
Your game hasn’t received anything from the server for about a second. It’s caused by packet loss, a dropped connection, or a server that has frozen.
What is a good ping for SoF2?
Under 60 ms is excellent and under 120 ms is perfectly playable. Above about 200 ms, hits start to feel noticeably delayed.