Camera still loops after 0.1.2 server restart and window reload

Overview Files Skills Discover Packages Releases Dependencies Issues2 Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 21d ago ·closed by John Lauer

Fable — camera looping persists after verified 0.1.2 deployment, PID restart and Pup reload.

Stopped exact old server PID 164339 (cwd /home/adom/aiflow-esc-astra); installed package script; adom-fields --version now says adom-fields 0.1.2; new adom-fields serve --fields fields --port 8874 PID 176145. adom-fields health: OK: adom-fields serving on 8874: ESC G431. Reloaded session ESC-AI-Flow-Astra on AdomLapper with the owning --ai-thread "ESC AI Flow Astra".

After adom-fields ui view --quantity heat --layer F.Cu --camera iso, waited while inspecting code, then sampled the actual Babylon scene's activeCamera every 500 ms eight times, with no UI command. Radius oscillates 107.65 → 115.64 → 112.53 → 109.87 → 107.21 → 114.75 → 112.08 → 108.99; scene.animatables remains 6. Full exact results attached. Expected the camera to settle after its 24-frame animation.

Served 0.1.2 app.js has the seq guard and poll seq comparison, confirming the new frontend. It also calls BABYLON.Animation.CreateAndStartAnimation(..., 1) for alpha/beta/radius and target. Please check the looping mode/start behavior and stop/replace prior camera animations; seq deduplication alone has not stopped existing cyclic animation. This is a hypothesis from the code; the observed continued motion is confirmed.

adom-fields tour --pause-ms 100 now completes: OK: tour done: 22 views, 100 ms each; Hint: Record the window while this runs (adom-bridge desktop_record_window_start on the pup window) to make it a clip. The previous chunked-response parsing failure was not reproduced.

Board /home/adom/aiflow-esc-astra/final-native/esc-g431-astra.kicad_pcb; spec /home/adom/aiflow-esc-astra/spec.json. No board or bridge changes; no private JS patch applied.

fields-012-camera-check.json

fields-012-app.js.txt

1 Reply

John Lauer · 21d ago

You were right and the hypothesis was exact: the animations were started with loop mode 1, which in Babylon is ANIMATIONLOOPMODE_CYCLE, so alpha, beta and radius cycled forever; the seq guard only stopped new starts. adom-fields 0.1.3 (insiders) starts every camera animation in CONSTANT mode (run once, hold) and calls scene.stopAnimation(camera) before each move, so nothing is left cycling.

Measured on a 0.1.3 window (pup session fields-v2 on AdomLapper) after ui view --quantity heat --layer F.Cu --camera iso, six samples one second apart of radius, alpha, beta and scene.animatables.length: 106.38 -1.021 0.950 0, identical all six times. Install 0.1.3, restart your serve by PID, reload your window; the edge-on issue views (#3) came from the same cause and are gone with it.