diff --git a/docs/DEVLOG.md b/docs/DEVLOG.md index 13f337abac..8740233332 100644 --- a/docs/DEVLOG.md +++ b/docs/DEVLOG.md @@ -3,6 +3,42 @@ Newest entries first. The `ashlar-build` scheduled task and interactive sessions both append here. +## 2026-11-15 (afternoon run) + +- Got the lock right away. Host memory had about 4 GB available at the + start and 2 GB during the build; the default JOBS=3 MEMORY=6g build (about + 250 steps after header changes) finished without trouble. +- #28 ledge mantling, `9e28969629`. New `[Game] mantling` (on), `mantle max + height` 1.1 and `mantle duration` 0.4 s. Jumping or falling into a wall + while moving towards it (within 60 degrees) makes the movement solver cast + the player's shape up, across the edge and down. A walkable surface above + the feet, within reach and with headroom gets climbed along that checked + path, with no animation needed and no fall damage. Lua: + `self.controls.mantle` (false vetoes) and the `AshlarMantle` local event. + The rules are in `mwphysics/mantle.cpp`; the casts are `tryMantle` in + `movementsolver.cpp`. +- Decisions: the climb state lives on `MWPhysics::Actor` (not saved) and + moves through `ActorFrameData`, so the climb steps at the physics rate. Who + may start a climb (setting, player, Lua veto, not knocked down or + recovering) is decided on the main thread in `prepareSimulation`, so no + settings are read on physics threads. Logging and the Lua event happen + there too, on the frame after the sync. The climb crosses just above the + ledge if a second cast shows that is clear, or at the top of the probe if + not. A move of over 30 units off the path (scripts, teleports) cancels + the climb. +- Lesson: the Game Template has no box or wall mesh. A hand-written COLLADA + box (`docker/scenarios/mantle/meshes/ashlar_ledge.dae`, CC0) works: it + renders, gets collision from its triangles, and `setScale` makes it a + taller wall. +- New `SCENARIO=mantle`: 1 climb (46.4 up from mid-jump) ending 81 units up + on the 80-unit ledge, 0 with the Lua veto, and 0 at a 240-unit wall. The + highest plain jump was 37.5. +- Tests: build OK, components-tests 1636 passed, openmw-tests 637 passed (18 + new). The default boot is clean. +- Feel (reach, duration, and whether Jump should be needed) needs Eric's + playtest. +- Next: #29 third-person camera defaults and polish, then #30. + ## 2026-11-15 - Got the lock right away. Host memory was 3 to 5 GB available; builds ran diff --git a/docs/ashlar/SCENARIOS.md b/docs/ashlar/SCENARIOS.md index 31fbbae53b..d16836d3f9 100644 --- a/docs/ashlar/SCENARIOS.md +++ b/docs/ashlar/SCENARIOS.md @@ -158,10 +158,10 @@ The engine logs each climb at verbose level, and the player script logs the `Ash phase: ``` -Ashlar mantle: "player" climbs 61.3 onto a ledge -Ashlar mantle: "player" finished at -ASHLAR_MANTLE event mantle height=61.3 -ASHLAR_MANTLE result mantle events=1 peak=81.0 dz=81.0 +Ashlar mantle: "Player" climbs 46.3628 onto a ledge +Ashlar mantle: "Player" finished at +ASHLAR_MANTLE event mantle height=46.4 +ASHLAR_MANTLE result mantle events=1 peak=85.0 dz=81.0 ``` `dz` is the player's height above the start at the end of the phase, and `peak` the highest it got. The climb