orbital-engine
    Preparing search index...

    Function resolveWorldPosition

    • A body's world-render position, computed by compressing each parent→child step independently and summing the compressed segments — NOT by summing the real km offsets first and compressing the final absolute position. Those give very different (and for anything not orbiting the star directly, very wrong) answers: distance compression is radial from the origin, so two points that are both far out — e.g. Jupiter and one of its moons, both ~778M km from the Sun — land almost on top of each other once compressed, even though the moon visibly orbits outside Jupiter in reality. Compressing each segment on its own scale (a moon's ~1M km orbital radius compressed on its own terms, then added to Jupiter's separately-compressed position) preserves that local structure instead of flattening it away — confirmed against real numbers: Callisto's absolute position compresses to within 0.0355 world units of Jupiter's (rendering it inside Jupiter's own compressed radius), while its own ~1.88M km orbital radius compresses to 1.56 world units on its own — the actual separation this function produces.

      Parameters

      Returns WorldVec