Point count for a drawn orbit path (or the flat reference ring for a
fixedPosition body) — same reasoning as sphereDetailFor, but for a
shape where "large apparent size" doesn't mean "close to filling the
screen" (nothing here is a solid body the camera zooms into), it means
the ring's own curve spans a large part of the view, which is exactly
when a fixed, modest segment count starts showing as visible straight
facets rather than a smooth curve. Call with apparentSize(ringWorldRadius, cameraDistance), the same as any other body — the ring is still
fundamentally a polyline at any segment count (no renderer draws a true
analytic curve), this just keeps the facets smaller than a pixel at
whatever scale the ring is actually being viewed at.
Point count for a drawn orbit path (or the flat reference ring for a fixedPosition body) — same reasoning as sphereDetailFor, but for a shape where "large apparent size" doesn't mean "close to filling the screen" (nothing here is a solid body the camera zooms into), it means the ring's own curve spans a large part of the view, which is exactly when a fixed, modest segment count starts showing as visible straight facets rather than a smooth curve. Call with
apparentSize(ringWorldRadius, cameraDistance), the same as any other body — the ring is still fundamentally a polyline at any segment count (no renderer draws a true analytic curve), this just keeps the facets smaller than a pixel at whatever scale the ring is actually being viewed at.