Fix speed traps not showing during race sessions

Minor update this time:

• Speed traps now show correctly during race sessions, on the Session Stats timing page
• Config files are now read correctly, and are properly optional

Full Changelog: v1.0.124...v1.0.127

v1.0.124 Introduce single-file executables for all major platforms

As well as running via dotnet tool, we now are building more standalone executables for multiple platforms (osx-arm64, linux/arm64, linux/x64, win-x64) which are self contained and therefore don't require the dotnet SDK to be installed.

Full Changelog: v1.0.118...v1.0.124

v1.0.118 Remove unused driver tracker screen, improve readability

• Improve readability of speed traps on session stats page
• Reorder columns when showing drivers/teams championship tables on session stats page
• Colour the VSC session state of yellow to make it clear when that is deployed

Full Changelog: v1.0.114...v1.0.118

v1.0.114 Chequered Flag handling

• Highlight the current fastest driver on track during a race (i.e. fastest Last Lap). This allows you to track who is currently making big gains, even during changeable conditions (like Silverstone this year)
• When a driver crosses the chequered flag during quali/race sessions, their driver tag will be inverted to show as such

Full Changelog: v1.0.109...v1.0.114

v1.0.109 Back to old SignalR

Revert back to the old SignalR protocol, as the new signalrcore endpoint seems to be missing lots of data, like CarData.z and Position.z, among others.

Pull circuit information from F1 MultiViewer, so that the driver tracker display has a proper route to draw drivers position on.

Support importing timing data from the static F1 feed, via new CLI commands. The CLI in general has been improved, using System.CommandLine to give proper help text and command info. The TUI is now started without the Kestrel API server enabled, but this can be enabled with the --with-api switch when starting.

Other CLI switches include -v to enable verbose logging.

Log files are now also written to ~/open-f1/logs as well as the in-memory logger available inside the TUI to make troubleshooting easier.

Full Changelog: v1.0.87...v1.0.109

v1.0.87 SignalR Core Update

Updates to change the SignalR client to use the newer AspNetCore SignalR client, as it seems the F1 live timing endpoint has switched to this instead of the legacy ASP.NET SignalR client.

Almost everything still works after this change, apart from the CarData and PositionData feeds. For some reason, these feeds are not being sent to the client with the new feed, and I haven't figured out why this is.

The data recording format has changed with this new data stream, and the JsonTimingClient has been updated to be able to read both the new and old recording formats.

Known Issues:

• CarData and PositionData not populated
• Feature related to Car/Position Data such as the new DRS indicator on the timing screens not available

Full Changelog: v1.0.82...v1.0.87

v1.0.82

Improved timing pages with:

• a useful Team Radio screen with includes Whisper powered audio transcriptions! (Transcription requires Ffmpeg to be installed locally)
• Redesigned championship prediction page with actually useful information and explanations of the predictions

Full Changelog: v1.0.78...v1.0.82

v1.0.78

Minor fix to v1.0.77 to fix packaging issue.

v1.0.77 Release Notes:

Introduces a very basic SwiftUI timing screen, very much in progress.

The TUI is now hosts a basic API with Swagger support, to allow any app to read all timing data at will whilst a session is running (both live and simulated). This API is what the SwiftUI app uses to read data. The API is available at http://localhost:61937/swagger/index.html

Refactored the timing TUI to use pages instead of distinct timing data screens, and refactors some of the key binds.

Full Changelog: v1.0.49...v1.0.78

v1.0.77

Introduces a very basic SwiftUI timing screen, very much in progress.

The TUI is now hosts a basic API with Swagger support, to allow any app to read all timing data at will whilst a session is running (both live and simulated). This API is what the SwiftUI app uses to read data. The API is available at http://localhost:61937/swagger/index.html

Refactored the timing TUI to use pages instead of distinct timing data screens, and refactors some of the key binds.

Full Changelog: v1.0.49...v1.0.77

v1.0.49

Improvements to non-race timing towers, overall colours everywhere and information density on screens.

Full Changelog: v1.0.34...v1.0.49