F1LT is a Formula 1 live timing application written using Qt library for Windows and Linux systems. It is an alternative application to the java applet available on formula1.com site. To use the application you only need an account on formula1.com site, which is used to login into the live timing server and obtain the data.
Main features of the application:
- gathering all live timing data - you can see lap time history of every driver,
- session statistics - fastest laps, fastest pit stops, speed records, charts,
- lap time comparison tool - allows you to compare lap times of up to 4 drivers at once,
- head to head tool - a driver tracking tool - select two drivers and program will be calculating the gap between them, showing the differences between lap and sector times and drawing charts on every lap,
- recording and replaying live timing - every session can be recorded and played later, very usefull tool when watching a replay of the race.
Main window of the application is presented on Fig. 1. We can see three panels there - the live timing data is presented on the left panel, while the right panel contains many additional informations, which include:
- driver info tab: lap history with charts
- basic informations about current event
- session statistics:
- fastest laps
- speed records
- fastest pit stops
- session commentary
The top panel contains session and weather data.
Icons on the toolbar:
- open archived LT session,
- connect to the LT server,
- head to head tool,
- lap time comparison tool,
- program preferences,
- exit,
- start recording the session,
- stop recording.
This is the main panel where the current live timing data is shown. This is basically the same what you can see using the formula1.com applet, so there isn't much to explain. Meaning of the colors:
- white - most of the data, no particular meaning,
- green - personal record of the driver
- violet - fastest lap (or sector) of the session
- red - driver is in the pits
- yellow - data from the previous lap/sector
When you select a driver and double-click on his name, his statistics will be shown in the right panel. You can use standard cursor keys, page up-page down, home and end keys to move around the table. Hitting enter will do the same as mouse double-click. Panel contains weather data and session timer. During the race there is also information about completed and total laps. Top left icon correspond to the current flag status (green, yellow, red, safety car, etc.). This tab contains data and statistics of a selected driver. It is splitted into 3 sub-tabs:
- basic driver information and statistics (Fig. 2.)
- lap time chart (Fig. 3.)
- position and gap charts (Fig. 3.)
- white - usuall laps
- yellow - laps behind a safety car
- red - pit stops
- green - driver best lap
- violet - fastest lap of the race
- cyan (free practice and quali only) - if the current lap time is worse than the drivers best, the LT server doesn't send us this time - it is approximated by the program using sector times (lap time is rounded to 0.1 of the second)
Lap history data can be selected and copied to the clipboard - just select what you need and press Ctrl-C. Three charts are printed in the driver data tab (Fig. 3.):
- lap time chart - contains sector and lap times, laps behind SC are printed in yellow, dots correspond to the pit stops,
- position chart - prints the drivers positions during the session. If you connect to the LT server during the race, server sends the position history, hence this chart always prints driver positions from the start of the race in opposition to other charts which are printed only for gathered data (e.g. when you connect on lap 14, program will start gathering data from that lap onwards). As previously, dots correspond to pit stops,
- gap to the leader chart - so far this works only during the race and free practice. The meaning of dots is as previously.
- event information (Fig. 4.)
- fastest laps (Fig. 5.) - during quali additional information about the quali period in which the time was set is printed
- speed records (Fig. 5.)
- fastest pit stops (Fig. 5.)
Lap time charts are rather self-explanatory.
The dialog window with lap time comparison is non-modal, therefore you can open it and still have access to the main application window. You can open up to 30 windows with the tool, that gives you a wide range of possible driver comparison combinations. This is more advanced version of the lap time comparison tool. It allows you to track two drivers - on every lap program calculates the gap between them and shows the differences between lap and sector times. The better times are printed in green. If SC is on track lap and sector times are printed in yellow. The gap is always calculated as a gap of Driver 1 (in Fig. 8. it is Vettel) to Driver 2 (Raikkonen). Since Vettel was always in front the gap is negative. As in lap time comparison tool, data can be selected and copied to clipboard (Ctrl-C). There are three charts in this tool (Fig. 9.) - lap time and position charts are rather self-explanatory. In the gap chart, the driver that is in front is always printed in 0. If Raikkonen would pass Vettel, his chart would be printed in 0 then, while the Vettels one - according to the gap he would have to Raikkonen. Similar to lap time comparison tool, this dialog window is also non-modal and allows you to open max. 30 windows. F1LT allows you to record current session, save to file and play it later. This can be very usefull when you miss a session and want to watch its replay. Saved files are very small - race files takes from 1 to 2 MB of disk space (free practice and quali sessions even less) and therefore can be easy shared on internet. To start recording the session you only need to choose the right option from the menu, or click the red button on toolbar. You can also set an auto-record option in the preferences - in this case recording will start automatically when the session starts. To stop recording you need to press the "Stop" button on toolbar. This automatically saves the recorded file onto the disk, in the ltdata folder. File names are determined using the following template:
year-GPno-name-session.lt
, e.g: 2012-04-bah-race.lt
Session can be
race
, quali
or fpX
, where X
is the free practice number. Actually program doesn't know what is the current free practice number, it saves the subsequent practice sessions as fp1, fp2 and fp3. If you miss free practice 2 for example, free practice 3 will be saved as fp2, etc.
Saved live timing sessions can be opened and played - just click the "open" button on toolbar (first from left), select the appropriate file and application will change its state into the "player state". In this state the application is not connected to the LT server, it doesn't even need the internet connection. When you open a .lt file, you will notice the apperance of player controls on the toolbar (Fig. 10.). These controls replace the "Record" and "Stop" buttons, as recording is not active during session playing. Live timing player can be controlled using these buttons:
- playing speed - from x0.5 to x8
- skip to begin
- rewind by 10 seconds
- play/pause
- stop
- fast forward by 10 seconds
- skip to end
To stop playing and go back to the standard program mode click "Stop" button or "Connect" - both of these will stop playback and reconnect to the LT server.
All races from 2012 season are included in the application archive file. I have also many races from 2010 and 2011 - they are avaialble here.
You can also set .lt files to be always opened using F1LT - double click on any of the .lt files and choose the right path to the application. After this, every time you double click on a .lt file F1LT application will be launched. Clicking "Preferences" button will open preferences dialog. Here you can choose font which the data is displayed in and a font for the commentary tab. There are also settings for reversing the laps order in lap history, lap time comparison and head to head tools, session auto-recording and alternating row colors in the LT window. This program is still under development and therefore contains many errors. The known issues are:
- sometimes application won't connect to the LT server - restart it,
- when application is launched more than 5 minutes before start of the session, it prints no data and can have problems with connecting to the server,
- data sent by the LT server is encrypted and sometimes the decryption algorithm fails,
- LT server often sends junk data, this could lead to append wrong data in the lap history.
If you have any questions or requests, please contact with me.