orbital-engine
    Preparing search index...

    Variable MAX_HOURS_PER_SECONDConst

    MAX_HOURS_PER_SECOND: 6

    The fastest speed this engine's own 60fps camera math can still model with real detail — not an arbitrary round number, and not simply "as fast as the slider can turn": the fixed camera-route fixture (see routeCameraSimulator.ts) directly measured that a fast, close orbiter's flight path develops genuine, hard-to-smooth curvature spikes once playback speed lets it complete a meaningful fraction of its own orbit within a single rendered frame — denser sampling only helps so much, because at that point the aliasing is real geometry, not an artifact.

    Anchored to real solar-system bodies this engine actually includes (see solarSystemData.ts), at "the reference body takes at least 1 real second per orbit at 60fps" (60 frames/orbit — comfortably smooth): Phobos (fastest NATURAL moon modelled, ~7.65h period) would allow ~7.65 h/s; the ISS (the fastest body of any kind modelled — its own comment already calls it a deliberate stress-test, not a body meant to track like any other) would need ~1.55 h/s to stay equally smooth. 6 h/s splits the difference: comfortably smooth for real natural bodies down to Phobos's own period, while accepting that the ISS/ Hubble-altitude stress-test case still blurs at max speed, same as it already did before this cap existed.