iRacing: Best app.ini for Network Latency Optimization

The objective is to ensure your client receives the highest resolution of opponent data ($D_{opp}$) without overwhelming your local CPU’s communication thread.

File Path & Setup

1. Navigate to: C:\Users\[YourName]\Documents\iRacing\app.ini
2. Open with: Notepad or a text editor.
3. Pro Tip: In the 2026 iRacing UI, many of these are tucked away in “Account Options,” but the .ini remains the only way to force the Net Tick Rate beyond standard presets.

Optimized “Netcode Guard” Configuration Table

Parameter	Recommended Value	Technical Purpose
max_bandwidth	100000	Ensures the server sends you the maximum data per packet.
Net_Tick_Rate	60	Matches the server’s update frequency for 1:1 sync ($S_{sync}$).
replayPacketSize	1024	Stabilizes data flow for live telemetry and ghost cars.
max_cars	63	Set to maximum; culling should be done via Draw Limit instead.
dynamic_network	0	Disables auto-throttling which can cause “Blinking” ($B_{link}$).

[Communications]
max_bandwidth=100000
Net_Tick_Rate=60
replayPacketSize=1024
dynamic_network=0
max_cars=63

[Graphics]
; Note: Set these in the UI, but verify here
MaxCarsToDraw=20  ; Critical for CPU-bound latency

HowTo: Engineering the Low-Latency Pipeline

Follow these GameEngineer.net technical steps to stabilize your connection:

1. The Bandwidth Handshake: Set max_bandwidth=100000. In 2026, even basic fiber/broadband handles this easily. This forces the iRacing server to send you the full “New Gen” telemetry packet for every car in your max_cars list, reducing position errors.
2. Disabling Dynamic Network: Change dynamic_network to 0. By default, iRacing tries to lower your data rate if it detects “jitter.” This often makes the problem worse by lagging your position for other drivers. Turning this off forces a consistent data stream.
3. The “Max Cars” Strategy: Always set max_cars=63 in the [Communications] section. However, go to your in-game Graphics settings and set Cars to Draw to a lower number (like 20). This way, your network knows where everyone is ($P_{coord}$), but your CPU doesn’t waste cycles rendering them, keeping your input latency low.
4. Ethernet Optimization: Ensure you are using a wired connection. In the app.ini, verify Net_Tick_Rate=60. If this is lower, your client is “guessing” where cars are between server updates, leading to the infamous “Netcode” contact where cars touch without visually overlapping.
5. Windows Power Throttling: Ensure High Performance power mode is active. If Windows throttles your Network Interface Card (NIC) to save power, you will see “Jitter” in your iRacing Q bar ($J_{net} > 5ms$).

Technical Explanation: Packet Frequency ($F_p$) and Interpolation

iRacing uses a “Client-Side Prediction” model. When a packet is lost ($P_{loss}$), your PC predicts where the opponent’s car will be based on its last known velocity ($V$) and trajectory.

$$Position_{predicted} = P_{last} + (V \times \Delta t)$$

By increasing the max_bandwidth and ensuring a stable Net_Tick_Rate, we reduce the $\Delta t$ (time between updates). The smaller the $\Delta t$, the more accurate the prediction. When your configuration is engineered correctly, the “Ghosting” effect is minimized because your client has more “Real Data” and needs to “Guess” less, resulting in the safest wheel-to-wheel racing possible.