Fixed in v0.14.0 (PR #14, merge commit 7db8fcc, tag v0.14.0):
Time-scale slider values are now 1, 2, 5, 10, 25, 50, 100, 250, 500, 1000 (lib/timeScale.ts ladder; off-ladder legacy values display at the nearest step)
Server-side MAX_TIME_SCALE raised 64 → 1000 with matching OpenAPI bounds and validation messages
All e2e specs now run at SCALE = 1000 (fastest time), which shortens the suite; the mid-flight map test moved to a ~1420 km leg so the flight window stays observable at 1000×, and its marker click pauses the sim briefly (rendered marker lags fresh state by up to one poll at that speed)
Fixed in **v0.14.0** (PR #14, merge commit `7db8fcc`, tag v0.14.0):
- Time-scale slider values are now **1, 2, 5, 10, 25, 50, 100, 250, 500, 1000** (`lib/timeScale.ts` ladder; off-ladder legacy values display at the nearest step)
- Server-side `MAX_TIME_SCALE` raised 64 → 1000 with matching OpenAPI bounds and validation messages
- All e2e specs now run at **SCALE = 1000** (fastest time), which shortens the suite; the mid-flight map test moved to a ~1420 km leg so the flight window stays observable at 1000×, and its marker click pauses the sim briefly (rendered marker lags fresh state by up to one poll at that speed)
Deployed to https://flight.dev.kkhost.pl (`/api/version` → 0.14.0).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Change slider to have values:
1, 2, 5, 10, 25, 50, 100, 250, 500, 1000
update tests so they can use fastest times
Fixed in v0.14.0 (PR #14, merge commit
7db8fcc, tag v0.14.0):lib/timeScale.tsladder; off-ladder legacy values display at the nearest step)MAX_TIME_SCALEraised 64 → 1000 with matching OpenAPI bounds and validation messagesDeployed to https://flight.dev.kkhost.pl (
/api/version→ 0.14.0).