There is a scene that repeats itself with a certain cruelty in the world of sim racing. You invest in a good wheel, adjust your seating position, spend hours dialing in your field of view, and just when everything seems to be in place, you discover that the real rival is not on the grid but inside the graphics engine itself. You can have a powerful rig and still feel that iRacing, at the worst possible moment, decides to remind you that technological perfection always comes with fine print.
That clash between expectations and reality is precisely what makes iRacing such a particular case. Its value as a simulator is not in question, but neither is the fact that its architecture carries technical decisions that force the user to understand more than they should theoretically need to. And that is where things get interesting: when you step away from the visible menus and into the less friendly layers of the simulator, you discover that you do not always need a new PC to gain performance. Sometimes it is enough to stop asking the game to waste energy on things that contribute nothing to the actual driving.
This article focuses on three of those lesser-known settings that, used correctly, can translate into a meaningful improvement in frame rate stability. These are not promises of instant optimization. They are concrete decisions about how to force the engine to prioritize what matters.
Understanding the Problem Before the Fix
To understand why these changes work, it helps to accept a simple truth: iRacing does not always waste resources where you think it does. Many times the player is focused on the car ahead, the braking point, or the racing line, while the simulator is busy spending CPU time on elements that have nothing to do with the competitive experience.
The result is familiar. During race starts with full grids, on straights beside crowded pit lanes, or in sessions loaded with secondary objects, the frame rate suffers. Not because the simulator cannot run well, but because it is doing too much at once. Optimization here does not mean raising FPS as an abstraction. It means deciding which parts of the world should keep their detail and which can be simplified without affecting the driving itself. That is the philosophy behind the three settings below.
The First Big Performance Drain: Mirrors
Few things look as innocent as a wing mirror. It sits there, small and discreet, seemingly secondary to the main view. But in iRacing, mirrors are one of those features that consume resources with surprising efficiency. Every mirror forces the engine to redraw the world from a different angle. You are not seeing a recycled portion of the main image. You are paying for a completely new render pass.
When you keep multiple mirrors active, the simulator not only has to build the forward-facing scene but also reproduce what is happening behind the car, with a level of visual generosity that is not always necessary. In the middle of a race, a mirror does not exist so you can admire the shading quality of the car behind you. Its function is far more practical: to tell you whether someone is there and whether you need to defend your position or give space.
That is why one of the most effective adjustments is to deliberately reduce the level of detail on mirrors using the LOD parameters specific to rear-view displays. Aggressively lowering the geometric quality in that secondary view frees load from the main CPU thread without compromising anything that actually matters on track. The car visible in the mirror will still serve its informational purpose, even if it becomes a considerably less detailed version of itself.
When you apply aggressive values to parameters such as LODPctDynoMirrorsMax, LODPctDynoMirrorsMin, LODPctMirrorsMax, and LODPctMirrorsMin, you are making a rational redistribution of resources: you are telling the simulator to treat mirrors as the functional tools they are, not as part of the world that deserves the same level of detail as the main scene.
The Pit Lane: An Expensive Set You Almost Never Need
The pit lane is one of the most visually costly spaces on any circuit. Structures, crew members, tools, tyres, panels, and small details that together form a considerable volume of geometry. From a visual standpoint that makes sense. From a performance standpoint, it is a quiet ambush.
Many users only discover the problem when they notice a localized frame rate drop on the main straight or when approaching the pit entry. The car has not changed, the track has not changed, but performance drops. The simulator is spending resources drawing an environment you are barely paying attention to at that moment.
This is where one of the most effective adjustments comes in: setting the number of pit objects to render to zero. By setting MaxPitObjsToDraw=0 and MaxPitObjsToDrawInMirrors=0, iRacing stops sending the majority of that secondary scenery to the graphics pipeline. The visual effect can sound drastic on paper, but in practice it is entirely functional. The simulator retains the information you need for your own pit reference while eliminating a volume of load that is completely disproportionate to its actual usefulness during a race.
The result tends to be immediately noticeable. The main straight stops being a zone of unstable performance, and the simulator gains consistency exactly where losing it is most frustrating.
AutoNoDynEmptyLOD: The Setting That Discards Without Hesitation
If mirrors are the elegant consumer and the pit lane the quiet spender, AutoNoDynEmptyLOD is the parameter that decides, under pressure, which objects deserve to keep existing and which do not.
Under normal conditions, many graphics engines retain simplified versions of distant or secondary objects to allow smooth transitions when they come back into view. The logic is sound: keeping some visual trace avoids abrupt pop-in. The problem appears when that cumulative effort still represents a significant load during the most demanding moments.
With AutoNoDynEmptyLOD=1, the simulator takes a more aggressive stance. Instead of holding onto residual elements, it discards them entirely when it detects that frame rate needs protecting. Collision debris, minor parts, peripheral objects no longer occupy computational space. What is lost in marginal visual richness is gained in stability and headroom for the engine to focus on what actually defines the driving experience.
What These Settings Reveal About iRacing
Beyond the specific FPS gains each user might see, these settings reveal something important about the nature of the simulator. iRacing does not always reward the user who spends the most, but the one who best understands which parts of the system are consuming resources unproductively. Optimization is not an obsessive habit. In a simulator this demanding, it is part of the process.
This is why so many performance problems are not solved by a faster graphics card. If the bottleneck lies in how workload is organized, adding raw power only delays the problem. Removing unnecessary weight changes the equation for real.
- Remember, you can join iRacing by clicking here.
See you on the track!
This website uses affiliate links which may earn a commission at no additional cost to you.
