Create New Participants for Unknown Chips

This controls how the software will handle unrecognised timing data, by default the software will create a participant record for any unrecognised transponder code, this is useful if you may have late registrations or mixed up transponders. 

You can choose to disable this, or enable it only for transponders listed in your Chip File.

How to Handle Times of Multi-Day Events

This setting is only shown when the End Date of your Event Settings is set to a date different from the Start Date. 

By default all times are stored as a value in seconds counted from midnight, however for multi-day events this time needs to count past 24 hours, and so a start reference is subtracted in order to get the total elapsed time. 

This can either link to the Event start date, which will subsequently automatically update, or a fixed date reference. Note that changing this setting does not impact existing timing data, if you need to fix this data you will need to reimport the passings. 

Keep Timing Active After Closing the Browser

Normally when timing you need to have keep RACE RESULT 12 open in the web browser in order to keep connections to Timing Systems alive.

For long-running events it can be useful to keep these connections active until the end of the event, this can be enabled using the Keep timing active checkbox at the bottom of the Chip Timing / Systems windows. 

When using this option, connected systems will remain connected until the event file end date, defined in the Basic Settings. 

If working with offline systems you will still need to keep the RACE RESULT Web Server running, and so requires the computer to remain active. It is advised to work online if using this feature.