iRacing’s automated spotter calls cars on your left, your right, and when you’re clear. But in team endurance events, the sim mutes those calls the moment a teammate enters the spotter position. Most drivers notice this for the first time mid-race. This guide covers how to find the setting, what to change, and a few other settings worth reviewing while you have the file open.
Why iRacing Mutes the Automated Spotter
iRacing’s spotter system works in two separate modes. First, there is the automated in-sim spotter, which runs on AI logic and calls car positions throughout a session. Second, there is live spotting. A human teammate joins as a spectator and calls traffic over team comms.
By default, iRacing treats a live spotter as a replacement for the automated one, not an addition to it. So when a teammate enters the spotting booth, the automated voice goes silent. The setting that controls this is called mute_spotter_if_live. It lives in app.ini and defaults to 1.
The logic behind the default is not unreasonable. If a human teammate is calling traffic, hearing the automated voice on top of it could cause confusion. But many drivers find it more useful to have both active. Live spotters can miss a call during a driver swap. They may drop connection briefly or be slower to react on a fast lap. Keeping both running gives you a backup layer of coverage.
How to Find app.ini and Change the Setting
app.ini is a plain text file that iRacing uses to store hundreds of session settings. You can edit it between sessions to adjust everything from graphics to audio preferences. Here is how to access and edit it:
Open File Explorer and open Documents, then the iRacing folder. Find the file named app.ini and open it in Notepad or any text editor. Use Ctrl+F to search for mute_spotter_if_live, change the value from 1 to 0, then save and close the file.
The next time you launch iRacing, the spotter stays active even with a live teammate in the spotter position.
Two things to keep in mind when editing app.ini: always close iRacing before making changes. If the sim is running when you save the file, it will overwrite your edits when the session ends. Also, iRacing sometimes resets app.ini values after a major build update. Keep a note of your custom settings so you can restore them quickly.
What Changes When You Set It to Zero
With mute_spotter_if_live set to 0, the automated spotter runs throughout the race regardless of whether a live teammate is active. You will hear both the automated position calls and your teammate’s voice over comms at the same time.
Whether that works for your team depends on how you communicate. Some drivers find the redundancy useful, especially in heavy traffic or when a spotter is slow to respond. Others find it distracting to hear “clear” twice in quick succession. If you prefer the original behavior, setting the value back to 1 restores it immediately.
One approach that works well for longer stints: leave mute_spotter_if_live at 0, but ask your live spotter to stay quiet in light traffic. Reserve their calls for close wheel-to-wheel moments, pit entry, and anything ahead that the automated system cannot anticipate. The automated spotter handles the routine calls, and your human teammate handles the moments that require actual judgment.
Other Spotter Settings to Check in app.ini
Since you have app.ini open, a few other spotter-related entries are worth reviewing.
spotter_vol controls the volume of the automated spotter on a scale of 0 to 100. If the in-sim calls feel too quiet against your team comms, raise this value. The default is usually moderate, but preferences vary depending on headset and audio setup.
pitroadspeed_alert_vol controls the volume of pit road speed warnings. This is not a spotter setting, but it is worth checking while you are already in the file. Pit lane speed violations are one of the most common avoidable penalties in team races.
iRacing also supports custom spotter packs. These are third-party audio replacements for the default spotter voice. Spotter packs install into the spcc folder inside Documents, then iRacing, then sounds. You select the active pack from iRacing’s audio options in the main menu. Hundreds of community-made packs exist with different voices and styles. The iRacing member forums are a useful place to find community recommendations. The mute_spotter_if_live change you made applies to all packs equally.
How Live Spotting Works in iRacing
If you have never set up live spotting in a team session before, here is how it works.
In a team event, a designated spotter joins the session as a spectator. They enter Spotter Mode by pressing F3 from the Spectator HUD. Once they activate Spotter Mode, iRacing registers them as the live spotter for the current driver. From that point, the default behavior mutes the automated spotter. The app.ini change you made prevents that mute.
The live spotter sees a broadcast-style view of the race and calls traffic over team comms. They have a full view of the standings, pit window, and incidents on track. A good live spotter does more than call left and right. They track fuel windows, monitor rival pit stop timing, and flag anything ahead before you reach it.
Teams often learn this the hard way in their first endurance race: the spotter slot covers only one driver at a time. When you swap drivers, your spotter must re-enter Spotter Mode for the incoming driver. Add this step to your driver swap checklist so you do not run a stint with no spotter coverage.
It also helps to assign a dedicated spotter before the race rather than rotating the role between stints. A spotter who stays in the booth builds situational awareness across the full event. They know the gaps, the traffic patterns, and which rivals are on aggressive strategies. That context does not carry over when you swap the role mid-race.
The mute_spotter_if_live fix is one of those small setup steps that matters most when the race gets complicated. One line in app.ini removes a variable you should not have to think about mid-stint.
