- Shoulder view, auto shoulder switch, standing preview, deferred preview
rotation, move 360, smooth view change and [Game] smooth movement are
on by default.
- Collision ease-out: the camera still snaps in on collision but eases
back out (0.15 s half-life, 60 u/s minimum speed).
- Aim mode: with a ranged weapon or a spell readied in third person the
view stays over the shoulder, moves closer and narrows the FOV. Camera
interface v2 adds getAimWeight and enable/disable functions.
- Pure math in camera/ease.lua with unit tests; SCENARIO=camera with
PASS/FAIL checks; docs in docs/ashlar/CAMERA.md.
- ashlar-run.sh deletes stored Lua settings before each run so changed
defaults are tested.
Closes#29
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New [Game] mantling setting, on by default, with mantle max height (1.1
times the actor's height above its feet) and mantle duration (0.4 s).
When the player jumps or falls into a wall while moving towards it
(within 60 degrees), the movement solver casts the player's collision
shape up, across the edge and down. If it finds a surface flat enough to
stand on, above the feet and within reach, with headroom and room on top,
the player moves up, across and onto it along that checked path. Movement
and jump input are ignored meanwhile, and the climb ends any fall without
fall damage. No animation is needed. A script move or teleport, noclip or
paralysis cancels a climb.
Lua: self.controls.mantle (true by default) vetoes climbs while false,
and the actor's scripts get an AshlarMantle event with the ledge height
when one starts. The engine logs "Ashlar mantle:" lines at verbose level.
Player only; with the setting off nothing changes.
The geometry rules (reach, headroom, room on top, slope, too high, too
low) and the climb path are in mwphysics/mantle.cpp, apart from the
physics calls, with unit tests. The new mantle scenario uses a CC0 box
mesh written for it: the player climbs an 80 unit ledge, doesn't climb it
with the Lua veto, and doesn't climb a 240 unit wall.
Closes#28
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New [Game] sprint setting, on by default, with sprint speed multiplier
(1.4 times run speed), sprint fatigue drain (10 per second on top of
running, halved at Athletics 100) and sprint fatigue threshold (0.1 of
maximum fatigue to start). A sprint ends when fatigue falls below 1% of
maximum; regeneration keeps fatigue just above 0 while running, so
exactly 0 is never reached.
Sprint is engine action 52, Lua input.ACTION.Sprint and the player's
'Sprint' Lua action, with self.controls.sprint. Defaults are Left Alt
and D-pad up, because L3 is already Sneak. Sprinting needs forward
movement within 45 degrees, and isn't possible while sneaking, in the
block stance, swimming, levitating, knocked down or paralyzed. Pressing
Use with a weapon or spell ready ends the sprint until Sprint is
released, so no attack starts while sprinting. A sprint counts as
running for animations, Athletics and the running fatigue cost. AI
doesn't sprint. With the setting off the control does nothing.
The rules are in mwmechanics/sprint.cpp with unit tests. The movement
scenario gains sprint, tiredsprint and sprintuse phases, run in a
circle from the start point so the player stays on land.
Closes#27
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New [Game] movement acceleration setting, on by default, with
movement acceleration time (0.15 s), movement deceleration time (0.1 s)
and movement air control (0.3). Movement ramps towards the requested
movement in the actor's own frame, so turning is never delayed.
Reversing slows down through zero before speeding up the other way,
and sideways movement left over from a direction change dies away at
the deceleration rate. NPCs and creatures stop at once so they never
overshoot a path point. With the setting off, behavior is unchanged.
The ramp is in mwmechanics/movementramp.cpp with unit tests, including
frame-rate independence from 1/30 to 1/240 s. A new headless
SCENARIO=movement logs the player's speed as it starts, stops and
reverses.
Refs #26
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The headless duel now drops the player's shield and holds Block to parry
with the blade, has the duelist set ignoreStagger on hits it takes for a
window, then holds the player's fatigue below the attack fatigue
threshold and below the attack fatigue cap.
The engine logs refused attacks (once per press, any actor) and capped
attack strength at verbose level as "Ashlar stamina:" lines, and
docker/ashlar-run.sh counts parries, refused and capped attacks, and the
duelist's flinches inside the ignoreStagger window. The scenario's
default run time is now 150 s.
Closes#25
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With [Game] real time combat and the new [Game] hit reactions setting on
(default), melee hits cause short reactions:
- A connecting hit queues a flinch of 0.2 to 0.7 s, growing with damage
up to a quarter of max health and halved at zero attack strength. It
starts when the hit's stagger is applied, so Lua's ignoreStagger and
god mode prevent it.
- A blocked hit or parry makes the blocker recoil for 0.1 to 0.25 s, and
a blocked blow at 0.75 strength or more staggers the attacker for 0.25
to 0.6 s.
- During any reaction, an attack wind-up is interrupted and no new attack
starts. Hit animations still play where the content has them; the
timer works without them, as on the Game Template.
The rules are in mwmechanics/hitreaction.cpp. The shield block and parry
resolution moves into resolveMeleeBlock, shared by NPCs and creatures.
The combat scenario now counts reactions. Also moves a stray line of the
ai active blocking docs back under that setting.
Closes#22
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SCENARIO=combat docker/ashlar-run.sh loads docker/scenarios/combat on top
of the Game Template: our own CC0 Lua content that gives the player a
shield and blade and spawns a hostile duelist with the same kit, cloned
from the template's player record. The player holds Block, then attacks,
and the run prints block counts. The default boot is unchanged.
The engine now logs each successful shield block or parry at verbose
level ("Ashlar block: ..."), so runs can count them.
Documented in docs/ashlar/SCENARIOS.md.
Closes#24
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docker/ashlar-bench.sh boots the Game Template with fixed video settings,
records OpenMW's per-frame profiler trace, and summarizes it with a new
stdlib-only script. By default it renders on the NVIDIA GPU through EGL and
SDL's offscreen driver, so no window opens. docs/ashlar/BENCHMARK.md holds the
method and the first RTX 5060 Ti baseline.
Closes#3
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Set MORROWIND_DATA to a Data Files folder to play it, mounted read-only,
with its own settings and saves.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is a combination of 4 commits.
Initial attempt at compose file for local generic builds
Maybe activate GCC better
Improved compose.yaml is improved
Ensure container gets rebuilt if stale