Entry 35

The viewer plays animations as the game steps them

2026-09-23rendertest

Filescrates/piney-viewer/src/mesh.rscrates/piney-viewer/src/main.rscrates/piney-viewer/src/render.rscrates/piney-data/src/scene.rs

With playback worked out (32), the viewer no longer stops at frame 0. The user had asked why --anime did nothing to Mac Anu's flags and ships.

• What moves. When the viewer builds a scene, each model posed by an animation remembers how:

  • a town object's instance remembers its one controller, under its row's root;
  • bone and skin models remember the whole clump the chosen Anime chunk poses.

  It also keeps the vertex spans each mmat wrote.

• How often. The viewer counts game frames at 29.97 a second (frameRate 2, as in towns and fields). On each new frame it poses only those spans again and sends only them to the GPU.

• How each animation runs. Each animation steps one frame (256 ticks) per game frame from 0. It loops or holds its last frame as its chunk says (Animation::looped). ExtObj copies stay separate instances, through a matrix form of Scene::controller_worlds.

• Controls. Space or P (Options on a pad) pauses. --time SECONDS poses a --shot.

Checked

town_objects_play builds Mac Anu and poses it at game frame 45. More than 100 vertices move, all stay finite, and posing frame 0 again restores every vertex exactly. Two shots of town01, 2 seconds apart, differ where the flags and boats are.