As an Amazon Associate I earn from qualifying purchases. Some links on this page may earn RealIRacing a commission at no extra cost to you. Gear I personally race on is called out as such; other picks are researched recommendations.

Driver settings live in a strange middle ground on the sim racing rig. You can run iRacing on almost any GPU with almost any driver version and still load into a race, but the difference between a carelessly configured setup and one tuned for your hardware is visible every lap. I run an RTX 5060 Ti on my rig. Disabling unnecessary driver features and dialing in power management can improve frame-time consistency enough that you feel the wheel responding more precisely to track surface change. Driver optimization matters more on mid-range cards than flagships, and it matters more in heavy-traffic multiclass than time trials.

Why Driver Settings Matter for iRacing

iRacing is CPU-limited at high refresh rates, but that does not mean your GPU driver is innocent. A GPU driver handles memory management, power states, thermal throttling, and feature enforcement. Aggressive power-saving features can cause micro-stutters when the GPU ramps up under load. Unnecessary post-processing can add latency to frame delivery. Frame pacing features can interact badly with iRacing's own sync mechanisms. The goal is a driver configuration that keeps your GPU awake and responsive without forcing it to work harder than your CPU can feed frames to it.

The cost of getting this wrong is not dramatic. You do not wake up one morning unable to qualify. Instead, you lose half a frame per second consistency, or your minimum frame time spikes once every five laps when the driver decides to do housekeeping. Over a 30-minute race with tight field positions, that translates to lock-ups in corner entry that feel like a momentary loss of precision.

NVIDIA Driver Settings for iRacing

Access the NVIDIA Control Panel

Right-click your desktop and select NVIDIA Control Panel. If you do not see this option, your NVIDIA driver is either missing or needs reinstallation. Ignore the settings in Windows Display settings; they are separate and less granular. The NVIDIA Control Panel is where you control GPU behavior globally.

Critical NVIDIA Settings

Per-Application Profile for iRacing

You can create a profile for iRacing specifically to override global settings. In the left sidebar of the NVIDIA Control Panel, select Manage 3D settings, then the Program Settings tab. Add iRacing (or the iRacingSim executable if it does not auto-populate). Apply the settings above to this profile. This prevents you from accidentally running other applications at maximum power state.

Driver Updates

Update your NVIDIA driver monthly. New drivers fix power-state bugs and improve iRacing compatibility. Do not skip more than two minor driver releases. Older drivers may miss optimizations for newer GPU architectures.

AMD Driver Settings for iRacing

Access Radeon Software

Right-click your desktop and select AMD Radeon Software, or open it from the system tray. AMD's interface is newer and less cluttered than NVIDIA's, but the principles are identical: keep the GPU awake, disable unnecessary post-processing, and let iRacing handle sync.

Critical AMD Settings

Per-Application Profile for iRacing

In Radeon Software, navigate to Performance tab and look for Game Profiles or Per-App Profiles. Add iRacing and apply the settings above. AMD Radeon Software will load these settings automatically when you launch the sim.

Cross-Platform Optimization: CPU and GPU Communication

Both NVIDIA and AMD drivers have options related to CPU-GPU communication speed. NVIDIA calls this PCIe generation management; AMD calls it similar variants. These default to your motherboard's maximum PCIe generation (usually 4.0 or 5.0 on modern boards). Leave them at auto. Forcing a lower PCIe version does not reduce latency; it only reduces bandwidth unnecessarily.

One setting that applies to both architectures: disable any driver-level motion blur, frame interpolation, or AI upscaling features. DLSS, FSR, and XeSS are application-level features that you enable inside iRacing if you want them. Do not enable them at the driver level. Driver-level filters add latency between your frame render and frame display.

Monitoring Frame Times After Optimization

After adjusting driver settings, launch iRacing and load into a practice session at a populated track. Open your performance monitoring tool (NVIDIA: GeForce Experience overlay or a third-party tool like MSI Afterburner; AMD: built-in Radeon overlay). Watch your frame time graph for at least ten minutes. You should see a flat line with no spikes above your target frame time. If you see regular dips (low frame time followed by normal frame time), your GPU is power-throttling; return to your driver settings and verify Power Management is set correctly.

Frame time consistency matters more than peak frame rate. A steady 95 FPS is faster than 120 FPS that occasionally dips to 60 FPS. After driver tuning, your frame-time floor should rise and your variance should shrink. You will notice this first in how the car responds to steering input at high speed and in how the horizon behaves during camera panning.

