orbital-engine
    Preparing search index...

    Interface EmbeddedBodyWarning

    A body whose real distance from its own immediate parent's centre is less than that parent's own radius — it would render fully inside the parent's solid sphere, occluded, however correct the underlying data is.

    This is deliberately NOT a data-correctness check (see a data pipeline's own equivalent, e.g. Citizens.Edge.Data's validateBodyPositions/ validateNoForeignContainment): a body genuinely sitting closer to its real parent's centre than a generic placeholder radius implies is expected, not a bug, whenever real per-body radii aren't known (every body of a type sharing one fixed radius regardless of true size is a documented, accepted approximation upstream). The bug this catches is purely visual — a real, confirmed instance: Star Citizen's Grim Hex sits ~686 km from Yela's own centre, well inside Yela's generic 1,737 km Moon-sized placeholder radius, so Grim Hex's own station model renders occluded behind Yela's opaque sphere. Surfacing this lets a host app flag it (e.g. in a dev-mode overlay) without either engine or app needing to guess at a body's real size just to notice the problem.

    interface EmbeddedBodyWarning {
        bodyId: string;
        bodyName: string;
        parentId: string;
        parentName: string;
        distanceKm: number;
        parentRadiusKm: number;
    }
    Index
    bodyId: string
    bodyName: string
    parentId: string
    parentName: string
    distanceKm: number

    Real km distance from the body to its parent's centre — NOT compressed/world-space, since the parent's own radiusKm this compares against is real km too.

    parentRadiusKm: number