Write one IAutoMovieLight's value onto the three.js light that plays
it: its PLACEMENT for every kind, colour and intensity for every kind,
falloff distance for the two that have one, the cone half-angle (degrees on
the artifact, radians in three.js) for a spot, and the panel extent for an
area source.
The one place the mapping lives. buildLight calls it to place a staged
light and applyLightMotion calls it to move that same light over time,
so an animated light and a static one can never disagree about what range
or coneAngle means.
The transform is written HERE rather than once at build time, which is what
makes a light's direction animatable at all. buildLight used to place the
light itself and this helper wrote everything except its placement, so a
/lights/<id>/rotation track could resolve to a new orientation every frame
and the three.js light would keep the one it was staged with forever. Both
callers now go through one writer, so the rendered placement is the resolved
placement by construction; aimLight keeps the light's target as a
CHILD for exactly the same reason, so a turning light turns what it aims at
with it.
Writing an absolute TRS every frame is also what lets applyLightMotion keep
its promise that the viewer's lighting is a pure function of scene, clips and
time: a light nothing addresses is written back to where the scene staged it
rather than holding wherever the previous frame left it.
Write one IAutoMovieLight's value onto the
three.jslight that plays it: its PLACEMENT for every kind, colour and intensity for every kind, falloff distance for the two that have one, the cone half-angle (degrees on the artifact, radians inthree.js) for a spot, and the panel extent for an area source.The one place the mapping lives. buildLight calls it to place a staged light and applyLightMotion calls it to move that same light over time, so an animated light and a static one can never disagree about what
rangeorconeAnglemeans.The transform is written HERE rather than once at build time, which is what makes a light's direction animatable at all.
buildLightused to place the light itself and this helper wrote everything except its placement, so a/lights/<id>/rotationtrack could resolve to a new orientation every frame and thethree.jslight would keep the one it was staged with forever. Both callers now go through one writer, so the rendered placement is the resolved placement by construction; aimLight keeps the light's target as a CHILD for exactly the same reason, so a turning light turns what it aims at with it.Writing an absolute TRS every frame is also what lets
applyLightMotionkeep its promise that the viewer's lighting is a pure function of scene, clips and time: a light nothing addresses is written back to where the scene staged it rather than holding wherever the previous frame left it.