GeorgeS2019
### 🧱 Godot-Only Data Structures / Functional Areas | **Godot Feature** | **Description** | |------------------|-----------------| | **CesiumDataSource** (`CesiumDataSource.h`) | Appears to be a unique abstraction for managing data sources—no Unity equivalent. | | **CesiumGDConfig** (`.cpp/.h`) | Configuration system specific to Godot’s integration—Unity doesn’t expose a similar config module. | | **CesiumGDPanel** (`.cpp/.h`) | UI panel integration for Godot’s editor—Unity uses different editor tooling. | | **CesiumHTTPRequestNode** (`.cpp/.h`) | Godot-specific HTTP request node—Unity uses UnityWebRequest or native C# HTTP clients. | | **HtmlRect / LocalAssetRequest / LocalAssetResponse** | Likely tied to Godot’s HTML UI rendering or asset loading—no direct Unity counterpart. | | **SimpleTaskProcessor** | Lightweight task processor for async operations—Unity uses `AsyncSystem` or coroutines. | | **TileMetadata** (`.cpp/.h`) | Godot’s approach to tile metadata—Unity uses more granular feature ID/property classes. | --- ### 🧪 Godot-Only Functional Concepts - **litehtml Integration**: Several files reference `litehtml` as a built binary—Unity doesn’t use this HTML rendering engine. - **Custom Trimesh Collision**: Implemented in `CesiumGDTileset.h`—Unity likely handles this differently via PhysX or Unity’s MeshCollider. - **Local Cache Configuration**: `CesiumGDRasterOverlay` supports local cache setup—Unity’s Cesium integration doesn’t expose this directly. - **Godot Signals & Nodes**: While not visible in filenames, Godot’s architecture relies on signals and scene trees—Unity uses MonoBehaviours and GameObjects instead. ---