AutoMovie API
    Preparing search index...

    Variable buildLightConst

    buildLight: (light: IAutoMovieLight) => THREE.Light = ...

    Build the three.js light one staged light plays on, aimed the way the artifact says. The kind decides the class; every value INCLUDING the placement is written by applyLightState, the same call a shot's lightMotions uses each frame, so placing a light and animating it cannot map range, coneAngle or the transform two different ways; the two aimed kinds then get their target (aimLight), which is the half of a light's placement three.js does not read off a quaternion.

    The placement is deliberately NOT applied a second time here. It used to be, back when applyLightState wrote everything except the transform; now that one writer owns the whole light, repeating the call would be a second statement of the same fact, and the kind of duplicate that survives right up until the two copies disagree.

    Exported because a host that assembles its own scene graph (a production's film page) must light it from scene.lights rather than from a hardcoded source of its own: a page that lights itself proves nothing about the film's lighting, which is how the aim defect in #1356 survived every capture.

    Type Declaration