HallMirrorLag.component
README.md
HallMirrorLag
The reflections are not keeping up. Attached to H_Mirrors, the group holding
the eight panes hung down the corridor's north wall, and the whole of shot 5.
Every pane is hung a little loose in its frame. This swings each one from where
the camera was about a third of a second ago rather than from where it is, so
the wall reflects the corridor late, and each pane eastward is a little later
than the one before it. One pane — slackIndex — is on a slack spring instead
of a delay line, so when the dolly stops that one is still travelling. The lock
at the end of shot 5 exists so that can be seen.
The panes are what moves. Nothing here touches the light, and nothing here
decides what a pane REFLECTS: that is the pane's hall_mirror material reading
the corridor's reflection probe, which demo.hall places and
M.bakeReflections() bakes.
What it carries
lag,lagStep— seconds the wall is behind, and the extra delay per pane.yawGain,yawLimit,slideGain,slideLimit— how a metre of camera travel becomes pane yaw and pane slide, and where each stops.slackIndex,slackStiff,slackDamp— which pane is on the spring, and what kind of spring.tremor— degrees of always-present shiver, so a locked shot is never still.glassZ— how far the pane stands proud of its frame. The frame boxes are built behind it; the two have to agree or the frame crops the reflection.
Who drives it
Nothing: it reads camera.active() itself and records a history of the camera's
x every tick. It has no methods and needs no schedule.
Cost
A 240-entry history ring and eight transform writes per tick. It guards both
hooks on engine.mode, because lag is measured in a dt-accumulated clock:
ticking twice a frame puts the wall 0.17 s behind rather than the authored 0.34
and records two history samples for one camera position.