Driver Version Strategy

NVIDIA releases new drivers every three to four weeks. AMD releases less frequently, roughly every four to six weeks. You do not need to update immediately; wait a week or two after release to let other users catch critical bugs. If your current driver is stable, skip minor updates (like 555.92 to 555.95). Update for major version changes (555 to 556) or if you notice frame-time anomalies that a driver release claims to fix.

Before updating, back up your driver settings. Export your NVIDIA Control Panel settings or photograph your AMD Radeon settings so you can restore them if the new driver resets them. After each update, verify your frame-time consistency has not degraded. Some driver releases improve iRacing performance measurably; others introduce regressions that affect frame pacing.

Rollback Rule

If you update your driver and frame times become erratic, roll back to the previous version immediately. Do not chase frame-time problems for multiple races. A proven driver version matters more than chasing the latest feature set.

Common Mistakes and How to Avoid Them

The driver layer is not glamorous, but it is foundational. A poor driver configuration means your CPU is doing excellent work, your rig is mechanically sound, but the frame you are seeing is 5-10 milliseconds old by the time your hand moves the wheel to respond to it. Clean driver settings eliminate that hidden latency and make your rig feel precise and immediate.

From the RealiRacing shop

Before you go live, free up your rig. NWM PitStop is the clean-up + stream-priority script set we run before every session — our own product, not a third-party pick. See NWM PitStop →

The gear in this guide
PickWhy it made the listTested?
MOZA R9 Direct Drive Wheelbase9 N·m direct drive — the base bolted to my rig right nowRaced on
NVIDIA GeForce RTX 5060 Ti (8 GB)renders iRacing and NVENC-encodes the stream on the same chipRaced on

As an Amazon Associate I earn from qualifying purchases. Some links are affiliate links — I may earn a commission at no cost to you.

Watch it, don't just read about it

I stream and upload iRacing races on my MOZA R9 rig — real laps, real force feedback, real mistakes. See the gear from this guide working before you spend a cent.

▶ Subscribe on YouTube

Skip the trial and error

The force-feedback, pedal and baseline settings I actually race, written up as setup packs for MOZA, iRacing, ACC and Le Mans Ultimate. The opening section of each pack is free to read.

See the setup packs →

Free FFB tuning checklist

The order I tune force feedback in, from rig to wheelbase software to iRacing, plus the clipping check. Enter your email and the checklist opens right here. No spam, unsubscribe anytime.

See the privacy notice.

FAQ

Should I enable NVIDIA DLSS or AMD FSR in iRacing?

Only if you need it to hit your target frame rate. DLSS and FSR reduce frame time by rendering at lower resolution and upscaling, which improves frame rate at the cost of visual clarity and sometimes introduces subtle artifacts. If you run steady 120+ FPS without upscaling, leave it off. If you drop below your monitor's refresh rate in heavy traffic, enable it and test it in time trial first to verify image quality is acceptable to you. Do not enable at the driver level; enable inside iRacing's graphics settings.

What is the difference between NVIDIA Prefer Maximum Performance and Adaptive power mode?

Maximum Performance keeps your GPU in its highest power state at all times, consuming more electricity but eliminating frame-time variance from power state transitions. Adaptive lets the driver downclock the GPU when demand is low and ramp it up under load, saving power but introducing micro-stutters during these transitions. For iRacing, use Maximum Performance because frame consistency matters more than power draw.

Why do my frame times spike every few seconds after updating my driver?

New drivers sometimes trigger shader recompilation on first launch, which can cause temporary frame-time spikes as the GPU builds and caches shader programs. Run a practice session for 15-20 minutes to let compilation finish, then restart iRacing and check if spikes persist. If they do, the driver version may have introduced a regression; consider rolling back to the previous version and waiting for the next update.

Does enabling G-SYNC or Freesync make my racing smoother?

Only if you run variable frame rate and your monitor supports it. G-SYNC and Freesync synchronize the GPU's frame delivery to your monitor's refresh rate, eliminating screen tearing but adding latency. Most sim racers cap their frame rate to a fixed value (like 120 FPS on a 120 Hz monitor), making G-SYNC and Freesync redundant. If you intentionally run uncapped and variable frame rate (not recommended for racing), enable these; otherwise disable them at the driver level and let iRacing manage sync.