iRacingAutoPit is a free Windows app that extracts real-time telemetry data from iRacing to automatically calculate and set pit stop fuel. It calculates pit stop strategy options, number of stops, pit stop window, average fuel usage and average lap time. It allows you to simulate full race distances in offline testing and logs all lap data. It provides a dashboard for desktop monitors and in-game messages for VR headsets. It has been designed as a portable app with no dependencies and minimal impact on system resources.
- Free and portable app with no installation or software dependencies.
- Simple setup so you can be up and running with a few clicks.
- In-car and on screen info for full compatibility with VR.
- Automatically calculates and sets fuel required for every pit stop in a race.
- Simulate a full race with pit stops in an offline test session.
- Displays pre-race fuel strategy options.
- Saves fuel and lap data from every session to improve accuracy of future calculations.
- Desktop dashboard showing all lap, fuel and pit stop information.
- Message info includes laps until pit stop, laps til pit stop window opens, fuel saving info and more.
- Assign a controller button to toggle automatic fueling at pit stop.
- Assign a controller button to toggle tire change at pit stop.
- Assign a controller button to get the latest fuel and pit stop information at any time.
- Log every lap showing session info, lap time, fuel usage per lap etc.
- Alert when fuel saving is possible to reach the end of the race.
- Supports fuel in litres, gallons, kilograms, pounds and imperial gallons.
- Designed to use minimal system resources.
Why another Fuel app?
After playing around with iRacing telemetry data for a while one thing lead to another and in the end I wanted to create a fuel app that was simple, portable, VR friendly, quick to setup, with no app dependencies and that used minimal system resources.
32-bit and 64-bit versions are supported.
Microsoft .NET 4.0 if on Windows 7.
How to use iRacingAutoPit
Simply extract the downloaded iRacingAutoPit zip file to a folder and then run the iRacingAutoPit.exe file. There is no installation required. It is completely portable and all files are in a single root folder. It can be run from any folder provided you have read/write permissions to that folder. It requires .net 4.0 to run if running on Windows 7.
2. Run iRacing and iRacingAutoPit
iRacingAutoPit can be started at any time. Just be sure to configure any settings listed below such as race type and distance before you get in the car if it’s a test session.
3. Set Race type and distance
This will be set automatically if a race session is detected. If the race is limited by both time and laps the app will try to predict which will occur first based on session lap times. You will need to set this manually if you are in a test session and you want to simulate a certain race type and distance.
4. Set Fuel tank maximum (optional)
This is only required in a non race session if you do not want to use the cars actual fuel tank maximum. For example if you want to simulate a race distance in a test session for a hosted race where you know the cars maximum fuel percentage will be set to 50%. In this case, select the checkbox adjacent to fuel tank maximum and then set it to 50%.
5. Start Race or stint.
That’s all you need to get started. You can now drive out of pit lane or start your race and iRacingAutoPit will start displaying all the data on the dashboard and send you status messages via text chat. Full details on all the apps options can be found below.
For a test session you must set the race distance type to laps or minutes and then set the number of minutes or laps. This will be set automatically for any hosted event that contains a race session. If the race is limited by both time and laps the app will calculate will most likely occur first based on session lap times.
Automatically fuel car (Auto-Fuel)
Turn this option on to automatically set the fuel add amount every lap based on the calculated required stops for the race. If turned off, the fuel add amount will still be calculated and shown in messages each lap but will not be set and you will need to set it manually using the iRacing black box controls.
Note that it will take 2 laps before fuel calculations can be determined. If you have completed 3 or more clean laps previously at the track, fuel usage data is saved and remembered for the initial calculations until enough new and current stint data is available. If you have to pit early before your pit window is open and this option is on, the fuel add amount will be set but the fuel tank will be too full to add the required amount. In this case it would just top up the tank to its maximum. You could toggle it off before pitting to not add fuel resulting in the pit stop strategy remaining the same. Alternatively, you could leave it on, let it fill the tank and the app will calculate a new strategy based on the new fuel level and remaining laps etc.
VR headset mode
Turn on this option if your are using a VR headset and will not be looking at the main dashboard whilst driving. This option will cause the dashboard to only be updated once every lap instead of once every couple seconds. This helps further minimise CPU usage for VR only drivers.
Turn this option on to allow you to optionally bind buttons on your controller to toggle fuel car at pitstop , change tires and repeat messages while driving. Turn this option off to disable all controller bindings. With controller bindings off you will need to turn on the fuel car at pitstop option if you want your fuel add amount automatically set each lap without using a controller button. If you have no controller bindings and fuel car at pitstop is set to off you will only be shown messages each lap stating the required pit stops and fuel add amount that you will then need to manually set yourself while driving using the traditional iRacing black box controls.
The numeric value adjacent to this option sets the number of times per second that your controller is polled for input. Once per second should be enough but if you want it to be a little more responsive you can increase this to 2. A little more CPU is wasted polling twice instead once per second.
Simply select you controller from the list and then complete the button bindings listed below. Unfortunately you cannot use button bindings across multiple controllers. All button bindings can only be assigned to one controller. Once you have completed your button bindings click the save button. If you plug in our controller after starting the app you will need to click the refresh button for it to appear in the list of controllers.
Select button – Toggle automatically fuel car
Click in the textbox and press the joystick button to set.
Click the save button when all button bindings are set. When pressed in car during a session it will toggle the “Automatically fuel car” option.
Select button – Toggle change all tires
Click in textbox and then press joystick button to set.
Click the save button when all button bindings are set. When pressed in car during a session it will toggle change all tires.
Select button – Show last message again
Click in textbox and then press joystick button to set.
Click the save button when all button bindings are set. When pressed in car during a session it will repeat the message from the lap just completed. This can be useful if you are busy racing another car and missed the message.
If pressed while out of the car and in the main session screen this will display the pitstop strategy option for the race if you have 3 or more laps of data for the track and car.
The logs panel accessible from the top toolbar shows all the logs for all the sessions and races you have run with iRacingAutoPit. For each race or stint it will log the session info , session stats , lap numbers, lap times, fuel usage, required fuel and more. It will show fuel estimates for preset lap or minute intervals. These estimates are useful if you’ve just jumped into a session for a quick race and need a rough guide as to how much starting fuel you’ll need. It will also suggest a pit stop strategy for the current race distance type you have set if you have completed at least 3 clean laps in this session or in the past. Each time you get out of the car after running a few laps you will find a full log of your laps and session here. You can also search, delete and refresh the log.
General tips and info
If you find the chat messages a little too small in VR you can increase the text size via the Graphics option in iRacing under UI Zoom. For a 1440 x 1600 HMD I would recommend a setting of 150%.
If you are driving cars that measure fuel in pounds (lbs) or imperial gallons (imp. gals) note that iRacing only allows adding of fuel in litres (L), gallons (g) or kilograms (k). iRacingAutopit handles this by converting the fuel add amount for imperial gallons to gallons and pounds to kilograms. This means for these units only you will see the fuel add amount displayed with both equivalent units as shown below.
Fuel add 10 k = 22 lbs
Fuel add 10 g = 8.3 ip
This will only be the case when driving cars like the Lotus 49/79 or when you have your units in iRacing set to English and you are driving cars that measure their fuel in weight like the HPDARX. Note that iRacingAutopit will only add the unit of measure suffix when showing the Fuel Add amount in the message shown while driving. At all other times it will not show any suffix and fuel will be displayed in the default unit of measure for the car and your iRacing setting. ie the same unit of measure shown in the iRacing fuel black box window.
The logs show Off track count for each lap. They are not always detected so it may show less than really occurred.
If you come across bugs, have suggestions or would like a feature please feel free to use the anonymous feedback form located here. Most of the testing and development was done with VR road racing and while it should work fine with other formats there could be some issues that Ive not come across. Note that this app was created in my spare time so while I’ll try to fix bugs quickly, common feature requests could take some time to get implemented if at all.