You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Data hub for stewards to watch live sessions they are in
Live incident feed with incident dossier with telemetry data on the incident that took place
Replay the incident during a live event
See the drivers involved within the incident
Take action against a driver for an incident, for example, 5s penalty, or flag it to review at a later time
Live track map of the session
Live "Pressure Monitor" that shows you close battles between same class cars or when a traffic incident is about to occur
Pin a battle in your Pressure Monitor to be able to focus on the drivers during the session and toggle between each driver
Full Camera control with replay capability such as fast forward, rewind - 0.5x, 1.0x, 2.0x speeds, camera angles, and rejoin live session
Full session time grid that shows each drivers current position, fastest lap time, fastest sector times, last lap time, on track status (garage, pit, on track), and interval to the car ahead.
Live sessions will automatically switch when the session switches from Practice -> Qualifying -> Race and keep an independent recording of each session.
View all of your previous live sessions in the Capture view, where you will be able to link your live session with a replay found on your local machine
Link a live session to a replay and you will be able to see the data from the replay logs as well as the live session in one single view.
Stewards can also take post session action on the replay view and assign penalties or flag items as reviewed with no action
All stewards decisions and actions taken during a live session, as well as post session, will be exportable on the replay view in different formats so you can import them easily into your league management system.
Control your data and automatically purge captured data after a certain time period. This setting can be found in the User Settings
To use this feature you must turn on Experimental Features as well as the Live Session feature setting to enable this feature
Capture View
View all live capture sessions in a single view
LMU Steward analyzes existing capture data, replay logs, and replay files to provide a match rate to link capture data to replay
- I intentionally did not automatically link capture sessions to replay logs because LMU can take up to 5 minutes sometimes to generate replay log and vcr files after a live session has completed.
Manage capture data from this view for linking, unlinking, and deleting capture data when its no longer needed
Driver Dashboard
Driver dashboard shows you the same stats as LMU and much much more
LMU Steward analyzes all of the data points it has available and creates a driver report card
Some stats include
- Total sessions
- Total of laps raced, and laps led
- Total Distance driven
- Race results such as win and podium rate, average class finish
- Drivers Pace stats including gap to session best, qualifying consistency, and tracks where you're closest and furthest away from the pace
- and much more
Import / Export
Import and export replays allows you to share your replays with another user of LMU Steward
Export replays and all data captured during that replay, including live session data captured with LMU Steward
Import replays to view the replay on your machine, as well as the session data that was recorded during the session, including any live session data captured from LMU Steward
Export replay log data to share all the data collected from LMU replay log, as well as any live session data captured by LMU Steward, and any decisions made from a steward during the live or post session review
Export Types Available:
- CSV - spreadsheets
- Markdown - document
- JSON - used for a league database or custom league management software
- Copy Markdown to clipboard - Useful for copying and pasting formatted information in Discord
Quality of Life Improvements
Replay Archive
Users can now archive sessions or entire weekend from their list of replays
- Archived sessions do not delete any data from your machine, its just moves the item to an "Archived" view found on the replays view
Replay Banner
Users can now navigate out of a replay without the replay closing in LMU
A replay banner will appear within LMU Steward allowing the user to return back to the replay they navigated away from
If you close LMU Steward while a replay is active in LMU and reopen LMU you the replay banner will still be available for you to use to navigate back to where you left off
A new "Close Replay" button is now on the replay view and driver analysis view that allows you to close the replay in LMU and returns you back to the replay list page
Persistent Filters and Sorting
Users can now configure their filters and sorting on the replay list view to be persisted even after application shutdown
Users can turn this feature on by going into User Settings and turning on "Remember Filters and Sorting" under the "Session Replays" settings
Experimental Features
Users can now try out experimental features build into LMU Steward by going into "User Settings" and enabling "Enable Experimental Features" under the "Experimental Features" settings
Users will be able to see what features are considered experimental so they know what features they'll be trying out
Experimental features are features that have been fully tested with limited set of data and scenarios
Users are encouraged to provide feedback, report bugs, and suggest changes or enhancements to these features
Features flagged under experimental are anticipated to be merged into a production release at a later version once a larger data set has been tested and any major defects or gaps in features have been fully met
Current Experimental Features
Replay Import & Export
Live Stewarding
Performance Improvements
Made significant performance improvements to the replay syncing process
Improved API query response time
Improved render time of the UI
Bugfixes
Fixed issue where camera controls were cycling forward when pressing the "previous" button due to change in LMU camera API schema