• • Room name – The room declared in iRacing Live Timing
  • User name – Represents a user which has been granted access to variables in iRacing Live Timing. In iRacing Live Timing, navigate to Variable Access Credentials in the F3 settings, enter your chosen username and variable type to grant access to (Overlay and/or IRacing on separate lines).
  • Sequence duration – The total time of the timed sequence of a given clock. When time in sequence reaches Sequence time it is reset to 0. To avoid restarting the sequence simply use a very large value.
  • Sequence state – The current time in sequence.
  • Reset variable name – The name of variable that resets Sequence state to 0 when set to True
  • Timed events – A list of actions to be performed on variables a given time in the sequence. Each line represents an event. Each event is composed of 4 fields separated by spaces:
    • Time in seconds. Can be decimal.
    • Variable name.
    • Equal sign.
    • Value with ” in front and “; behind.
  • Sequence type – buttons selecting a given clock. All clocks are always running when their context is active even if not displayed. Contexts available:
    • 4 general purpose clocks named Global 1 to Global 4: these clocks are always running.
    • 4 session type specific clocks (not counting race clocks) named Testing, Practice, Qualifying and Warmup: these clocks are only active and running when in the corresponding session kind. When not running clock is set to 0.
    • 12 race session state specific clocks named Race – Gridding,Race – Getting ready,Race – Formation laps,Race – Racing,Race – Finishing,Race – Finished,Race – One to green flag,Race – Green flag,Race – Yellow flag,Race – White flag,Race – Five to go flag,Race – Ten to go flag: these clocks correspond to the different session states possible in a race. These clocks are only active and running when in the corresponding session kind. When not running clock is set to 0.User interface:

The Multi Scheduler is automatically started on app load. To make edits to the events first stop the scheduler using the Stop button and click the Start button after changes have been made.

All the settings can be loaded and saved to a json formatted file using the Export and Import buttons.

The app stores your settings locally. Therefore when the web page is loaded or reloaded your settings are loaded as well. Several sets of settings can be prepared by adding the instance parameter “?instance=settings_name” to the URL. For example https://livetiming.sdk-gaming.co.uk/multi-scheduler.html?instance=settings_v1 will load the settings_v1 set of parameters.

• In the example on the left:
  • At the beginning of the sequence:
    • all components except the grid component are hidden
    • the grid component is displayed
    • grid row is set to 1 (first row)

• • Then every 20 seconds the grid is shifted one page (6 rows)
  • After 120 seconds it starts over again
  • The list of all available variables and their values can be found here: Variables

There are a huge amount of possible uses for the Multi Scheduler. Make sure you join our Discord server for help in getting started on your own project: https://discord.gg/dj6CBxF