window.kaolin
    Preparing search index...

    Variable OrbitCameraControllerOptionsSchemaConst

    OrbitCameraControllerOptionsSchema: ZodObject<
        {
            up: ZodDefault<ZodArray<ZodNumber>>;
            enableDamping: ZodDefault<ZodBoolean>;
            dampingFactor: ZodDefault<ZodNumber>;
            enableRotate: ZodDefault<ZodBoolean>;
            enablePan: ZodDefault<ZodBoolean>;
            enableZoom: ZodDefault<ZodBoolean>;
            screenSpacePanning: ZodDefault<ZodBoolean>;
            rotateSpeed: ZodDefault<ZodNumber>;
            zoomSpeed: ZodDefault<ZodNumber>;
            panSpeed: ZodDefault<ZodNumber>;
        },
        $strip,
    > = ...

    Schema for OrbitCameraController. Exposes the subset of three.js OrbitControls parameters we want configurable from Python, plus the world up direction applied to the owned camera. Single source of truth: the TS option type (OrbitCameraControllerOptions) is derived via z.infer, defaults are read off it at construction, and the build-time manifest dumper projects it to JSON for the Python auto-UI pipeline.

    Numeric/boolean defaults mirror OrbitControls' own defaults so the interaction is unchanged unless explicitly overridden. up defaults to +Z because Kaolin scenes are +Z up (three.js itself defaults to +Y up).