“Sorry bro it wasn’t me, it was netcode” mutters some guy whilst your irating takes another 50+ point dump for the 3rd race in a row. If you are the type of person who blames every springbok rugby loss on the ref, you might be the same person blaming on-track incidents solely on netcode.
The topic of netcode is something that has been plaguing Sim racers, more so outside of North America and Europe, for a long time. High ping, erratic packet loss and inconsistent netcode behaviour can all contribute to erratic online racing outside of your control.
What Is Netcode?
Netcode is a system that synchronizes car positions and contact by predicting when there are delays in communication such as packet loss, jittery comms or disconnections. This doesn’t always work as intended. “Ghost” contact, blinking, rubber banding and weird penalties or crashes are all signs that you have a “netcode” issue.
However, netcode is in a lot of cases not solely to blame for the erratic experience in iRacing. To use our previous rugby analogy. Netcode is the referee trying to manage the game fairly despite various issues that arise.
The Contributing Factors
Although netcode is sometimes used as the umbrella term, like I did above, there is more to consider. Here is a breakdown of the main considerations affecting your racing experience and what it means:
| Term | What It Means | In Sim Racing |
| Netcode | The game’s networking system that syncs players, handles collisions, and predicts movement. | Tries to “smooth over” network imperfections. |
| Ping | Time it takes for your data to reach the server and come back (latency, in ms). | High ping = delayed inputs, late positioning. |
| Packet Loss | Some of your data never arrives, lost in transit. | Causes blinking cars, phantom hits. |
| Jitter | Ping isn’t stable, it jumps up and down between packets. | Leads to stuttering or rubber-banding movement. |
If you have downstream connection challenges netcode may incorrectly synchronise the data causing inconsistent game play. Additionally, issues with your ISP and bad routing will further exacerbate these issues.
Unfortunately for players in countries like South Africa, online racing always comes with slightly more risk. Due to the distance from the server farms, you will most likely have more connection challenges affecting your racing in weird ways. Efforts are however continuously being made to improve the iRacing online experience.
Improvements Made So Far
- Regional server farms in Japan, Germany, AUS
- Ping tracing & diagnostic tools
- Connection flag system (ghosts unstable cars)
- Regular improvements to prediction & contact logic
The above measures have made positive changes to the overall game play but improvements are still needed.
What Needs Improvement
It’s important to remember that some connection challenges are not just with a specific gaming title. Stronger connections are also based on infrastructure availability and regional improvements. Holistically, here are some points that require attention:
- More server farms (e.g., South Africa, India, Brazil)
- “Smart” server selection to minimize worst-case ping
- Better peering with global ISPs
- Stronger netcode for jitter tolerance
- Pre-race quality checks & alerts
- Guides for users on testing & improving routing
What You Can Do
Any form of online gameplay is affected by your location. For Sim racing, leagues such as the iRacing Masters ensure racing on an equal playing field for all competitors. Should you venture into the open lobby world make sure you have a wired connection and choose races with regional splits to avoid connection issues. Or just ignore the advise and blame the “referee” for punting your fellow competitor into the barriers…
Want To Join The Masters Grid?
We would love more drivers to join us in the series. The joining fee is minimal, and you will become a faster driver whilst enjoying the racing and getting to know some industry stalwarts in the process! More information can be found here: https://masters-series.co.za/Entry