Note #29 and #35 in the devlog

Refs #29, #35

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-16 15:45:35 -05:00
co-authored by Claude Opus 5.5
parent 53e3d92496
commit b97d7076da
+26
View File
@@ -3,6 +3,32 @@
Newest entries first. The `ashlar-build` scheduled task and interactive
sessions both append here.
## 2026-11-16 (afternoon run)
- Got the lock right away. Available memory was 3.9 GB at the start and
passed 4 GB within a minute; the default JOBS=3 MEMORY=6g build was fine.
- #29 third-person camera, `53e3d92496`: built and tested the tree left by
the early run. components-tests 1644 passed (8 new), openmw-tests 637
passed. `SCENARIO=camera` passed 5/5 in three runs. The wall pulls the
camera from 192 to 95 at once, it eases back out in about 0.64 s (44 to
46 frames), and aim mode reaches weight 1 with the FOV at 0.9 of base and
the target distance at 134.4. The default boot is clean.
- Lesson: `docker/ashlar-run.sh` reused `player_storage.bin` from earlier
runs, so the new Lua setting defaults never applied and 4 of 5 camera
checks failed. The script now deletes the stored Lua settings before
each run. Real profiles keep their old values too (noted in
`docs/ashlar/CAMERA.md`).
- #35 (bug, opened and closed this run), `76d1796e6c`: valid `.dae` files
intermittently failed with "Extra content at the end of the document",
including the Game Template's own player body. OSG's dae plugin seems to
hand collada-dom an unterminated buffer. `loadNonNif` now appends a NUL
to `.dae` input. That gave zero failures in four runs, against one or two
per run before. Earlier scenario screenshots with an error-marker player
were this bug.
- Feel of the camera (offset, ease-out, aim framing, standing preview)
needs Eric's playtest.
- Next: #30 first-person presence, then #31 to #34 (#7 animation).
## 2026-11-16 (early run)
- Got the lock right away. Available memory stayed at 2 to 2.9 GB for over