Introduction to iRaceControl
1.1.SETTING UP
1.1.1.WINDOWS 11
IMPORTANT: With Windows 11, if iRaceControl is run without Administrator rights, it cannot create files if it is installed in/under the "Program Files" folder. Consider unpacking the iRaceControl ZIP into a dedicated folder elsewhere on your drive.
1.1.2.RUNNING AS ADMIN
If you are running iRacing as admin, you will need to run iRaceControl as admin too. However, it is recommended to run both iRacing and iRaceControl normally without elevated rights.
1.1.3.GETTING ALL THE DATA
To get all the data from all the cars you will need to set iRacing to request every car's data from the server. To ensure this, in iRacing, go to OPTIONS > GRAPHIC and set "Max Cars" to 63.
NOTE: Even if you have set Max Cars to 63, if your available bandwith is low, the iRacing server might send fewer cars' data.
THE USER INTERFACE
[F11] will toggle Fullscreen mode (which is different to a maximised window).
2.1.CONNECTION SECTION
These two toggles control the connection between iRaceControl and iRacing and - optionally - any other iRaceControl users. There are also indicator lights here which show the activation of iRaceControl's communication modules.
2.1.1.RUN/STOP
If you want to load saved data, keeping this at STOP will prevent new data from "polluting" the saved data. You can load, save or clear race data from memory by using the "Data" menu. Moving the toggle to RUN will cause iRaceControl to attempt to fetch new live telemetry from iRacing.
2.1.2.MAIN/OFF/SUPP
This toggle has 3 positions, with OFF being in the middle. If you have an active license you can select to either be the MAIN controller (Server) or a SUPPorting controller (Client). See more under Networking.
2.2.CLOCKS AND COUNTERS
Across the top is a selection of clocks and one counter to help you orient yourself timewise in iRacing.
2.2.1.REAL TIME
Shows you the date and time of your local computer.
2.2.2.SIM TIME
Shows you the start date of the race, and the current time in iRacing.
NOTE: The date does not "tick over" into a new date if your event crosses midnight. It will always stay on the date the race started.
2.2.3.TOT INC
The total number of incident points accrued in the current session across all cars. A collision is double-counted, as both cars receive 4 incidents each.
2.2.4.SESSION REM TIME
The time remaining in the current session.
Under the remaining time is the session timer. This shows you how long a session has been going - unless you are in the race, when it shows the current race time.
2.2.5.LAPS REM
The number of laps remaining in the race, if the race is lap limited.
Under the Laps Remaining counter is the lap counter. This shows how many laps the car with the most laps has completed.
2.3.ADVANCE AND SESSION INFO
2.3.1."ADVANCE" BUTTON
Pressing this button will request an advance to the next session in iRacing.
2.3.2.SESSION TYPE AND STATUS
These two boxes will each scroll a list to show you what session iRacing is currently in, and the status of that session.
SESSION TYPES:
* UNKNOWN
* PRACTICE
* OPEN QUALIFY
* LONE QUALIFY
* WARMUP
* RACE
* TESTING
SESSION STATUS:
* INVALID
* GET IN CAR
* WARMUP
* PARADE LAPS
* RACING
* CHECKERED
* COOLDOWN
2.5.FLAG BOX AND START LIGHTS
2.5.1.FLAG BOX
A light-display that shows any flag currently shown to your car.
2.5.2.START LIGHTS
Shows the current state of the start lights in iRacing.
2.6.SEQUENCER, IGNORE AND RESTART FORMAT
2.6.1.SEQUENCER BOX
This box shows information about random Full Course Yellows (FCYs) or other events happening because they have been programmed with the Sequencer settings. The window only shows the actions defined for the current session. A race session is further divided into GET IN CAR, PACE LAPS and RACE.
When the time window for an action is not yet here, its status will show WAIT. When the time window is over, the status will show DONE. What is displayed as status during the time window is dependent on the setting of the Sequencer DETAIL toggle.
2.6.2."IGNORE" BUTTON
If the SEQUENCER DETAIL toggle is set to HIGH, and "Sequencer ignore yellow time" is also set to non-zero in the Sequencer settings, this button will start to flash when a yellow is called by the Sequencer logic.
It will flash for as many seconds as you have set for the "Sequencer ignore yellow time". If not pressed, a full course yellow will be called. If the button is pressed while flashing, the yellow will be ignored and not thrown.
2.6.3.RESTART PATTERN INDICATOR
This indicator will be lit to display the currently-selected pattern for restarts after a Full Course Yellow. Either single-file or double-file.
2.7.iRACING STATUS
These values are from the C/S/P meters within iRacing.
2.7.1.CPU
This indicator will light up in red if iRacing is using more than 98% of available time for each tick. If this happens too often, or if this indictator is always on, the SDK might provide you with bad data.
2.7.2.SKEW
Skew is how much out-of-sync you are with the iRacing server. This indicator will light up in red if you drift more than 0.5 seconds away from the server.
2.7.3.FAULTS
This indicator will light up in red if iRacing experiences more than 50 memory page faults per second. A page fault happens when Windows needs to move data from a hard drive into memory, or vice versa. It isn't an issue if this happens occasionally, but frequent or constant triggering of this status might indicate a performance issue.
2.8.TOGGLE SWITCHES
This second group of switches, to the right-hand side of the screen, are for controlling how some iRaceControl features look or work.
2.8.1.SEQUENCER
ON/OFF:
Choose whether the Sequencer feature is enabled and running or not.
DETAIL HIGH/LOW:
Choose how much detail about the random yellows will be displayed in
the box to the left. HIGH will, when the time window opens, either
display "NORY" if that random yellow is not being thrown, or a
countdown to when the yellow is to be thrown. LOW will only display
"ACTV" when in the time window for the random yellow, so that even
the person with iRaceControl cannot know if, and when, the yellow
will be thrown.
2.8.2.AUTO STWD
ON/OFF:
Select whether the AutoSteward feature is enabled and running or not.
2.8.3.TIMING
NAME TEAM/DRVR:
Selects between showing the TEAM name or current DRiVeR name
for display in the timing view and race log. This also selects
what is displayed at the top of the SELECTED CAR box, and the
non-selected is displayed on the second line.
GAP/INT:
Whether to display the GAP from each car to the leader, or
the INTerval to the next car in front.
GAP LAPS/TIME:
For cars which have been lapped, whether to display LAPS behind leader
or TIME behind leader.
SPD MPH/OFF/KPH:
This toggle has 3 positions, with OFF being in the middle.
Whether to add an extra timing column displaying each car's current
calculated speed in either MPH or KPH.
BEST CLASS/OVERALL:
Select whether, in a multi-class race, the best laptime in each CLASS
should be highlighted in purple or just the best time OVERALL.
2.9.TRACK MAP
Many circuits available in iRacing have had their layout translated for this map feature. If no map exists or it cannot be loaded, a circle will be used instead. A toggle in the top left corner allows you to switch between map mode and circle mode. In circle mode, the pit lane is always drawn inside the track circle. You may request new track conversions via the iRaceControl Discord.
The track map is animated to show where the cars are and some incident information.
A portion of the track will have a yellow highlight if a car is reported to be off-track by iRacing or if a car's speed is below 5 m/s. The yellow zone is between 5% lap distance behind and 1% lap distance ahead of the cars position.
You will also see a red marking on the track where any incidents have occurred. These markings will fade away over a period of 10 minutes.
The selected car in iRaceControl will be marked on the map by a red ring around the car roundel. There is also a small toggle in the top right corner where you can set whether the leader will be marked with a green ring around its roundel. If you have blue flag detection enabled, any car with a blue flag will get a blue circle around its car roundel.
The number in the roundel is either black or white depending on the fill color. Fill colors depend upon the system chosen on the General settings page.
2.10.TIMING VIEW
Lists all the cars in the session and their latest timing data. Which columns to display in the timing view can be configured via the Timing option on the Settings menu.
During a race the cars are ordered by the travelled distance, while the position number is the one reported by iRacing. iRacing only updates the position numeral when a car crosses the start/finish-line, so it may seem that drivers are out of order, but that only means some overtaking has taken place on this lap.
Click just once on a line in the timing to select a car. That car's info will then appear in the SELECTED CAR box, and its incidents in the CAR LOG box.
Double-click on a line in the timing to select that car AND change the iRacing camera to view it. iRacing will also go from delayed replay to live feed if you have set the appropriate option in General settings.
Extra detail about some of the columns:
INC: The INC column shows each car's current number of incidents.
If this number is red, the cars have unresolved incidents.
If the number is white, all recorded incidents have been resolved.
(Any incident of 0x or more recorded against a car can have either a note or
a penalty judgement recorded against it. Until this is done the incident
is shown in red writing and referred to as UNRESOLVED.)
The INC number might be "0" and red. This can happen either when there are
unresolved incidents in a previous session but no incidents have been recorded
in the current one, or the car has received a 0x within iRaceControl either
manually or from the AutoSteward (any 0x given by iRacing cannot be recognized
by iRaceControl).
FLAG BLOCKS: In the left margin there will be a yellow block if the car is reported
as being off track by iRacing, or its speed is below 5 m/s. Before the start of
a race, when cars are lining up on the grid or for a rolling start, all cars
will get this yellow block. This will then tell you if any cars are starting
from the pits as they will not get this rectangle.
If blue flag detection is enabled, a car that has a blue flag will display a
blue block in the left margin.
When iRaceControl detects that a car has finished the race, a small checkered flag
will appear in the left margin.
CLASS POSITION: If the race contains more than one class of cars, this column
will show the current class position with a background color indicating which
class the car is in.
LAST: When a car completes a lap, its laptime will be calculated by iRaceControl
and show up colored white. When (if) we get an official laptime from iRacing,
the color changes to yellow (or purple or green if the laptime is overall best
or a personal best).
NIW: Stands for "Not In World", which happens when a car disappears. This column
counts how many times a car has gone to NIW. This is useful for tow-detection,
and to identify any blinkers.
Going to NIW from your pit-box when you change drivers is not counted.
LAPS LED: This counts the number of laps a car has led. It increments when a car
is the first to start a new lap. NOTE: The opening lap is not counted.
2.11.RACE CONTROL COMMAND BUTTONS
Pace car -
DEPLOY: Throws a Full Course Yellow (FCY) and deploys the pace car.
END: Tells the pace car to come in at the earliest opportunity.
Pace car must have passed the start/finish-line once already.
ADD LAP: Adds one lap of pacing.
CUT LAP: Removes one lap of pacing.
SNGL FILE: Sets restart to single file.
DBLE FILE: Sets restart to double file.
Pit entry - iRacing might or might not comply with these commands, depending on the situation.
OPEN: Attempt to convince iRacing to open the pit lane entry.
CLOSE: Attempt to convince iRacing to close the pit lane entry.
Race start - When in RACE and GET IN CAR...
START: Go immediately to starting the race.
HOLD: Resets the countdown to 10 minutes.
Penalties -
CLR ALL: Clears all outstanding penalties from all cars.
AUTO CLR: When this is enabled (lit red), a car receiving either a
furled black flag or a black flag from iRacing will have it
automatically cleared.
EOL / Wave around -
CLASS SEP: Re-orders a pacing field by class, so that all the cars from
the fastest class is in front of the second class, and so on.
WAVE LAPD: When a field is pacing, this button will issue a wave-by command
to all lapped cars.
2.12.RACE LOG
The race log shows you a list of all incidents and events that have happened. Clicking once on an event will select that car AND select that event in the car log.
Double-clicking on an event will select the car, select the event, AND change the iRacing camera to view the car. iRacing will also go from delayed replay to live feed if you have set the appropriate option in General settings.
If you have scrolled the race log to the very bottom, it will autoscroll down when new events are added to the log. If you are not positioned at the bottom, it will stay where it is when new entries are added.
2.12.1.LOG FILTERS AND AUTOJUMP
At the top of the race log are the log filter buttons. Here you can set which log entries you wish to display. Note that all events are always logged but the filters allow you to hide the ones you are not interested in. Changing the filters also instantly affects the CAR LOG in the same way.
Filters which are lit (often coloured) will allow those events to be visible in the log. Click a filter button once to switch it between being on or off.
If you right-click a filter button, a small line becomes visible beneath it. This will make the iRacing camera auto-jump to view whichever car has just caused that log entry. At busy times this may get confusing.
2.12.2.RACE CONTROL MESSAGE
You can type a message here which will be instantly sent to all drivers and team members as a Race Control text chat message.
Text longer than 59 characters will be split into separate messages all delivered at once. As you approach that limit the background color of the box will change to orange, then red when you have exceeded it.
2.13.SELECTED CAR/WEATHER BOX
To select between the SELECTED CAR and WEATHER boxes, simply click on the label for the box you want to see. The label will illuminate to indicate wich box is currently active.
The units can be selected under SETTINGS > GENERAL.
For free users, the weather box will simply print out the current values about the weather.
Pro users will also get the following:
Logging of air and track temperatures, displayed on a graph.
Logging of precipitation values, displayed on a graph.
Average wind speed over the last 2 minutes.
Maximum wind speed the last 10 minutes. (Gust)
The wind speed has the following labels for pro users:
MVEL: Momentary Velocity (The wind speed right now)
VEL: Average Velocity (Last 2 minutes)
GUST: Maximum wind speed (Last 10 minutes)
The timespan for the graphs, can be adjusted from 15 minutes up to 24 hours.
If a session has been declared wet by the iRacing marshalls, a white label with "WET" will appear next to the precipitation graph.
The current wetness of the track is also diplayed to the right of the precipitation graph.
2.14.CAR LOG
Same as the race log, but only shows events pertaining to the selected car.
Double-clicking on an event will jump the iRacing replay to the selected car, 5 seconds before the event.
For Pro users, clicking on a red text incident event will let you handle or resolve it by using the Action Buttons below the log, which will illuminate when you select a valid event.
2.15.CAR-RELATED ACTION BUTTONS
Many of these buttons do not act instantly and will instead prompt you first to enter an optional text message to go with it (or cancel the command completely). The message will either be public, private, or not sent at all depending on your choice for that message type in the CACS (Chat And Command System) settings.
Commands which act instantly with no cancellation option are labelled in the descriptions below with "[INSTANT]".
2.15.1.SELECTED CAR
WAVE ARND Lets this car pass the pace car and go around.
EOL Tells this car to drop back to the End Of Line.
NOTIFY Send an iRacing text chat message to this car.
CLEAR PENS [INSTANT] Clears all outstanding iRacing penalties for this car.
(does not clear time penalties given in iRaceControl.)
0x [INSTANT] Give this car a 0x incident in iRaceControl.
Useful for issuing a car a penalty without an incident.
No message is sent within iRacing.
DSQ Disqualify this car. You can enter a reason for the DSQ.
2.15.2.CAR LOG
REPLAY [INSTANT] Starts a replay of the selected event 5 seconds before
it was logged. You can also start a replay by double-clicking
on the event in the log.
NOTED [INSTANT] Sends a message saying this incident is NOTED.
This does not resolve the incident (text stays red), and you
may change the outcome of the incident using another of these
buttons later.
INV [INSTANT] Sends a message saying this incident is UNDER INVESTIGATION.
This does not resolve the incident (text stays red), and you
may change the outcome of the incident using another of these
buttons later.
NO ACTION [INSTANT] Marks an incident with message of NO ACTION.
Resolves the incident (text turns white). Cannot be changed later.
INCIDENT [INSTANT] Marks an incident with message of RACE INCIDENT.
Resolves the incident (text turns white). Cannot be changed later.
NOTICE Marks an incident as resolved (text turns white and is final), but
allows you to add a note to it first.
DRIVE THR Gives the car a drive-through penalty. Can have a reason attached.
Resolves the incident (text turns white). Cannot be changed later.
STOP/GO Gives a simple stop-and-go penalty. Can have a reason attached.
Resolves the incident (text turns white). Cannot be changed later.
STOP/GO Xs Gives a stop-and-HOLD penalty where you can specify the number of
seconds to hold in the pit box. Can have a reason attached.
Resolves the incident (text turns white). Cannot be changed later.
TIME PEN Gives the car a time penalty. This penalty is only visible within
iRaceControl results, and alters nothing in iRacing.
Resolves the incident (text turns white). Cannot be changed later.
To void a served time penalty, issue the car a new time penalty with
negative time.
DSQ Same as DSQ for selected car, but you mark this incident as the reason.
Resolves the incident (text turns white). Cannot be changed later.
2.16.REPLAY CONTROLS AND CAMERA SELECT
A selection of buttons which directly control the iRacing replay.
Two pairs require further explanation -
NEXT/PREV: These move the camera to an adjacent car on track, as the original
iRacing controls do.
P-/P : These move the camera to the next car in class, regardless of where
the vehicles are in traffic.
2.17.PROFUNC
Extra functions for users with an active license. You can also create custom Race Control message buttons here.
Built-in buttons are -
NO-AC ALL: Tags all unresolved incidents with NO ACTION.
MANUAL STAGE: [description needed]
RED FLAG: Posts Race Control (and Race Log) message of a red flag.
GREEN FLAG: Posts Race Control (and Race Log) message of a green flag.
SETTINGS PAGES
3.1.GENERAL
Changes in this dialog do not take effect until you press OK. CANCEL ignores any changes.
3.1.1."GENERAL OPTIONS"
Autosave data:
Activate this to have iRaceControl autosave its data every 5 minutes.
The autosaves are stored in the iRaceControl folder, and are named
autosave1.bin, [...], autosave5.bin.
Each time iRaceControl autosaves it overwrites the oldest of the 5 files.
If the files don't exist, they will be created.
Throw yellow if yellow is already thrown:
Sometimes iRaceControl wants to issue a new yellow when the field is already
under caution. This settings determines if that yellow should be thrown or not.
Autoconnect on startup:
Whether to automatically set the RUN/STOP toggle to RUN when starting iRaceControl.
Class Based wave by:
[description to be confirmed]
Go live on timing double click:
If selected, double-clicking on a car in the timing view will also switch
the iRacing camera to view the car live, leaving replay mode if required.
Use custom classes:
If selected, the settings you have entered into the "classes.txt" file
(found in the "Settings" folder where iRaceControl is installed) will be used.
Autojump max class position:
[description to be confirmed]
3.1.2."QUALIFY"
Per cent cutoff line:
[description to be confirmed]
3.1.3."MAP ROUNDEL COLOURS"
The roundel colors can be set to one of three options:
Car Colors: Takes colors from the iRacing Paint Shop.
May not be helpful if you run Trading Paints.
Class Colors: Colors the cars according to their iRacing class color.
License Colors: Colors the cars according to the current driver's license color.
3.1.4."SECTOR TIME DECIMALS"
Sets the number of decimals to display for the sector times in the timing view. From 1 to 4.
3.1.5."WEATHER UNITS"
The measurement units used for Temperature, Pressure, Density and Wind Speed in the Weather box can be customised here.
3.1.6."INCIDENT LOGGING"
These options pertain to features only available to Pro users.
Group incidents:
Activate this to use incident groups for when multiple cars get x'es around the
same time on the same place on track. Instead of an incident report for each
incident, there will be one for the group combined.
When selecting the group in the race log you can issue a message about the
incident being NOTED or INVestigated. The message will then list all cars
involved in the group.
To resolve the incident, deal with each car separately.
Log blue flags:
iRacing does not give out what cars are being shown a blue flag, but iRaceControl
can calculate its own blue flags.
Using the default settings in the following controls will approximate the
blue flags given in iRacing, but can not be assumed to be identical.
Fine tune the settings to your own needs.
Seconds behind:
How close behind a lapping car must be to trigger a blue flag.
Delay:
How long must a blue flag be triggered for iRaceControl to start logging it.
Use this setting to avoid many short-duration blue flags if lapping cars
are hovering around the "Seconds behind" trigger.
Minimum time:
The minimum duration of a blue flag once the delay-period has passed.
This is the delay-settings opposite. It will keep a blue flag active for
this many seconds, to avoid multiple blue flag logs in succession.
Actions for ignoring blue flags too long can be set in AutoSteward settings.
3.1.7."TIME PENALTIES FOR FURLED/BLACK FINISH"
Choose how many seconds are automatically added to a car's finish time (within iRaceControl but not iRacing) if they finish the race with a Black Flag or a Furled Black Flag which has not been served.
ENABLE THE PENALTIES:
If not selected, iRaceControl will not add the seconds that you set below.
3.2.TIMING
Changes in this dialog do not take effect until you press OK. CANCEL ignores any changes.
This page lets you choose which columns are visible in your Timing View, plus their sequence left-to-right and some other settings.
The box on the RIGHT lists the columns you have selected to include on your timing. The box on the LEFT offers other columns which you could add.
Click a column in one of the boxes, then use the arrow buttons to move it either across to the other side (enable or disable it) or up and down in the sequence (higher is first).
HEADLINE:
The short identifying title to display at the top of the column.
HEADLINE OFFSET:
How many spaces to include before the column headline. Can help readability.
COLUMN WIDTH:
Change the horizontal space that the column is allowed to occupy.
3.2.1.AVAILABLE TIMING COLUMNS
Full list of available timing columns and formatting.
COLUMN ALIGN NOTES
Best Laptime RIGHT
Car Class LEFT (Squeeze fit)
Car Flags LEFT
Car Number RIGHT
Car Type LEFT (Squeeze fit)
Car Type Id RIGHT
Class Position RIGHT
Driver Name LEFT (Squeeze fit)
Driver/Team Name LEFT (Squeeze fit)(Togglable)
Fast Repairs Used RIGHT
Flag LEFT (If width is more than 1, more flags will be displayed)
Gap RIGHT (seconds to leader)
Gap/Interval RIGHT (Togglable)(Shows PIT/OUT)
Incident points RIGHT (x's)
Interval RIGHT (seconds to car ahead)
Laps Completed RIGHT
Last Laptime RIGHT
Laps led RIGHT
Laps led in class RIGHT
Laps since pit RIGHT
Not in World RIGHT (NIW)
Overall Position RIGHT
Pit Stops RIGHT
Race Time RIGHT (Only gets set when a car finishes a race)
Raw Tyre Compound RIGHT (Will display -1 if no tyre is fitted)
Sector Times CUSTOM (The width parameter is ignored)
Speed RIGHT (Unit selected by toggle)
Team Name LEFT (Squeeze fit)
Time Penalty RIGHT (Total seconds of time penalties)
Total Time Penalty RIGHT
Tyre Compound Icon CENTRE
Tyre Compound Id RIGHT
Tyre Compound Name LEFT (If name is not found, the compound id is displayed
instead. Same as 24)
X Count 1 RIGHT (Total number of inc points from 1x incidents)
X Count 2 RIGHT (Total number of inc points from 2x incidents)
X Count 4 RIGHT (Total number of inc points from 4x incidents)
3.3.SEQUENCER
You can create a list of actions to be executed during the current session. Actions include, but are not limited to, random Full Course Yellow (FCY) based on time, random FCY based on lap count, Stage Yellows, and Race Control text messages. Open the Sequencer from the Settings menu.
You create an action by first selecting the session it should occur in and then the type of action. You will see different sub-options depending on the action you choose. When you click "Add" your action is added to the active list (the box on the left of the Sequencer window).
Actions in the active list are not editable but a small red button labelled "DEL" allows you to delete any action with a single click. When you close the Sequencer window, any actions in the active list will be remembered, even if you close iRaceControl and re-open it.
You do NOT need to program the Sequencer with events that are in the correct time order.
IMPORTANT: Remember that even if there are actions in the active list, the Sequencer is not active at all unless the SEQUENCER ON/OFF toggle is set to ON.
LOAD - ADD - SAVE:
It is possible to SAVE and LOAD sets of Sequencer instructions. You can also inject a saved Sequencer set into the current list with the nearby ADD button. You could save several small groups of related instructions as modular sets and load a mixture of them to fit your needs for the next race.
SEQUENCER IGNORE YELLOW TIME:
Use this control to set the number of seconds that the "IGNORE" button should flash for before throwing a random FCY.
3.3.1.RANDOM YELLOW - TIME
START:
The earliest time for this random yellow to be thrown.
END:
The latest time for this random yellow to be thrown.
CHANCE:
The probability for this random yellow to be thrown. Enter a value between
0 and 1. For a 50/50 change, enter '0.5'. For a 1 in 8th chance, '0.125'. (Chance
values will be rounded to 2 decimal places when displayed in iRaceControl.)
3.3.2.RANDOM YELLOW - LAP
START:
First lap of the random yellow window.
END:
Last lap of the random yellow window. (Technically not true. See note below).
CHANCE:
The probability for this random yellow to be thrown. Enter a value between
0 and 1. For a 50/50 change, enter '0.5'. For a 1 in 8th chance, '0.125'. (Chance
values will be rounded to 2 decimal places when displayed in iRaceControl.)
When the leader starts his START'th lap, the random yellow is set up. If it is to be thrown (based on the CHANCE parameter) it will be thrown at a random time from the beginning of that lap. The earliest possible time is 0 seconds from the START lap begins. The latest possible time is ((END - START) * leaders last lap time) seconds from the START lap begins.
3.3.3.MESSAGE - LAP
Sends a message when the leader starts a given lap. The destination for the message is set for SEQUENCER MESSAGE in CACS.
(Enabling IRACING PRIVATE has no effect for this message type)
3.3.4.MESSAGE - TIME
Sends a message at a given race time. The destination for the message is set for SEQUENCER MESSAGE in CACS.
(Enabling IRACING PRIVATE has no effect for this message type)
3.3.5.LAP STAGE YELLOW
LAP:
At what lap should the stage yellow be thrown.
POSITION:
Throw the stage yellow when the car in this position starts LAP.
CLOSE PIT:
Checking this box will cause iRaceControl to tell iRacing to close the pit-lane
entrance when the car in "CLOSE PIT POS" crosses the start-finish line 2 laps before
the stage yellow is to be thrown.
CLOSE PIT POS:
[description to be added]
3.3.6.TIME STAGE YELLOW
Throw a Stage Yellow at the specified time.
3.3.7.PIT OPEN/CLOSE - LAP
Sends the pit open/close command to iRacing when the leader starts the set LAP.
3.3.8.PIT OPEN/CLOSE - TIME
Sends the pit open/close command to iRacing at the specified TIME.
3.4.AUTO STEWARD
Here you can set rules that will be active during sessions. Each rule has a selectable trigger and action, and you can limit rules to certain sessions, and for certain classes.
3.4.1.TRIGGERS
Total inc count
Triggers when the total inc count for all the cars in the session is at or above the
set limit.
Inc count:
Trigger point
End Prtct (m):
Optional setting to not trigger the last set minutes of a race. Only works if the
race is time limited.
Every Nth Inc
Triggers first at the set limit, then every Nth total incident count after that.
Inc count:
First trigger point
Then every:
How many incident points to re-trigger
End prtct (m):
Optional setting to not trigger the last set minutes of a race. Only works if the
race is time limited.
Inc in X sec
Triggers when a set amount of incident points has been given in a set number of
seconds.
Inc Count:
Incident points required
Seconds:
Time period to count the incident points in
End prtct (m):
Optional setting to not trigger the last set minutes of a race. Only works if the
race is time limited.
Inc in 1st lap
Triggers for total amount of incident points for all cars incurred in the first lap.
Inc Count:
Incident points required
Car total inc
Triggers when a car has gotten this many incident points.
Car every Nth inc
[description needed]
Car clean driving
Triggers when a car has driven for a set amount of minutes without incurring any
incident points.
Car blue flag
Triggers when a car has been shown a blue flag for the same car for more than the set
number of seconds.
Remember to enable logging of blue flags under Settings > General.
Car 1x count, Car 2x count, Car 4x count
Triggers for when a car has incurred a set number of incident point from specific
incident types.
Two 1x incidents = 2 incident points
Two 4x incidents = 8 incident points.
Nx count:
Number of incident points
Car 1x N-count, Car 2x N-count, Car 4x N-count
Same as for the Nx count, but with a 'then every' setting to repeat the trigger.
Car Fast Repairs Used
Triggers when a car has used the set number of fast repairs.
3.4.2.ACTIONS
Full course Yellow
Sends the command to trigger a full course yellow to iRacing.
Message:
An optional message to accompany the full course yellow.
Set the destination for this message with CACS - FULL COURSE YELLOW points.
Ignore time:
I set above 0, when the yellow is triggered, the IGNORE-button on the main
interface will start to flash yellow, and you can then stop the yellow from being
executed by pressing that button.
The ignore-action can also be assigned to a controller, mouse, or keyboard button
under Settings > Controls.
RC Message
Sends a race control message.
Destinations can be configured with CACS - RACE CONTROL MESSAGE points.
Inc Drop
Drops the cars incident points by the set amount. This only affects the inc number
within iRaceControl, but will give cars a chance to avoid other auto steward's
automatic penalties.
Optional message to accompany the inc drop.
Destination set with CACS - STEWARD INC DROP points.
Warning
Sends a set message.
Destinations set with CACS - STEWARD NOTICE points.
Drive Through
Issues a drive through penalty.
Message destinations set with CACS - STEWARD DRIVE THROUGH points.
Stop/Go
Issues a stop/go penalty.
A common issue with the stop/go penalties, is that i.e. you set the penalty to be 5
seconds, it will show up for the driver as 31 seconds. This is because the driver
hasn't turned off pit servicing, and since you're not allowed to receive service
while serving a stop/go penalty, iRacing converts the 5 seconds into 31 seconds.
(The number of seconds might vary)
To get the hold time down to the correct number, the driver needs to turn off
refueling and tyre changing. Might also be necessary to turn off fast repair and
optional repairs.
Message destinations set with CACS - STEWARD STOP GO points.
DSQ
Disqualifies a car
Message destinations set with CACS - STEWARD DSQ points.
Time Penalty
Gives a car a time penalty of the set number of seconds.
Only applies within iRaceControl.
If a cars erroneously gets a time penalty, they can be cancelled by giving the car a
0x, and applying a time penalty with the corresponding negative number of seconds.
Message destinations set with CACS - TIME PENALTY points.
0X
Gives a car a 0x incident.
Useful for flagging cars for further inquiry when you don't want to give a penalty
automatically.
3.5.CACS
iRaceControl's Chat And Command System (CACS) allows you to select whether and where notification messages are sent when events happen or you take actions.
3.5.1.MESSAGE ROUTING
The routing table for different messages sent from iRaceControl. For each message type you can enable or disable four different destinations. Multiple destinations can be enabled at the same time.
IRACING PUBLIC
Sends the message as a race control message in iRacing. Shows up as purple text in
the iRacing chat.
IRACING PRIVATE
Sends the message as a private message to the car.
SDK GAMING INFO
If SDK-Gaming is enabled, sends the message as a race control info-message.
SDK GAMING PENALTY
If SDK-Gaming is enabled, sends the message as a race control penalty-message.
3.5.2.USE SHORTFORM MESSAGES
Use shorter forms for the NOTED and INV-messages.
Longform:
INCIDENT ON LAP 39 INVOLVING CAR 18 (YOU) IS NOTED
INCIDENT ON LAP 39 INVOLVING CAR 18 (YOU) IS BEING INVESTIGATED
INCIDENT ON LAP 116 INVOLVING CARS 6 (JOB) AND 11 (HEN) IS NOTED
INCIDENT ON LAP 116 INVOLVING CARS 6 (JOB) AND 11 (HEN) IS BEING INVESTIGATED
Shortform:
L39 INCIDENT: CAR #18 NOTED
L39 INCIDENT: CAR #18 INVESTIGATING INCIDENT
L116 INCIDENT: #6, #11 NOTED
L116 INCIDENT: #6, #11 INVESTIGATING
3.5.3.PACE CAR SETTINGS
When issuing pace car commands, you can select who receives the command.
iRacing Pace Car
The commands are sent to iRacing, and it's Pace Car will execute them.
No Pace Car
Pace car commands are not sent anywhere.
Specific Car
You can select a car to receive pace car commands. They will be sent as a private
message to the selected car.
3.5.4.SDK-GAMING INTEGRATION
See SDKGaming.
3.6.CONTROLS
Mapping of inputs to commands. Allows you to map a keyboard button, or a button on your steeing wheel to certain commands in iRaceControl.
EXPORTS
4.1.PDF EXPORT
On the first page of the PDF-report there is a possibility to place up to four images of your choice. They need to be located in the "Resources"-folder and have the filenames logo1, logo2, logo3 or logo4. The imagetype can be either jpg or png.
The images can be selected in the pdf-setting dialog.
Each image will be fitted into a square that this 1/4 of the page width.
In the pdf-settings you can also choose what to include in the report.
4.2.CSV EXPORT
Exports a CSV-file that should be compatible with iRacing race result csv.
SETTING FILES
Files with the various settings for iRaceControl is stored within the Settings subfolder. If the folder don't exists, iRaceControl will create it.
Users can edit the files found inside the Settings subfolder for more advanced configuration of iRaceControl.
NOTE: When iRaceControl closes, it will re-write ALL the files inside the Settings folder. So make your edits while iRaceControl isn't running.
If a settings file fails to load, defaults will be used instead.
LIST OF FILES:
settings.cfg - General settings for iRaceControl
current.seq - The sequencer actions
timing.cfg - Column settings for the Timing View
cameras.cfg - Cameras for the CAM SEL box
classes.txt - User customizable classes
usermsg.txt - Premade race control messages
colors.json - Colours for the program
5.1.CAMERAS.CFG
The cameras.cfg list the cameras for the CAM SEL box. The box gets filles column by column, so the first 3 cameras in the file are the first column in the CAM SEL box.
Each line in the file is the following format:
"iRacing Camera Name": "Text on button in CAM SEL box",
A few special iRacing Camera names exists, these are triggering functions within iRaceControl:
Prev : Selects the car in the previous position (higher number)
Next : Selects the car in the next position (lower number)
TrackAhead : Selects the next car ahead on track
TrackBehind : Selects the next car behind on track
NOTE: Do not have a trailing comma after the last camera.
NETWORKING
6.1.THE IMPORTANT BIT
The only thing being "networked" is the race log. Every controller needs a connection to the iRacing simulator to receive the timing data, review incidents, and issue penalties.
6.2.SETTING UP
One instance of iRaceControl needs to be the MAIN control. This instance will then be the server all others connects to. For other controllers to be able to connect, and you are behind a firewall, you need to forward your selected port to the pc running the MAIN iRaceControl. The port number can be set under SETTINGS > NETWORK.
You can also specity an id/name here. If you are MAIN, your SUPPs will see this id/name in the bottom right corner of iRaceControl if they are connected. As MAIN, you will see the number of connected SUPPs in the bottom right corner. A full list with connected SUPPs, and their id/names is found under Settings > Network, where you also can kick a SUPP.
When you are ready to host, toggle the second CONNECTION toggle up to MAIN. The SERVER indicator will turn blue.
Only one controller should have the sequencer and/or the auto-steward active at any one time. Since all controllers are connected to iRacing, you don't want multiple actions or penalties to be applied.
6.3.CONNECTING
For assisting in controlling a race, multiple instances of iRaceControl can be SUPP (Support).
Connect to your local iRacing first, by toggling CONNECTION to RUN. Then wait a second, or two, to let iRaceControl sync up with iRacing.
Open SETTINGS > NETWORK and type the correct URL/IP and port number of the MAIN controller. Then toggle the second CONNECTION toggle down to SUPP. The SERVER indicator will turn yellow to indicate that it is trying to connect. If a connection is acheived, the SERVER indicator will turn green.
Supporting race controllers can connect to the MAIN at any time, and their race log will be synced up to MAINs log.
SDK GAMING
iRaceControl can send race control-messages to SDK gaming. To do so, open SETTINGS > CACS, activate SDK-Gaming integration, and type in the correct room and user name. You can also set the headlines for informations and penalty messages, as well as the duration they should be visible.
When SDK-Gaming integration is enabled, you will see it's connection status in the status bar of iRaceControl.
The settings for SDK-Gaming is under Settings > CACS.
7.1.HOW TO SET UP
In SDK iRacing Live Timing, open the menu and note the following:
SDK-INFO iRC SETTING
Live Timing Server, room name SDK-Gaming Room
Overlay, Variable access credentials. SDK-Gaming User
The SDK-Gaming User is in the list of Variable access credentials, and need to have the Variable Filter set to "RaceControl"