Introduction

This page describes the workings of Track Limits monitoring and covers a range of areas including:

System Overview

Track Limits can be configured to one of the following profiles: None, Default, Strict and Relaxed. This is configured on the session settings page in single player. It can also be configured on the dedicated server via the UI where sessions are configured.

These profiles set up the thresholds for penalties and warnings for infringements. In non race sessions the penalty is just to invalidate your current and possibly next lap. In a race you earn points. Once you pass a points threshold which can be configured a drive through penalty is issued. This setting is configured on the single player race configuration screen or on the Dedicated UI by entering a number of points next to the rule selection drop down. Additionally a single infringement of at least 3 points also triggers an automatic drive through penalty.

A Driving Standard Dialogue will show when a driver is at risk of an infringement. They will have a brief opportunity to slow down whilst the situation is calculated to avoid a penalty however by how much is not shown.

If drivers pass a driver whilst off track illegally then a dialogue will tell them as such and recommend they give back the place. They will have 15s to give up the place. The system will ignore cars that are off track, driving slowly, in the pits or have DNFd. Note that if further positions are gained during 10s period, this time will be extended.

Cut Track Detection

A track cut is defined as leaving the legal bounds of the race surface and re-joining it and gaining a lasting time or positional advantage from it.

By default the game detects if the car is off track by using the car's average track width. This means to ensure you do not instigate an investigation you need to retain two complete wheels inside the track bounds, although there will be a little further grace beyond this in practice.

The calculations for if it take into consideration the following:

Once we return to track we now take some time to consider the situation and to see if the driver is trying to correct for their errors, under control or even going quick enough. This will help reduce false detections and receiving warnings for basically making a mistake.

The following factors must be present before a cut track is scored:

The system will handle if a driver passes over the track and off again during a track limits violation provided it is with in the limits set above, and will continue scoring the cut until they finally rejoin properly.

Whilst the track limits are being scored, an “Evaluating” on screen message appears. This is now colour coded. The colours mean the following:

Drivers are strongly warned to behave appropriately and avoid sudden braking with cars behind them.

Passing when under Track Limits Investigation

The system logs gained positions when a Track Limits investigation is underway.

At the time of position change we log cars which meet the following criteria:

Then at each point during the process we re-check the above criteria and only score the cars that are behind us and meet this criteria.

The track limits info dialogue shows the current state of play, with the number of passes made illegally and also the name of the driver closest that we need to give the position back too.

An initial 15s is given to return positions. If a place is gained with 50% of the time remaining, a further 50% of the initial time will be granted to prevent drivers from being penalised at the last moment before scoring the incident.

Note that if you slow down a lot but do not return the place, you may not be penalised if you give up enough time. Similarly if the opposition driver slows down to try to instigate a penalty for you, the pass maybe automatically removed. However the system does not attempt to figure out if you cut and knocked another driver off the track for example.

Wall Riding Detection

The track limits system features detection for wall riding.

The amount of wall contact logged is scaled by the amount of throttle input. So if you are not accelerating you will not be penalized

The detection works on both a per incident basis and also over the entire lap. Depending on the penalty mode selected, different allowances are set. Note that on strict mode in non race sessions nearly any contact with the wall will invalidate your lap.

Wall contact starts a generic track limits violation, and the system will monitor for passes immediately after wall contact. However time gained calculations do not start unless the car runs out of legal bounds at some point.

Pitlane Violations

Pitlane Violations can be disabled on a per track basis or via the RFM or GDB. 

At present they are enabled unless running on an Oval in a non race session.

Track Limits Violations in non Race sessions

In non race session if what if a violation is:

Track Limits Violations in Race sessions

In race sessions warning points are awarded for Track Limits violations.

Wrong Way Driving

If a driver goes the wrong way down the track they can be disqualified. However the system will take into account how far away from the race track they are and how quickly they are travelling as well as trying to give the player as much time as possible to react.

Differences between Default, Strict and Relaxed profiles

Compared to the “default” profile, the “relaxed” profile makes the following changes:

Compared to the “default” profile the “strict” profile makes the following changes:

Per Track Customization

Much of the previous per track customization has been removed at this time. Note you do not need to specify these unless you wish to change them. The only settings that are available at present and their default values are:

The intention is to keep all other systems internal.

The majority of the track limits violations can be tweaked by ensuring the cut track corridors in the AIW file are correct.

All previous GDB settings are deprecated.

Logging / Debugging Issues

The game now logs the results of each track cut violation to the trace log file. This will allow for easier debugging of false cuts. A log file along with a video/replay of the issue should be sufficient to analyse the situation.

When using ModDev, you can change the Track Limits profile via the Steward Tweakbar. This also allows you to set the Track Limits Info mode, giving you options to show the Default mode, Penalties only or the Debug mode. The debug mode shows on screen live scoring of cuts.

The steward bar also shows internal parameters, however it is not possible for users to change these parameters permanently. The three different profiles set these accordingly.

On Screen Display

On the Graphics page you can configure where the Track Limits dialogue is shown via the “TLI screen position” options. By default it will be set to “HUD”. This means it will show where the HUD configures it to be shown. However many HUDs will not have been updated yet. So you can configure this manually if you desire.

When authoring HUDs you can now set up the Track Limits dialogue to use fonts and the size and position required for your HUD. This is available via the editor in ModDev. If it is not configured, it will default to the way it is setup in the Default S397 HUD. Below are the options that are available for configuration from the HUD.ini

// DSI Configuration (These are the default values for the game)
DSI_SCREENXPOS = 0.5
DSI_SCREENYPOS = 0.2
DSI SCREENXSIZE = 0.18
DSI_SCREENYSIZE = 0.065
DSI_SCREENOPACITY = 0.75
DSI_FONT = 0
DSI_FONTHDRSCALE = 1.0
DSI_FONTMSGSCALE = 0.8
DSI_TEXTX = 0.005
DSI_HDRY = 0.25
DSI_MSGY = 0.7


Content Creation

How to setup track limits is covered separately on our developers guide.