Public/Live_RC
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix staggered heat call-out order and extend its shared clock

Browse Source 
getEventDrivers followed the drivers directory's internal creation
order instead of the order participants were actually selected for
the event, so the fallback qualifying/finals grid, the Start List
display, and the staggered-release announcer all read out drivers in
a scrambled order relative to how the event was actually entered.
Fixed to preserve raceConfig.driverIds' own order.

Also, a staggered heat's shared clock/auto-finish target only ever
counted the flat session duration, not the staggered release schedule
itself - so the last-released driver's own personal window could
still be running when the session force-finished. The shared clock
now widens by (driverCount - 1) * staggerGapSec on top of the base
duration for staggered sessions; each driver's own personal quota is
unchanged.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
larssand
2026-09-10 21:59:23 +02:00
parent 1565baab2a
commit e356e30eda
7 changed files with 94 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
CHANGELOG.md
View File

@@ -8,6 +8,13 @@ The application version is maintained in `package.json` and displayed in the adm
No changes recorded yet.
## 1.14.1 - 2026-09-10
### Fixed
- A staggered heat's car call-outs (and its start list, and its fallback grid seeding before any practice has been run) followed the drivers directory's internal creation order instead of the order participants were actually selected for the event - so the announced order, and the start list shown in Race Day, could look scrambled relative to how the event was actually entered.
- A staggered heat's shared clock and auto-finish timer only ever counted a flat session duration (e.g. 5:00), not accounting for the staggered release schedule itself - so with several drivers being released a few seconds apart, the last-released driver's own personal window could still be running when the session force-finished. The shared clock now starts from duration + the full release schedule (e.g. 5:09 for 4 drivers 3 seconds apart) instead of just the flat duration, while each driver's own personal 5-minute quota is unchanged.
## 1.14.0 - 2026-09-10
### Added