Optimal Network & Connection Settings for Quake Live

Why Quake Live Is Different

Quake Live is unusually sensitive to timing consistency

• Very small UDP packets — easily affected by buffering
• High update frequency — needs consistent delivery
• Tight hit verification windows — timing precision required
• Client-side prediction with server reconciliation — jitter causes visible corrections

As a result:

• Low jitter matters more than low latency
• Bufferbloat breaks gameplay while "ping looks fine"
• 1 Gbps bandwidth means nothing if packets arrive late or uneven
• Game quality correlates more with stable upload than download or raw ping

Latency vs Jitter

Understanding the difference

Advanced Diagnostics

Additional tests for specific issues

Bufferbloat Test

If you experience lag spikes during uploads/downloads but your idle ping looks fine:

If your grade is D or F, enable SQM/QoS on your router (see Step 2).

Common Symptoms & Likely Causes

Quick diagnosis guide

Common Myths

Clear these up before diving deeper

Understanding the Lagometer

Your primary diagnostic tool for network issues

The lagometer is a real-time graph showing how well your client is receiving data from the server. It's the single most useful tool for diagnosing connection problems in Quake Live.

cg_lagometer 1

How to Read the Lagometer

The lagometer has two graphs stacked vertically:

Visual Examples

Learn to recognize these patterns at a glance:

Test Your Own Connection

Reproduce issues to confirm bufferbloat:

1. Join a server and enable cg_lagometer 1
2. Observe the lower graph — it should be steady green
3. Start a speed test or cloud sync upload on your network
4. Watch the lower graph: if green bars spike during upload, you have bufferbloat
5. Enable SQM/QoS on your router to fix this

Scoreboard Ping is Reliable

The ping shown on the scoreboard uses actual game engine data, not a separate ping tool like some games. It's averaged over a few seconds, so it won't show instant spikes but accurately reflects your real connection to the server.

This means:

• Trust the scoreboard ping for your actual latency
• For spike detection, watch the lagometer instead
• If scoreboard says 40ms but feels like 80ms, the issue is likely jitter (use lagometer to confirm)

How Interpolation, Timenudge & Lag Compensation Work

Important: Understanding these mechanics

cl_timenudge offsets the client render time, reducing (or increasing) that interpolation buffer.

Key points:

• cl_timenudge -20 reduces the interpolation delay by ~20 ms — enemy positions are rendered earlier compared to cl_timenudge 0
• Lower (more negative) values = less buffering = more responsive feel
• Less buffering = less tolerance for jitter or packet loss

cl_timenudge -20 is the recommended default and is commonly used by competitive players. The trade-off is that on unstable connections, reduced buffering can cause visible enemy warping or jitter.

Lag Compensation (Backwards Reconciliation)

Quake Live uses server-side backward reconciliation for hitscan weapons:

• The server checks where the target was at the time of your shot
• Not where they are when the server receives it

Implications:

• Railgun hits register even at high ping (within limits)
• Dodging feels less intuitive vs high-ping players
• Being hit "behind corners" can happen legitimately

Step 1: Eliminate Local Network Issues

Fix problems at the source

Use Ethernet (Mandatory)

• Wi-Fi introduces jitter even with strong signal
• Powerline adapters are unreliable
• Use a direct Ethernet cable to your router

Eliminate Background Traffic

Disable or pause:

• Cloud sync (OneDrive, Google Drive, iCloud)
• Game launchers (Steam, Battle.net, Epic)
• Torrents / P2P
• Smart TVs / streaming devices
• OS updates

Network Adapter Settings (Windows)

Device Manager → Network Adapter → Properties → Advanced

Only change settings that exist on your adapter.

Step 2: Router & ISP Equipment

Reduce bufferbloat and congestion

Enable SQM / QoS (If Available)

Look for:

• SQM
• QoS
• Smart Queue
• fq_codel / CAKE
• "Gaming mode"

Set bandwidth to 85–90% of your real speed (up & down). This prevents bufferbloat.

Bufferbloat Explained

UPLOAD FULL → router queues packets → game packets wait
           → packets arrive late
           → jitter spikes

Ping stays "low" but gameplay breaks.

Test Bufferbloat

Use: Waveform Bufferbloat Test — isolates bufferbloat from clean latency. If your lagometer spikes during an upload or download test, it often indicates bufferbloat.

Disable Packet Inspection Features

If present, disable:

• DPI (Deep Packet Inspection)
• IDS / IPS
• "Advanced security"
• Parental filtering

These cause latency spikes.

ISP-Specific Notes

Step 3: DNS (Correct Expectations)

Keep it simple

Use one resolver:

Step 4: Quake Live Network Settings

In-game cvars that actually matter

rate 25000
com_idleSleep 0
cl_packetdup 2
cl_timenudge -20

About cl_packetdup

Packet duplication sends multiple copies of each input packet. If one copy is lost in transit, the duplicate can still arrive — reducing visible artifacts like player warping or teleporting caused by packet loss.

cl_packetdup 2 is the recommended general default. Duplicate packets add small upstream overhead, but on modern connections this is usually negligible.

• cl_packetdup 0–1 — stable connections with no packet loss
• cl_packetdup 2 — recommended general default
• cl_packetdup 3–5 — lossy or unstable connections

About cl_timenudge

cl_timenudge -20 is the recommended default — it reduces interpolation delay by ~20 ms, making enemy movement feel more responsive. Most competitive players use this value.

Trade-off: less buffering means less tolerance for jitter. If you experience visible warping, try cl_timenudge 0 for smoother interpolation at the cost of slightly higher visual latency.

Recommended Profiles

cl_packetdup 2
cl_timenudge -20

cl_packetdup 3
cl_timenudge 0

cl_packetdup 5
cl_timenudge 0

Step 5: Test Real Quake Live Servers

Test with actual game servers, not synthetic benchmarks

Common EU Test Servers

Ping Test

ping -n 50 57.129.16.240

ping -c 50 57.129.16.240

Look for:

• 0% loss
• Tight min / avg / max
• No large spikes

Route Analysis (Advanced)

Step 6: Interpret Results

What your tests mean

VPNs & Tunnels

• Can improve routing
• Can add latency
• Prefer WireGuard-based tunnels
• Avoid "privacy" VPNs for gaming

Technical Reference

Quick facts