Drive movie event timelines from the selected video picture timestamp

This commit is contained in:
automata.
2026-11-11 14:00:56 -05:00
committed by chrg6
parent 2571e180c8
commit feeb504bf4
4 changed files with 134 additions and 7 deletions

View File

@@ -193,13 +193,11 @@ static void frame_limit_live(void) {
else rt_log("frame rate: limit at the monitor's refresh rate (60 until the window measures it)");
}
// NX2NAVI_MOVIE_FPS (default 60; 0 = off): the game's frame rate while a movie plays (ov_movie2.c ov_movie_live). A
// movie's event counts the game's updates as 60 Hz frames whatever the step: at 144 fps the intro's narration lines
// started 2.4 times too early, each over the one before, and its closing fade to black came at 65 s of the movie's
// 154, hiding the whole dream. The movies are 60 fps, so the cap shows the same pictures. It is the rate in both
// directions: under a lower limit (40 fps, or 60 shown with frame generation, which is 30 of the game's) the movie ran
// at that fraction of its speed and ended many seconds behind its sound, so the game is paced at the movie's rate
// while one plays, above the limit too.
// NX2NAVI_MOVIE_FPS (default 60; 0 = off): the game's frame rate while a movie plays (ov_movie2.c ov_movie_live).
// Movie-synchronised events use the selected picture's timestamp with the 1.1.1 ostep patches enabled; redrawing
// a picture no longer advances that timeline. Keep the 60 Hz pacing policy for the 60 fps movies and for builds
// without those patches. It applies in both directions: a lower gameplay limit must not slow the movie's updates
// relative to its audio. A player can turn this pacing override off independently of the timestamp patches.
static int movie_cap_hz(void) {
static int hz = -1;
if (hz < 0) {