Part of #6. OpenMW already has an over-the-shoulder camera in files/data/scripts/omw/camera/ (viewOverShoulder, autoSwitchShoulder, move360, previewIfStandStill, deferredPreviewRotation, slowViewChange, povAutoSwitch, head bobbing), all off by default. Make the modern behavior the default and fill the gaps.
Scope
Turn on by default: viewOverShoulder, autoSwitchShoulder, previewIfStandStill, deferredPreviewRotation, move360, slowViewChange, and [Game] smooth movement. Keep each individually switchable in the settings menu.
Add: camera collision that eases back out instead of snapping (smoothing on distance recovery), and an aim mode that tightens the shoulder offset and FOV slightly while a ranged weapon or spell is readied.
Combat lock-on is out of scope here (consider a follow-up).
Acceptance
New settings documented; defaults changed only in game-neutral Lua/settings files.
Any pure math (collision distance easing, aim blend) unit tested or covered by a Lua test.
Headless boot screenshot shows the third-person over-the-shoulder view when the scenario switches to third person.
How the camera feels needs Eric's playtest.
Part of #6. OpenMW already has an over-the-shoulder camera in `files/data/scripts/omw/camera/` (`viewOverShoulder`, `autoSwitchShoulder`, `move360`, `previewIfStandStill`, `deferredPreviewRotation`, `slowViewChange`, `povAutoSwitch`, head bobbing), all off by default. Make the modern behavior the default and fill the gaps.
**Scope**
- Turn on by default: `viewOverShoulder`, `autoSwitchShoulder`, `previewIfStandStill`, `deferredPreviewRotation`, `move360`, `slowViewChange`, and `[Game] smooth movement`. Keep each individually switchable in the settings menu.
- Add: camera collision that eases back out instead of snapping (smoothing on distance recovery), and an aim mode that tightens the shoulder offset and FOV slightly while a ranged weapon or spell is readied.
- Combat lock-on is out of scope here (consider a follow-up).
**Acceptance**
- New settings documented; defaults changed only in game-neutral Lua/settings files.
- Any pure math (collision distance easing, aim blend) unit tested or covered by a Lua test.
- Headless boot screenshot shows the third-person over-the-shoulder view when the scenario switches to third person.
- How the camera feels needs Eric's playtest.
claude
added this to the 2. Feel milestone 2026-11-14 20:44:54 +00:00
Progress 2026-11-16 (early run): the implementation is written but not built or tested yet. Available memory on the host stayed between 2 and 2.9 GB for over 15 minutes, under the 4 GB this task needs to build, so this run did planning only. The changes are left uncommitted in the working tree at ~/Desktop/ashlar for the next run to build, test and commit.
What's in the tree:
Defaults on: viewOverShoulder, autoSwitchShoulder, previewIfStandStill, deferredPreviewRotation, move360, slowViewChange (camera/settings.lua), and [Game] smooth movement (settings-default.cfg, game.rst).
Collision ease-out (collisionEaseOut, collisionEaseOutTime 0.15 s half-life): moving in stays immediate; moving back out eases with a 60 units/s minimum speed. Off gives upstream's constant-rate recovery.
Aim mode (aimMode, aimDistance 0.7, aimFieldOfView 0.9): with a bow, crossbow, thrown weapon or spell readied in third person, the view stays over the shoulder instead of centring, moves closer and narrows the FOV. The FOV is only touched while the blend is above zero. Camera interface v2 adds getAimWeight, isAimModeEnabled, disableAimMode, enableAimMode.
Pure math in the new camera/ease.lua, with unit tests in apps/components_tests/lua/testcameraease.cpp.
New SCENARIO=camera (shoulder, wall, clear, aim, unaim phases) with scripts/ashlar_camera_summary.py PASS/FAIL checks; docs in docs/ashlar/CAMERA.md and SCENARIOS.md.
Next run: build, run both test suites and SCENARIO=camera, check the screenshot, then commit. How the camera feels still needs Eric's playtest.
Progress 2026-11-16 (early run): the implementation is written but **not built or tested yet**. Available memory on the host stayed between 2 and 2.9 GB for over 15 minutes, under the 4 GB this task needs to build, so this run did planning only. The changes are left uncommitted in the working tree at `~/Desktop/ashlar` for the next run to build, test and commit.
What's in the tree:
- Defaults on: `viewOverShoulder`, `autoSwitchShoulder`, `previewIfStandStill`, `deferredPreviewRotation`, `move360`, `slowViewChange` (`camera/settings.lua`), and `[Game] smooth movement` (`settings-default.cfg`, `game.rst`).
- Collision ease-out (`collisionEaseOut`, `collisionEaseOutTime` 0.15 s half-life): moving in stays immediate; moving back out eases with a 60 units/s minimum speed. Off gives upstream's constant-rate recovery.
- Aim mode (`aimMode`, `aimDistance` 0.7, `aimFieldOfView` 0.9): with a bow, crossbow, thrown weapon or spell readied in third person, the view stays over the shoulder instead of centring, moves closer and narrows the FOV. The FOV is only touched while the blend is above zero. Camera interface v2 adds `getAimWeight`, `isAimModeEnabled`, `disableAimMode`, `enableAimMode`.
- Pure math in the new `camera/ease.lua`, with unit tests in `apps/components_tests/lua/testcameraease.cpp`.
- New `SCENARIO=camera` (shoulder, wall, clear, aim, unaim phases) with `scripts/ashlar_camera_summary.py` PASS/FAIL checks; docs in `docs/ashlar/CAMERA.md` and `SCENARIOS.md`.
Next run: build, run both test suites and `SCENARIO=camera`, check the screenshot, then commit. How the camera feels still needs Eric's playtest.
Done in 53e3d92496 (the tree described in the comment above, built and tested).
Tests
Build OK. components-tests 1644 passed (8 new LuaCameraEaseTest), openmw-tests 637 passed.
SCENARIO=camera, 3 runs, 5/5 checks each time: shoulder offset 30 with standing preview; a wall 100 units behind pulls the camera from 192 to 95 at once; it eases back out to 192 in 44 to 46 frames (0.63 to 0.64 s), the largest step about 6.5 units and the last 0.1 to 0.6; aim weight reaches 1.0 with the FOV at 0.90 of base, the shoulder offset kept and the target distance at 134.4 (0.7 x 192); after the bow is put away, weight 0 and the FOV back at base.
The default boot is clean, and the screenshot shows the over-the-shoulder view.
Two problems found along the way
The first scenario run failed 4 of 5 checks because the reused run profile had a player_storage.bin holding the old false values. docker/ashlar-run.sh now deletes the stored Lua settings before each run. The same applies to real players: a profile that ran before this change keeps its old camera settings. That's noted in docs/ashlar/CAMERA.md.
The wall mesh intermittently failed to load. That was an engine COLLADA bug, opened and fixed as #35 (76d1796e6c).
Still needed: Eric's playtest of how it feels: the shoulder offset, ease-out speed, aim distance and FOV, and whether the standing preview should stay on by default.
Done in `53e3d92496` (the tree described in the comment above, built and tested).
**Tests**
- Build OK. components-tests 1644 passed (8 new `LuaCameraEaseTest`), openmw-tests 637 passed.
- `SCENARIO=camera`, 3 runs, 5/5 checks each time: shoulder offset 30 with standing preview; a wall 100 units behind pulls the camera from 192 to 95 at once; it eases back out to 192 in 44 to 46 frames (0.63 to 0.64 s), the largest step about 6.5 units and the last 0.1 to 0.6; aim weight reaches 1.0 with the FOV at 0.90 of base, the shoulder offset kept and the target distance at 134.4 (0.7 x 192); after the bow is put away, weight 0 and the FOV back at base.
- The default boot is clean, and the screenshot shows the over-the-shoulder view.
**Two problems found along the way**
- The first scenario run failed 4 of 5 checks because the reused run profile had a `player_storage.bin` holding the old `false` values. `docker/ashlar-run.sh` now deletes the stored Lua settings before each run. The same applies to real players: a profile that ran before this change keeps its old camera settings. That's noted in `docs/ashlar/CAMERA.md`.
- The wall mesh intermittently failed to load. That was an engine COLLADA bug, opened and fixed as #35 (`76d1796e6c`).
**Still needed:** Eric's playtest of how it feels: the shoulder offset, ease-out speed, aim distance and FOV, and whether the standing preview should stay on by default.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #6. OpenMW already has an over-the-shoulder camera in
files/data/scripts/omw/camera/(viewOverShoulder,autoSwitchShoulder,move360,previewIfStandStill,deferredPreviewRotation,slowViewChange,povAutoSwitch, head bobbing), all off by default. Make the modern behavior the default and fill the gaps.Scope
viewOverShoulder,autoSwitchShoulder,previewIfStandStill,deferredPreviewRotation,move360,slowViewChange, and[Game] smooth movement. Keep each individually switchable in the settings menu.Acceptance
Progress 2026-11-16 (early run): the implementation is written but not built or tested yet. Available memory on the host stayed between 2 and 2.9 GB for over 15 minutes, under the 4 GB this task needs to build, so this run did planning only. The changes are left uncommitted in the working tree at
~/Desktop/ashlarfor the next run to build, test and commit.What's in the tree:
viewOverShoulder,autoSwitchShoulder,previewIfStandStill,deferredPreviewRotation,move360,slowViewChange(camera/settings.lua), and[Game] smooth movement(settings-default.cfg,game.rst).collisionEaseOut,collisionEaseOutTime0.15 s half-life): moving in stays immediate; moving back out eases with a 60 units/s minimum speed. Off gives upstream's constant-rate recovery.aimMode,aimDistance0.7,aimFieldOfView0.9): with a bow, crossbow, thrown weapon or spell readied in third person, the view stays over the shoulder instead of centring, moves closer and narrows the FOV. The FOV is only touched while the blend is above zero. Camera interface v2 addsgetAimWeight,isAimModeEnabled,disableAimMode,enableAimMode.camera/ease.lua, with unit tests inapps/components_tests/lua/testcameraease.cpp.SCENARIO=camera(shoulder, wall, clear, aim, unaim phases) withscripts/ashlar_camera_summary.pyPASS/FAIL checks; docs indocs/ashlar/CAMERA.mdandSCENARIOS.md.Next run: build, run both test suites and
SCENARIO=camera, check the screenshot, then commit. How the camera feels still needs Eric's playtest.Done in
53e3d92496(the tree described in the comment above, built and tested).Tests
LuaCameraEaseTest), openmw-tests 637 passed.SCENARIO=camera, 3 runs, 5/5 checks each time: shoulder offset 30 with standing preview; a wall 100 units behind pulls the camera from 192 to 95 at once; it eases back out to 192 in 44 to 46 frames (0.63 to 0.64 s), the largest step about 6.5 units and the last 0.1 to 0.6; aim weight reaches 1.0 with the FOV at 0.90 of base, the shoulder offset kept and the target distance at 134.4 (0.7 x 192); after the bow is put away, weight 0 and the FOV back at base.Two problems found along the way
player_storage.binholding the oldfalsevalues.docker/ashlar-run.shnow deletes the stored Lua settings before each run. The same applies to real players: a profile that ran before this change keeps its old camera settings. That's noted indocs/ashlar/CAMERA.md.76d1796e6c).Still needed: Eric's playtest of how it feels: the shoulder offset, ease-out speed, aim distance and FOV, and whether the standing preview should stay on by default.