mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-15 19:19:58 -04:00
The game's movie player adds the time manager's step to an accumulator at each update and advances the movie by whole pictures of it, at most the player's limit per update, which is one for the Triforce movie. While a movie plays the game is held at 60 updates a second, but every late frame cost an update, the pacer started its slots again from the late one, and the steady step's payback of the lost time came as steps over one frame, which the player cannot turn into more than one picture. So each late frame put the picture further behind the sound, which plays by the clock, and it never caught up. While a movie plays the step is now exactly one movie frame, and the pacer keeps the movie's slots through a lateness of up to a second, presenting the frames after a late one at once until the game is back on them. The updates then average the movie's rate, and the picture, the event's update count and the game's clock all stay with the sound. movie_clock = 0 gives the earlier behaviour. The movie log now measures the picture on screen against real time where the game releases it (the game fetches pictures ahead into a list of its own) and reports it at the end of each movie. test_hitch = <every>:<ms> makes a frame that much late every so many presents, for test runs. Measured on the Triforce movie (event Dm_Kokiri_0095, 7,040 pictures, 117 s), one exe with movie_clock = 0 against 1, and a 70 ms late frame every two seconds (test_hitch = 120:70), as a run with natural hitches had shown a drift of 40 ms every ten seconds. Drift of the picture on screen behind real time, from the movie's first 10 s to its end: fps_limit before (updates/s, drift at the end) after (updates/s, drift over the movie) unlimited 58.86, 2,187 ms behind 60.22, flat at 53 to 55 ms 144 58.86, 2,196 ms behind 60.04, flat at -11 to -15 ms 120 58.98, 2,257 ms behind 60.20, flat at -1 to 0 ms 60 58.88, 2,220 ms behind 59.98, flat at -21 to -22 ms Without the late frames both kept time (unlimited: before flat at 21 ms, after flat at -13 ms). The selftest, --probe-cfg, --probe-kernel, --probe-movie and tests/frame_step_check.py pass; the check now plays a movie started at 240 fps with late and short frames and needs exactly one frame every update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>