-
-
Notifications
You must be signed in to change notification settings - Fork 12
Race Settings
The following table will give you an overview over all settings, which are available in the session database. As described here, this settings can be defined precisely for a given simulator / car / track / weather combo and will overwrite the settings you have chosen in the "Race Settings" dialog. This allows you to automate most of the settings required for an upcoming session.
This settings are generally available, although you can and have to define them specific for a given simulator / car / track / weather combo as described. Further down below you can find additional settings, which are not generally available, but are specific for a selected simulator.
Category | Setting | Type | Default | Available in "Race Settings" dialog | Description |
---|---|---|---|---|---|
Assistants | Cooldown | Integer | 90 | No | Number of seconds that the Assistants will wait after a finished session before they will become active again. |
Car | Max steer angle (Steer Lock) | Integer | 480 | No | The maximum number of degrees the steering wheel can be moved in one direction. |
Coach | Repeat whole voice message | Boolean | True | No | When an Assistant voice output is interrupted, it will try to repeat its message. When this setting is enabled, which is the default, the whole message will be repeated. Due to the sometimes long answers of the Driving Coach, you may prefer to set it to False, since then only the interrupted sentence will be repeated and then the voice output continues after that sentence. |
Take session information into account during Practice | Boolean | True | No | If enabled (True), the Coach will include the "Session" instruction when transfering your question to the GPT service during a Practice session. | |
Take stint information into account during Practice | Boolean | True | No | If enabled (True), the Coach will include the "Stint" instruction when transfering your question to the GPT service during a Practice session. | |
Take handling information into account during Practice | Boolean | True | No | If enabled (True), the Coach will include the "Handling" instruction when transfering your question to the GPT service during a Practice session. | |
Take session information into account during Qualifying | Boolean | True | No | If enabled (True), the Coach will include the "Session" instruction when transfering your question to the GPT service during a Qualifying session. | |
Take stint information into account during Qualifying | Boolean | True | No | If enabled (True), the Coach will include the "Stint" instruction when transfering your question to the GPT service during a Qualifying session. | |
Take handling information into account during Qualifying | Boolean | False | No | If enabled (True), the Coach will include the "Handling" instruction when transfering your question to the GPT service during a Qualifying session. Default is False. | |
Take session information into account during Race | Boolean | True | No | If enabled (True), the Coach will include the "Session" instruction when transfering your question to the GPT service during a Race session. | |
Take stint information into account during Race | Boolean | True | No | If enabled (True), the Coach will include the "Stint" instruction when transfering your question to the GPT service during a Race session. | |
Take handling information into account during Race | Boolean | False | No | If enabled (True), the Coach will include the "Handling" instruction when transfering your question to the GPT service during a Race session. Default is False. | |
Data | Update Frequency | Integer | 10 | No | Specifies the number of seconds to wait between each update of the data acquired from the currently running simulator. This data is used mainly by the Race Assistants, but will also be used to detect session state changes in general by other modules. Lower values will increase responsiveness of the Assistants, but may impose increasing system load. With an up-to-date computer system values as low as 2 seconds may be possible wthout negative effects. Be aware, that going lower than 2 seconds will stall the Race Assistants. |
Collect Telemetry during Practice | Boolean | True | No | If enabled (True), general telemetry data is collected by the Strategist during practice sessions. | |
Collect Telemetry during Qualifying | Boolean | False | No | If enabled (True), general telemetry data is collected by the Strategist during qualifying sessions. | |
Collect Telemetry during Race | Boolean | True | No | If enabled (True), general telemetry data is collected by the Strategist during race sessions. | |
Collect Tyre Pressures during Practice | Boolean | True | No | If enabled (True), pressures (hot and cold) are collected by the Engineer during practice sessions. | |
Collect Tyre Pressures during Qualifying | Boolean | False | No | If enabled (True), pressures (hot and cold) are collected by the Engineer during qualifying sessions. | |
Collect Tyre Pressures during Race | Boolean | True | No | If enabled (True), pressures (hot and cold) are collected by the Engineer during race sessions. | |
Engineer | Late Join | Boolean | False | No | If enabled (True), the Engineer will also become active, when you join mid-session. Attention: This can lead to funny results in almost all calculations. |
Repeat whole voice message | Boolean | True | No | When an Assistant voice output is interrupted, it will try to repeat its message. When this setting is enabled, which is the default, the whole message with all sentences which belong together, will be repeated. | |
Refuel Service | Boolean | True | No | If enabled (True), the Engineer will consider refueling during pitstop servicing. You won't want to change this. | |
Tyre Service | Boolean | True (1) | No | If enabled (True), the Engineer will consider tyre changing during pitstop servicing. You may want to disable this for simulators without correct pressure information available in the API, like iRacing. In this case you will have to manage the tyres on your own. | |
Repair Service | Boolean | True | No | If enabled (True), the Engineer will consider repairing during pitstop servicing. You can disable this and manage the repair settings on your own, but why you want to do this? | |
Confirm Pitstop Preparation | Always, Listening, Never | Always | No | If Always, the Engineer will always ask for confirmation when it is time to prepare a pitstop, if Listening, only when a voice command listener is configured and if it is Never, the Engineer will never ask, but will always prepare the pitstop automatically. | |
Confirm Pitstop for Refuel | Always, Listening, Never | Always | No | If Always, the Engineer will always ask for confirmation to plan a pitstop when fuel is low, if Listening, only when a voice command listener is configured and if it is Never, the Engineer will never ask, but will always plan the pitstop immediately. | |
Confirm Pitstop for Repair | Always, Listening, Never | Always | No | If Always, the Engineer will always ask for confirmation to plan a pitstop need for damage repair, if Listening, only when a voice command listener is configured and if it is Never, the Engineer will never ask, but will always plan the pitstop immediately. | |
Confirm Pitstop for Weather | Always, Listening, Never | Always | No | If Always, the Engineer will always ask for confirmation to plan a pitstop due to changing weather conditions, if Listening, only when a voice command listener is configured and if it is Never, the Engineer will never ask, but will always plan the pitstop immediately. | |
Pitstop Service during Practice | Boolean | False | No | If enabled (True), pitstop service handling will be available during practice. Normally disabled, but practical, if you want to test this stuff. | |
Pitstop Service during Qualifying | Boolean | False | No | If enabled (True), pitstop service handling will be available during practice. You typically won't want to enable this. | |
Pitstop Service during Race | Boolean | True | No | If enabled (True), pitstop service handling will be available during race sessions. You won't want to disable this, right? | |
Low Fuel Warning | Integer | 3 | Yes | Specifies the number of laps, the Engineer will issue a fuel warning, before you will run out of fuel. | |
Fuel warning during Practice | Boolean | True | No | If enabled (True), the Engineer will issue fuel warnings during practice sessions. | |
Damage warning during Practice | Boolean | False | No | If enabled (True), the Engineer will issue damage warnings during practice sessions. | |
Pressure warning during Practice | Boolean | False | No | If enabled (True), the Engineer will issue pressure loss warnings during practice sessions. | |
Fuel warning during Qualifying | Boolean | False | No | If enabled (True), the Engineer will issue fuel warnings during qualifying sessions. | |
Damage warning during Qualifying | Boolean | False | No | If enabled (True), the Engineer will issue damage warnings during qualifying sessions. | |
Pressure warning during Qualifying | Boolean | True | No | If enabled (True), the Engineer will issue pressure loss warnings during qualifying sessions. | |
Fuel warning during Race | Boolean | True | No | If enabled (True), the Engineer will issue fuel warnings during race sessions. | |
Damage warning during Race | Boolean | True | No | If enabled (True), the Engineer will issue damage warnings during race sessions. | |
Pressure warning during Race | Boolean | True | No | If enabled (True), the Engineer will issue pressure loss warnings during race sessions. | |
Pitstop | Repair Bodywork | Never, Always, Threshold, Impact | Impact | Yes | Defines, when the Engineer will recommend a pitstop for bodywork repairs. See the above explanations for more information. |
Threshold for Repair Bodywork | Float | 1.0 | Yes | Detail value, when Repair Bodywork is Threshold or Impact. | |
Repair Suspension | Never, Always, Threshold, Impact | Always | Yes | Defines, when the Engineer will recommend a pitstop for suspension repairs. See the above explanations for more information. | |
Threshold for Repair Suspension | Float | 0.0 | Yes | Detail value, when Repair Suspension is Threshold or Impact. | |
Repair Engine | Never, Always, Threshold, Impact | Impact | Yes | Defines, when the Engineer will recommend a pitstop for engine repairs. See the above explanations for more information. | |
Threshold for Repair Engine | Float | 1.0 | Yes | Detail value, when Repair Engine is Threshold or Impact. | |
Change Compound | Never, Temperature, Weather | Never | Yes | Defines, when the Engineer will recommend to mount a different tyre compund at the next pitstop. See the above explanations for more information. If Weather is chosen here, the rules for weather specific tyre compounds apply. | |
Threshold for Change Compound | Float | 0.0 | Yes | Detail value, when Change Compound is Temperature. | |
Tyre Compound Choices | Text | No | Using this setting the available tyre compounds for a given car can be defined. See the explanation of compound rules for more information. | ||
Fresh Tyre Set | Integer | 2 | Yes | Specifies the first fresh tyre set to use during a pitstop. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. | |
Threshold for Target Pressure Deviation | Float | 0.2 | Yes | This value specifies the deviation from the ideal hot pressure, which must be detected, before the Engineer considers altering the cold setup pressure for this tyre. | |
Dry Ideal Tyre Temperature | Integer | 85 | No | The ideal hot temperature for dry compound. | |
Wet Ideal Tyre Temperature | Integer | 50 | No | The ideal hot temperature for wet compound. | |
Dry Target Pressure Front Left | Float | 26.5 | Yes | The ideal hot pressure for the front left tyre with dry compound. | |
Dry Target Pressure Front Right | Float | 26.5 | Yes | The ideal hot pressure for the front right tyre with dry compound. | |
Dry Target Pressure Rear Left | Float | 26.5 | Yes | The ideal hot pressure for the rear left tyre with dry compound. | |
Dry Target Pressure Rear Right | Float | 26.5 | Yes | The ideal hot pressure for the rear right tyre with dry compound. | |
Wet Target Pressure Front Left | Float | 30.0 | Yes | The ideal hot pressure for the front left tyre with intermediate or wet compound. | |
Wet Target Pressure Front Right | Float | 30.0 | Yes | The ideal hot pressure for the front right tyre with intermediate or wet compound. | |
Wet Target Pressure Rear Left | Float | 30.0 | Yes | The ideal hot pressure for the rear left tyre with intermediate or wet compound. | |
Wet Target Pressure Rear Right | Float | 30.0 | Yes | The ideal hot pressure for the rear right tyre with intermediate or wet compound. | |
Tyre Pressure Database Correction | Boolean | False | Yes | If enabled (True) and if cold tyre pressures are available in the pressure database for the current environmental conditions, these values will also be used to calculate the setup pressures at the next pitstop. See the above explanations for more information. | |
Tyre Pressure Temperature Correction | Boolean | True | Yes | If enabled (True), the trend of the air temperature will be considered to apply a small correction to the setup pressures at the next pitstop. See the above explanations for more information. | |
Tyre Pressure Loss Correction | Boolean | False | Yes | If enabled (True), a detected pressure loss of a tyre will be considered and a correction to the setup pressure at the next pitstop will be automatically applied. See the above explanations for more information. | |
Temperature Air Correction Value | Boolean | -0.1 | No | When target pressures are calculated, but no exact match is available, this correction value is added for each degree celsius of deviation in the ambient temperature. | |
Temperature Track Correction Value | Boolean | -0.02 | No | When target pressures are calculated, but no exact match is available, this correction value is added for each degree celsius of deviation in the track temperature. | |
Service Order | Simultaneous, Sequential | Simultaneous | Yes | Defines, whether refueling and tyre service will happen simulteneously, thereby saving some time in the pit. | |
Refuel Service Rule | Fixed, Dynamic | Dynamic | Yes | Defines, whether refueling will take a fixed amount of time or whether refueling will take a fixed amount of time. | |
Refuel Service Duration | Float | 1.8 | Yes | The time used for the Refuel Service Rule in seconds. If refueling time will be calculated dynamically, this number must be the seconds used for each 10 litres of fuel. | |
Tyre Service Duration | Integer | 30 | Yes | Amount of time (in seconds) needed for swapping all four tyres. | |
Session | Average Fuel Consumption | Float | 3.0 | Yes | Average fuel consumption of the given car / track / weather combo. Only used in the first few laps in statistical calculations. This value will be updated automatically (depending on your configuration), once you have been on the track. |
Safety Fuel | Float | 4 | Yes | The amount of fuel the Engineer will take in reserve in his calulations. | |
Fuel Capacity | Float | 120 | No | The size of the fuel tank for the given car / track / weather combo. This value will be updated automatically (depending on your configuration), once you have been on the track. | |
Average Lap Time | Integer | 120 | Yes | Average lap time of the given car / track / weather combo. Only used in the first few laps in statistical calculations. This value will be updated automatically (depending on your configuration), once you have been on the track. | |
Formation Lap | Boolean | True | Yes | If enabled (True), the session rules require a formation lap, which is considered in fuel calculations. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. | |
Post Race Lap | Boolean | True | Yes | If enabled (True), the session rules require a cool down lap after the end of the session, which is considered in fuel calculations. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. | |
Setup | Tyre Compound | Dry, Intermediate, Wet | Dry | Yes | The tyre compound mounted at the start of the session. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). |
Tyre Compound Color | See this list | Black | Yes | The tyre compound mixture used at the start of the session. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Tyre Set | Integer | 1 | Yes | Specifies the tyre set of the tyres initially mounted for the car. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Dry Pressure Front Left | Float | 26.1 | Yes | The setup (cold) pressure of the front left tyre at the start of the session for dry tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Dry Pressure Front Right | Float | 26.1 | Yes | The setup (cold) pressure of the front right tyre at the start of the session for dry tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Dry Pressure Rear Left | Float | 26.1 | Yes | The setup (cold) pressure of the rear left tyre at the start of the session for dry tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Dry Pressure Rear Right | Float | 26.1 | Yes | The setup (cold) pressure of the rear right tyre at the start of the session for dry tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Wet Pressure Front Left | Float | 28.5 | Yes | The setup (cold) pressure of the front left tyre at the start of the session for intermediate or wet tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Wet Pressure Front Right | Float | 28.5 | Yes | The setup (cold) pressure of the front right tyre at the start of the session for intermediate or wet tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Wet Pressure Rear Left | Float | 28.5 | Yes | The setup (cold) pressure of the rear left tyre at the start of the session for intermediate or wet tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Wet Pressure Rear Right | Float | 28.5 | Yes | The setup (cold) pressure of the rear right tyre at the start of the session for intermediate or wet tyre compounds. Typically not entered into the "Session Database", but into "Race Settings" just before the start of a session. For some simulators, this information can be determined automatically via API (depending on your configuration). | |
Spotter | Late Join | Boolean | True | No | If enabled (True) (which is the default), the Spotter will also become active, when you join mid-session. |
Repeat whole voice message | Boolean | True | No | When an Assistant voice output is interrupted, it will try to repeat its message. When this setting is enabled, which is the default, the whole message with all sentences which belong together, will be repeated. | |
Car Categories | All, Classes, Cups | Classes | No | Specifies which cars and drivers will be considered to be in different categories or classes by the Spotter for the purpose of position and gap information. Classes stands for the different car classes like "GT3" or "GT4" and Cups stands for different race ratings like "Pro", "Pro-AM" and so on. The default let the Strategist differentiate between the different car classes. | |
Car Indicator | Number, Position, Both | Position | No | Using this setting you can define, how the Spotter will indicate other cars. Number will result in phrases like "Car number 7 had a problem", whereas Position will result in a phrase like "The car in P 3 had a problem". The position used in the indication will relate to the car class. Using "Both" here will result in the Spotter mentioning both informations. | |
Threshold for Lap Up car in range | Float | 1.0 | No | Specifies the gap in seconds, before the Spotter will analyzes a situation with a car which is at least one lap ahead of you. | |
Threshold for Lap Down car in range | Float | 2.0 | No | Specifies the gap in seconds, before the Spotter will analyzes a situation with a car which is at least one lap behind you. | |
Minimum gap for observation of car in front | Integer | 2 | No | The minimum gap in seconds, for which the Spotter gives you gap and delta information about the car in front of you. | |
Maximum gap for observation of car in front | Integer | 3600 | No | The maximum gap in seconds, for which the Spotter gives you gap and delta information about the car in front of you. | |
Minimum gap for observation of car behind | Integer | 2 | No | The minimum gap in seconds, for which the Spotter gives you gap and delta information about the car behind you. | |
Maximum gap for observation of car behind | Integer | 3600 | No | The maximum gap in seconds, for which the Spotter gives you gap and delta information about the car behind you. | |
Threshold for Attack car in front | Float | 0.8 | No | Specifies the gap in seconds, before the Spotter will think that it is time to attack the car in front of you (if you are faster on average). | |
Threshold for Gained on car in front | Float | 0.3 | No | Specifies the time in seconds, you must have gained to the car in front, until the Spotter will give you updated information about the gap and the laptime difference. | |
Threshold for Lost on car in front | Float | 1.0 | No | Specifies the time in seconds, you must have lost to the car in front, until the Spotter will give you updated information about the gap and the laptime difference. | |
Threshold for Attack car behind | Float | 0.8 | No | Specifies the gap in seconds, before the Spotter will think that the car behind you will attak you (if it is faster on average). | |
Threshold for Lost on car behind | Float | 0.3 | No | Specifies the time in seconds, you must have lost to the car behind you, until the Spotter will give you updated information about the gap and the laptime difference. | |
Threshold for Gained on car behind | Float | 1.5 | No | Specifies the time in seconds, you must have gained to the car behind you, until the Spotter will give you updated information about the gap and the laptime difference. | |
Threshold for Overtaking car ahead | Float | 0.3 | No | Specifies the time gap in seconds, which is considered to be the range to start overtaking. In this case, no more information is given for the car ahead. | |
Maximum distance for accident ahead | Integer | 800 | No | Accidents will be reported by the Spotter when they are detected in this range before the drivers car. The distance will be interpreted according to the currently chosen "Length" unit (meters or yards). | |
Maximum distance for accident behind | Integer | 500 | No | Accidents will be reported by the Spotter when they are detected in this range behind the drivers car. The distance will be interpreted according to the currently chosen "Length" unit (meters or yards). | |
Maximum distance for slow car | Integer | 500 | No | Slow cars will be reported by the Spotter when they are detected in this range behind the drivers car. The distance will be interpreted according to the currently chosen "Length" unit (meters or yards). | |
Strategist | Late Join | Boolean | False | No | If enabled (True), the Strategist will also become active, when you join mid-session. Attention: This can lead to funny results in almost all calculations. |
Repeat whole voice message | Boolean | True | No | When an Assistant voice output is interrupted, it will try to repeat its message. When this setting is enabled, which is the default, the whole message with all sentences which belong together, will be repeated. | |
Car Categories | All, Classes, Cups | Classes | No | Specifies which cars and drivers will be considered to be in different categories or classes by the Strategiest for the purpose of position and gap information. Classes stands for the different car classes like "GT3" or "GT4" and Cups stands for different race ratings like "Pro", "Pro-AM" and so on. The default let the Strategist differentiate between the different car classes. | |
Car Indicator | Number, Position, Both | Position | No | Using this setting you can define, how the Strategist will indicate other cars. Number will result in phrases like "Your gap to car number 7 is 5 seconds.", whereas Position will result in a phrase like "The gap to the car in P3 is 5 seconds.". The position used in the indication will relate to the car class. Using "Both" here will result in the Spotter mentioning both informations. | |
Confirm Pitstop Planning | Always, Listening, Never | Always | No | If Always, the Strategist will always ask for confirmation when it is time to plan an upcoming pitstop, if Listening, only when a voice command listener is configured and if it is Never, the Strategist will never ask, but will always ask the Engineer to plan the pitstop automatically. | |
Confirm Strategy Update | Always, Listening, Never | Always | No | If Always, the Strategist will always ask for confirmation when the strategy needs to be updated, if Listening, only when a voice command listener is configured and if it is Never, the Strategist will never ask, but will always update the stratey immediately. | |
Confirm Strategy Cancel | Always, Listening, Never | Always | No | If Always, the Strategist will always ask for confirmation when he thinks that a strategy is no longer valid and should be dropped, if Listening, only when a voice command listener is configured and if it is Never, the Strategist will never ask, but will always drop the stratey immediately. | |
Confirm Strategy Explanation | Always, Listening, Never | Always | No | If Always, the Strategist will ask whether he should explain the changes, before a strategy gets updated, if Listening, only when a voice command listener is configured and if it is Never, the Strategist will always explain the stratey changes. | |
Confirm Strategy Update for Weather | Always, Listening, Never | Always | No | If Always, the Strategist will always ask for confirmation to update the strategy or prepare for an unplanned pitstop due to changing weather conditions, if Listening, only when a voice command listener is configured and if it is Never, the Strategist will never ask, but will always initiate the necessary actions immediately. | |
Strategy summary at race start | Boolean | True | No | If enabled (True), the Strategist will give a summary of the active strategy in one of the first laps of the race. | |
Strategy summary after each update | Boolean | True | No | If enabled (True), the Strategist will give a summary of the new strategy after each update. Please note, that strategy updates must be enabled in the settings. Also note, that setting this to False may be confusing, if you require a confirmation of a strategy update on the other hand, since it would not be obvious what will be confirmed. | |
Strategy summary before pitstop | Boolean | False | No | If enabled (True), the Strategist will give a summary of the active strategy just before an upcoming pitstop. This can be enabled as an alternative to the other settings above. | |
Strategy | Position Extrapolation | Integer | 3 | Yes | The Strategist permanently simulates the events of the upcoming laps depending on the development of the recent laps to predict future race standings. This information is used for example for pitstop recommendations and strategy updates. This value specifies, how many laps into the future will be calculated on each crossing of the start / finish line. Attention: High values might result in high CPU consumption. |
Overtake Delta | Integer | 1 | Yes | During simulation of the future race development, the Strategist will also take overtaking into account. This value defines the time loss for both cars in seconds according to this formula: Abs( X / laptime difference), where X is the value entered here. | |
Pitlane Delta | Integer | 60 | Yes | The time difference in seconds between drive by and drive through of the pitlane. | |
Pitstop Variation Window (+/- Lap) | Integer | 3 | Yes | Specifies, how many laps before an after the projected pitstop (depending on available fuel), the Strategist will simulate to create his recommendation for an upcoming pitstop. Also used in the dynamic traffic simulation to specify the number of laps the simulation is allowed to deviate from the pitstop lap derived by linear calculation. As said, remaining fuel is taken into account, so if you want to be able to delay your pitstop long enough, be sure, to increase the amount of safety fuel as well. | |
Traffic Track Length | Integer | 5 | Yes | Specifies the length of the track (in percentage of the overall length) which will be considered in traffic density calculations by the Strategist. Used both in pitstop recommendations derived by linear calculations as well as in the dynamic traffic simulation using the Monte Carlo method. | |
Dynamic Traffic Simulation (Monte Carlo) | Boolean | false | No | If this setting is enabled, the Strategist will use a Monte Carlo simulation model to create a probability distribution for the further race development, thereby finding the best possible lap for the next pitstop (see this Wikipedia entry for an introduction to Monte Carlo methods). Once enabled, you can use the following settings to fine tune the probability distrubution and the depth of search. WARNING: This will consume lots of CPU cycles and can take quite some time. It is strongly advised, to let this setting disabled, unless you own a really powerful PC. In team races, it is possible to run the Monte Carlo simulation in the "Team Center", thereby offloading the computational load from the drivers PC. | |
Traffic Randomness | Integer | 5 | No | [Dynamic Traffic Simulation] Specifies the general random factor for each data point in percentage. 5% means, that the given data point will defer from the value provided by a linear calculation in 5% of all cases. | |
Traffic Scenarios | Integer | 20 | No | [Dynamic Traffic Simulation] Specifies the number of scenarios to generate before choosing the best scenario. Be aware, that each scenario in itself might contain many scenerios for tyre wear, compound mixture choices and so on, if you have used the Optimizer while generating the initial strategy. So be careful using high numbers here in combination with complex strategies, or you might end up waiting for a long time... | |
Simulate lap time variations (Consistency) | Boolean | true | No | [Dynamic Traffic Simulation] If enabled, variations in lap time of you and your opponents will be taken into account according to the consistency values of past laps. | |
Simulate driver errors (Control) | Boolean | true | No | [Dynamic Traffic Simulation] If enabled, random off-track events and even incidents will be simulated based on the car control and previous incidents of a given driver. This will have a much larger effect than variations by generated of the drivers consistency. | |
Simulate opponent pitstops | Boolean | true | No | [Dynamic Traffic Simulation] Will enable the simulation of pitstops of your opponents. Recent pitstops will taken into account, if available. Otherwie a random factor is used here as well. | |
Autonomous Mode | Yes, No, Custom | Custom | Yes | This is a very special setting. It lets you give the different Assistants a lot of autonomy and capabilities to guide you through a race without further interaction needed from your side. The setting combines a lot of settings also available seperately, namely: "Engineer: Confirm Pitstop Preparation", "Strategist: Confirm Pitstop Planning", "Strategist: Confirm Strategy Update" and "Strategist: Confirm Strategy Explanation". When the value of "Autonomous Mode" is Yes, all these other settings are implicitly assumed to be true, if the value is No, all these other settings are assumed to be false, and if the value is Custom, those settings are used as they are specified. Therefore, if you set "Autonomous Mode" to Yes, the Strategist and the Engineer will work together during strategy planning and execution without asking the driver for confirmation. | |
Automatic recalculation (Laps) | Integer | 0 | Yes | If there is an active strategy for the current session, the Strategist can try to optimize this strategy on behalf of the current race situation and will inform the driver if a better strategy can be derived, who then can decide to activate the new strategy. This setting specifies the number of laps between each recalculation, with 0 meaning no recalculation at all. Enabling this will put a high demand on the CPU, so test it before using it in an important race. | |
Automatic recalculation (Pitstop) | Integer | 0 | Yes | If there is an active strategy for the current session, the Strategist can try to adjust this strategy when an upplanned pitstop has been necessary. If the strategy could be adjusted to the new situation, the driver will be informed and can decide to activate the new strategy. This setting specifies the number of laps a pit stop may deviate from the originally planned pitstop lap, so that it is considered to be in line with the strategy. 0 als means here no recalculation at all. Enabling this will put a high demand on the CPU after a pitstop, so test it before using it in an important race. | |
Team Session | Cooldown | Integer | 600 | No | Number of seconds that will be waited after a finished session before a new connection to a Team Server session will be opened. |
(1) The default for iRacing is False, since the simulator does not provide correct tyre pressure information while driving. This will lead to setup pressure values, which are way off, when tyres are changed at the pitstop. Therefore it might be better to manage tyre change manually. Up 2 u...
The following settings are only available, if you have selected the corresponding simulator.
- Assetto Corsa
Category | Setting | Type | Default | Description |
---|---|---|---|---|
Pitstop | Key Delay | Integer | 20 | The time in ms to wait between each virtual key press, when controlling the pitstop dialog of Assetto Corsa. Increase this, if your computer can't keep up with the speed of the virtual input. |
# Car Specific Settings | Integer | 0 | Some cars of Assetto Corsa provide car specific settings, which can be changed during pitstop. You can specify them using this setting, so that the setting navigation for these cars is correct. Only necessary for cars not already known in the meta data set for Assetto Corsa in Simulator Controller. | |
Minimum Pressure Front Left | Integer | 15 | Minimum pressure for the front left tyre allowed for a given car in Assetto Corsa. Only necessary for cars not already known in the meta data set for Assetto Corsa in Simulator Controller. | |
Minimum Pressure Front Right | Integer | 15 | Minimum pressure for the front right tyre allowed for a given car in Assetto Corsa. Only necessary for cars not already known in the meta data set for Assetto Corsa in Simulator Controller. | |
Minimum Pressure Rear Left | Integer | 15 | Minimum pressure for the rear left tyre allowed for a given car in Assetto Corsa. Only necessary for cars not already known in the meta data set for Assetto Corsa in Simulator Controller. | |
Minimum Pressure Rear Right | Integer | 15 | Minimum pressure for the rear right tyre allowed for a given car in Assetto Corsa. Only necessary for cars not already known in the meta data set for Assetto Corsa in Simulator Controller. | |
Repair duration for bodywork damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the bodywork at a pitstop. | |
Repair duration for suspension damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the suspension at a pitstop. | |
Repair duration for engine damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the engine at a pitstop. | |
Track | Type | Circuit, Rally, Hill, Street | Circuit | Defines the type of the specific track. ALl closed tracks are of type Circuit, all open tracks are of type Rally. |
- Assetto Corsa Competizione
Category | Setting | Type | Default | Description |
---|---|---|---|---|
Pitstop | Key Delay | Integer | 20 | The time in ms to wait between each virtual key press, when controlling the pitstop dialog of Assetto Corsa Competizione. Increase this, if your computer can't keep up with the speed of the virtual input. |
Image Search | Boolean | False | If enabled (True), the image search method is used, when controlling the Pitstop MFD of Assetto Corsa Competizione. If you enable this, because the default option walk disturbs you while driving, you have to provide the search images as described in the [documentation] for the "ACC" plugin. | |
Repair duration for bodywork damage | Float | 0.282351878 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the bodywork at a pitstop. | |
Repair duration for suspension damage | Float | 31.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the suspension at a pitstop. | |
Repair duration for engine damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the engine at a pitstop. |
- rFactor 2 and Le Mans Ultimate
Category | Setting | Type | Default | Description |
---|---|---|---|---|
Data | Pitstop setup update interval | Integer | 60 | Specifies how often the current choices in the Pitstop menu are requested. Since the API call moves the cursor in the menu, it can be very annoying for the driver, when this is done to often. If 0, the data is never requested. Otherwise specify a number of seconds to wait between each request. Default is 60 seconds. |
Pitstop | Repair duration for bodywork damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the bodywork at a pitstop. |
Repair duration for suspension damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the suspension at a pitstop. | |
Repair duration for engine damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the engine at a pitstop. |
- Automobilista 2 and iRacing
Category | Setting | Type | Default | Description |
---|---|---|---|---|
Pitstop | Key Delay | Integer | 20 | The time in ms to wait between each virtual key press, when controlling the pitstop settings of the simulator. Increase this, if your computer can't keep up with the speed of the virtual input. |
Repair duration for bodywork damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the bodywork at a pitstop. | |
Repair duration for suspension damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the suspension at a pitstop. | |
Repair duration for engine damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the engine at a pitstop. | |
Track | Type | Circuit, Rally, Hill, Street | Circuit | Defines the type of the specific track. ALl closed tracks are of type Circuit, all open tracks are of type Rally. |
- Project Cars 2 and RaceRoom Racing Experience
Category | Setting | Type | Default | Description |
---|---|---|---|---|
Pitstop | Key Delay | Integer | 20 | The time in ms to wait between each virtual key press, when controlling the pitstop settings of the simulator. Increase this, if your computer can't keep up with the speed of the virtual input. |
Repair duration for bodywork damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the bodywork at a pitstop. | |
Repair duration for suspension damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the suspension at a pitstop. | |
Repair duration for engine damage | Float | 0.0 | This value is multiplied with the internal damage percentage to compute the number of seconds need to repair the engine at a pitstop. |
Simulator Controller - 2024 by Oliver Juwig (TheBigO), Creative Commons - BY-NC-SA
- Quick Start
- Installation
- Configuration
- Splash Screen Editor
- Translations Editor
- Controller Layout Editor
- System
- Tactile Feedback
- Motion Feedback
- Pedal Calibration
- Driving Coach
- Race Engineer
- Race Strategist
- Race Spotter
- Team Server
- ACC - Assetto Corsa Competizione
- AC - Assetto Corsa
- IRC - iRacing
- RF2 - rFactor 2
- LMU - Le Mans Ultimate
- R3E - RaceRoom Racing Experience
- AMS2 - Automobilista 2
- PCARS2 - Project CARS 2
- Integration
- Introduction
- Race Settings
- Track & Automation
- Sessions
- Laps
- Strategies
- Setups
- Tyre Pressures
- Administration
- Configuration
- Introduction
- Describing Setup Issues
- Understanding the Recommendations
- How it works
- Managing Car Setups
- Extending and Customizing
- Introduction
- Starting a session
- Data Analysis
- Telemetry Viewer
- Planning and managing practice stints
- Exploring data
- Exporting data
- Introduction
- Overview Report
- Car Report
- Driver Report
- Positions Report
- Lap Times Report
- Performance Report
- Consistency Report
- Pace Report
- Introduction
- Normal vs. Lite UI
- Connecting to a session
- Data Analysis
- Telemetry Viewer
- Strategy Handling
- Session & Stint Planning
- Driver specific tyre pressures
- Planning a Pitstop
- Introduction
- Installation
- Interacting with Jona
- Racing with Jona
- Technical Information
- Troubleshooting
- Introduction
- Installation
- Interacting with Cato
- Racing with Cato
- Strategy Handling
- Technical Information
- Troubleshooting
- Introduction
- Installation
- Interacting with Elisa
- Alerts & Information
- Simulator Integration
- Track Mapping
- Track Automations
- Introduction
- Booster Overview
- Instructions
- How it works
- Managing Actions
- Managing Events
- Predefined Actions & Events
- Introduction
- Installation & Configuration
- Managing teams
- Preparing a team session
- Running a team session
- Server Administration
- How it works
- Troubleshooting