Orbital Controll System

Description

Controller rebase system for large scale planetary systems. It uses an AActor Component Instancing system for pcg based runtime lods and event based gpu driven rendering with HLSL Custom Nodes.

This is a system-level framing, not marketing. Defining the orbital model, its constraints, and what technical problems it exists to solve. Why this is an orbital system at all and not just a procedural toy.

Features

Artist controlled building through blueprints, adaptable to procedural generation. Client owned worldstate for possible multiplayer support through FLAG updates with server authority (possible anticheat ai). Distance based per object LOD through pcg, use graphs to fade details or swap to not just lod but totally different staticmesh group.

This section is about interaction intent: what the designer or artist experiences, how control is exposed, where authorship lives.

Performance

PCG, HLSL, data flow, update frequency. Why things live on GPU vs CPU and why some decisions are locked early.

Specifications

authorial constraints: Orbits and Star systems are artistically curated Planet creation is deferred to Blueprints Levels own composition, not the generator That makes the system reproducible and intentionally non-procedural in certain dimensions.

full procedural generation is possible, but not always desirable
authorship and intent sometimes matter more than entropy.