AutoMovie API
    Preparing search index...

    Variable applyLightMotionConst

    applyLightMotion: (
        lights: readonly IAutoMovieLight[],
        clips: readonly IAutoMovieClip[],
        seconds: number,
        resolve: (light: string) => THREE.Light | undefined,
    ) => void = ...

    Drive scene lights from a shot's lightMotions: evaluate the clips at seconds through the engine's resolveShotLighting and write each resolved light onto the THREE.Light that resolve returns for its id.

    The render side of #1348, and the reason the axis is not a false green: the engine decides what the light IS at an instant and this writes it, so a candle blown out at 1.6s dims in the viewer at 1.6s instead of holding its staged glow for the whole film.

    Lights are resolved by id and never by position. buildScene adds them as top-level children and the segmentation mask palette is keyed by top-level child index, so an index-addressed light would silently re-target whenever staging inserts one; IAutoMovieSceneObject.lights is the id index built for exactly this call.

    Every staged light is written, not only the ones a clip addresses, which is the deliberate difference from applyObjectMotion. That helper owns no rest poses, so it must leave an unaddressed channel alone; a light carries its rest on the scene, so writing all of them makes the viewer's lighting a pure function of scene, clips and time. A host swapping clips mid-scene gets the staged light back instead of whatever the previous frame left behind.

    A light the host cannot resolve is skipped: the engine has already refused a clip addressing a light the scene does not stage, so the only way to arrive here unresolved is a host that built a subset of the scene.

    Type Declaration

      • (
            lights: readonly IAutoMovieLight[],
            clips: readonly IAutoMovieClip[],
            seconds: number,
            resolve: (light: string) => THREE.Light | undefined,
        ): void
      • Parameters

        Returns void