erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions

fix #389: port retail's SmartboxFOV law; retire AD-89 (display slice 1)

Browse source 
Retail's world-camera FOV is not a constant: the applied vertical FOV is
m_fGameFOV / (viewportAspect - 0.1), recomputed on every aspect or
game-FOV change (CreatureMode smartbox sites 0x00452b2f/0x00453b14),
gated by Render::SetFOVRad's open (0, pi) acceptance (0x0054b2d0 -
rejected results keep the previous FOV). m_fGameFOV defaults to pi/2 =
90 degrees (0x00454649) and is what the Field of View option sets in
degrees (0x00451e6a; registered range [10,160] default 90 -
gmClient::InitUIPreferences @0x004035b0). Net effect: the horizontal
view stays ~85-90 degrees across aspect ratios; wide screens trim the
vertical slice instead of ballooning the sides.

acdream hardcoded FovY = pi/3 = 60 degrees on all four world cameras,
aspect-independent, and the Config slider wrote raw vertical-FOV
degrees. New: RetailFieldOfView (the law + gate, decomp-cited),
CameraController.GameFovRadians + SetGameFov + one ApplyProjection
chokepoint recomputing every camera on SetAspect/SetGameFov/
EnterChaseMode/RestoreState; ApplyFieldOfView now feeds the law;
DisplaySettings.Default.FieldOfView 60 -> 90 (the retail registered
default; the stored number changed MEANING with this commit).

The same seam closes a second latent bug the 2026-08-13 "squished" gate
report exposed: SetAspect only ever updated Orbit/Fly - the CHASE
cameras (the ones the player looks through) kept their creation-time
aspect across every mid-session resize, drawing the world at the old
shape stretched onto the new viewport.

The paperdoll camera stays outside the law by design (retail portrait
mode is UseSharpMode, not smartbox - DollCamera's own doc).

Tests: RetailFieldOfViewTests (golden law values at 4:3/16:9/21:9, the
constant-horizontal property, the rejection gate, controller propagation
incl. chase attach/restore + rejected-law aspect-still-propagates);
DisplaySettingsTests + RuntimeSettingsControllerTests updated to the new
semantics. App suite 4,953/3 skips; UI.Abstractions 916/0. AD-89 retired
in this commit; user settings.json migrated 60->90 by hand (stale
pre-port default).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-13 17:08:41 +02:00
parent a1efc8bcb3
commit 7e0c130344
13 changed files with 334 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

10
tests/AcDream.App.Tests/Settings/RuntimeSettingsControllerTests.cs
View file

@ -144,8 +144,14 @@ public sealed class RuntimeSettingsControllerTests
Assert.Equal(1, displayWindow.ApplyCount);
Assert.Equal(1, surface.RefreshReadCount);
Assert.Equal(new FramePacingPolicy(false, 144d), pacing.Policy);
Assert.Equal(83f * (MathF.PI / 180f), cameras.Orbit.FovY, precision: 5);
Assert.Equal(83f * (MathF.PI / 180f), cameras.Fly.FovY, precision: 5);
// #389: the stored degrees are retail's m_fGameFOV; the camera's
// applied vertical FOV comes through the smartbox law at the
// controller's current (default 16:9) aspect — never the raw degrees.
Assert.Equal(83f * (MathF.PI / 180f), cameras.GameFovRadians, precision: 5);
Assert.True(RetailFieldOfView.TryAppliedVerticalFov(
83f * (MathF.PI / 180f), 16f / 9f, out float expectedFov));
Assert.Equal(expectedFov, cameras.Orbit.FovY, precision: 5);
Assert.Equal(expectedFov, cameras.Fly.FovY, precision: 5);
}
[Fact]