Running iRacing in VR puts your GPU and CPU under serious load. Add Crew Chief, SimHub, and overlay apps running on the same machine and you will start to notice frame drops, stutters, and audio glitches at exactly the wrong moment. The solution is to offload those telemetry and overlay apps to a second PC, and a free open-source tool called iracing-teleport makes it possible.
Also See
➡️ Best CPU and GPU for iRacing on Triple Monitors
🎮 iracing-teleport on GitHub
This guide covers why Crew Chief hurts VR performance, how to set up the two-PC telemetry offload, what you can and cannot offload, and what you need to get started.
Why Crew Chief Hurts VR Frame Rates
Crew Chief is a voice-based race engineer app that reads iRacing telemetry in real time and delivers audio callouts: early wreck warnings, tire status, fuel calculations, and gap readings to cars around you. It is genuinely useful. It is also running a constant telemetry polling loop and playing back audio through your sound system, which means it is competing for CPU cycles with iRacing itself.
In flat-screen iRacing, the CPU overhead from Crew Chief is manageable for most machines. In VR, the margin is much smaller. iRacing in VR requires high, consistent frame rates to avoid motion sickness, and any process that creates CPU spikes or audio latency will show up immediately as dropped frames or judder. The same applies to SimHub, which handles dashboard overlays and tactile feedback, and to any other app that polls the iRacing data broadcast.
The clean fix is to move all of those apps off your iRacing PC entirely.
How iracing-teleport Works
The iracing-teleport tool by blaxklabel on GitHub (iracing-teleport and its companion sim-teleport) works by forwarding the iRacing shared memory data broadcast over your local network. You run one executable on your iRacing PC and another on your second PC, and the second PC sees the telemetry stream as if it were sitting directly inside iRacing.
The setup is two steps. On the iRacing PC, run source.exe. On the second PC, run target.exe. Once both are running and connected on the same network, apps like Crew Chief and SimHub on the second PC will receive the full iRacing telemetry feed and function normally. You do not need to configure anything inside Crew Chief or SimHub.
Setting Up the Connection
Both PCs must be on the same local network, either wired or on the same Wi-Fi network. A wired connection on both machines is recommended to keep latency low, though Wi-Fi works in most cases. The telemetry data stream is small enough that network speed is not a concern.
Download both executables from the GitHub repository. Place source.exe on your iRacing PC and target.exe on the second PC. Launch source.exe first, then target.exe. The target executable will display the IP address it is listening on. If the connection does not establish automatically, check that your firewall is not blocking the port iracing-teleport uses.
Once connected, launch Crew Chief on the second PC. It will detect the iRacing data stream and start processing telemetry normally. If Crew Chief does not connect on the first attempt, close it, confirm both executables are running, and relaunch. The connection is stable once established and does not require any changes to your Crew Chief configuration.
What You Can Offload
Any app that reads iRacing telemetry through the shared memory interface can be moved to the second PC using this method. That includes Crew Chief, SimHub, and most overlay apps. If you use multiple overlays for timing, standings, or gap data, those can move to the second PC as well. If an app reads iRacing data and does not need to be physically connected to hardware plugged into your iRacing PC, it can go on the second machine.
Tactile feedback hardware like bass shakers or SimHub haptics is an exception. If your tactile devices are physically connected to your main sim rig, SimHub still needs to run on that machine to drive them. You can run SimHub on the second PC for dashboard overlays and audio alerts while keeping a lightweight SimHub instance on the iRacing PC for tactile output only.
Crew Chief vs. the Default iRacing Spotter
iRacing includes a built-in spotter that handles basic position calls and proximity alerts. Crew Chief extends this significantly. It delivers early wreck warnings before incidents happen rather than after, calls drivers by name when they are alongside you, reminds you about cold tires on out laps, tracks your fuel consumption and projects pit stop timing, and gives you gap readings to the car ahead and behind on request. For most serious iRacers, those additions are worth keeping even if they require a second PC to run cleanly in VR.
Troubleshooting Common Issues
If Crew Chief on the second PC is not picking up telemetry after launching both executables, the most common cause is a Windows Firewall block. Open Windows Defender Firewall on the iRacing PC and add an inbound rule allowing the port iracing-teleport uses. The GitHub repository lists the default port in the readme. If you are on Wi-Fi and experiencing delays or missed callouts, switch to a wired connection on at least the iRacing PC. On some machines, antivirus software will flag source.exe or target.exe as unsigned. Adding both to the exclusion list resolves this without disabling protection.
What You Need
You need two PCs connected on the same local network. The second PC does not need to be powerful. Any machine capable of running Windows and playing back audio can handle Crew Chief and SimHub. Many sim racers use an old laptop or a budget mini PC for this purpose. The iRacing PC only needs to run source.exe in the background, which has negligible CPU and memory overhead.
The second PC does not need a dedicated GPU or gaming hardware. A basic office PC or even an older laptop with a working audio output is enough. If you are setting up SimHub on the second machine for dashboard display, a small screen or spare monitor helps, but it is not required for Crew Chief voice alerts.
Once the setup is running, your iRacing VR session has one fewer source of CPU competition, and your Crew Chief calls, SimHub alerts, and overlay data continue to work exactly as before.
