RaceTools v2.68 – new Check Control Lines/Validate Track Map features

Tired of switching track maps during a race weekend? Using the new $U message to identify the control lines from the data feed (available only since Detroit), RaceTools can now use a single track map to display both the race and alternate track configurations.

Check Control Line to automatically adjust for Alternate SF line(s):

To automatically adjust for different SF/SFP timelines, enable the ‘Check Control Line’ option found in the main program Options menu.


Validate Trackmap to manually check and adjust for Alternate SF line(s):

To manually force the software to adjust the SF line, select the Validate Trackmap menu item from the Track Map popup menu (right click track map). This will prompt for the SF and SFP timelines to use and compare it with the current configuration and track map. If the SF/SFP lines are different and found in the track configuration, the software will automatically offset the track map to match the specified timelines. Note that you can only execute this once the track configuration is available (ie. when the session has gone warm).


How it works:

  1. On a new session or when the program launches, only the SF line is displayed. There are no sections defined.2015-07-23_12h40_57
  2. After the track message is received (after the session has gone warm), the sections and location of timelines are available. If this is a PQ session and the track map loaded is the race map, the track map does not match the actual location of the SF line for this session.2015-07-23_12h41_49
  3. If the Check Control Line option is enabled, as soon as the $U message is received, RaceTools will compare the SF and SFP lines defined by the $U message with the current track configuration. If it does not match, RaceTools will adjust the track to the SF/SFP lines defined by the $U message.

    If the Check Control Line option is disabled, you can force RaceTools to validate the track map by executing the ‘Validate Trackmap’ option in the track map popup menu. You can use this if the $U message is missing or incorrect. If the $U message is incorrect, you should disable the ‘Check Control Line’ option to prevent it from automatically adjusting the track map.

    Remember that the track definition must be available before you can execute the Validate Trackmap function and the SF and SFP lines must be defined in the track definition. To see the track definition, open the Track Editor (CTRL+T).

    The map below is after the Validate Trackmap has been executed (either manually or automatically) for a PQ session.2015-07-23_12h52_19

RaceTools v2.68

This is a maintenance upgrade and offers a few refinements to the software as requested by our users.

For IndyCar, one of the most common errors and frustrating parts of the software was making sure the correct map was loaded and the correct SF line was configured for the race and alternate start/finish lines. The latest version makes use of the newly added $U message and it’s control line designator (*) to identify the lap counter line for each session. With this information, RaceTools can now compare the settings to make sure the correct timeline is used for the SF and SFP lines, and if required, shift the trackmap to the alternate SF line. Now you can just load the race map and not have to switch between session types and let the software do the change for you.

Other minor changes are listed below:

2018 07 22 – fix LineCrossingLog lap calculation
– add ValidateTrackMap to trackmap to check for correct SF/SFP timelines (use IndyCar RP $U to determine SF/SFP lines)
– automatically switch between SF and Alt SF for IndyCar series when $U RP messages available.
2015 07 16 – add parsing for $M Manufacturer Points: messages, store in SessionInfo.ManufacturerPoints
– add Manufacturer Points to Clock types
– Clear LineChartPopUp in NewSession
2015 07 13 – Set Track Map CarPosition to use 1/3 spacing if Side-By-Side enabled
– check LiveSections Column Width when updating column titles. Make sure column titles can be seen.
– eRMON filter out duplicate $L messages
2015 06 29 – update StartStint and EndStint to use Telemetry.ElapsedTime-Session.StartTime for actual Elapsed Time instead of TOD, fixes Drive Times report
2015 06 27 – implement setMinimumPitStopTime to update minpitstoptime within PitLaneMonitor
– set Current.PitIn and Current.PitOut times to session time, not TOD. Telemetry.ElapsedTime is in TOD.
2015 06 27 – re-enable freeze field for IMSA Race Control version
2015 06 26 – change lap speed calculations to use Session.TrackLength instead of Track.Length (which is populated by $U message and may not be the same as the ‘official’ track length
– fix IMSA version to subtract SessionInfo.StartTime from TimeToLine calculations. Telemetry.ElapsedTime is TOD not session time. Fixes ProjectedTime calculations
2015 06 22 – move code to GenerateSectionTimes to routine in TASDB module
2015 06 21 – optimize calculations to use objects instead of database – reduce calculation time from 17s to 0.06s
– add ‘P’ column to display RecNo
– hide/exclude Class/Rating from non-MultiClass versions
2015 06 18 – add support for WEC Al Kamel $PASSING records
2015 06 01 – Force SF, SFP, Start, PIT, In Lap, Out Lap to be T1, P1, T1, PIT, IL and OL to fix wrong configuration issues in IMSA version.
2015 05 30 – add mnuLockScale to Graphs to not automatically reset the Axis scales
2015 05 16 – make BoldTitle an option in the configuration file ([Layout] BoldFont=1)