Evergine.Bindings.CesiumNative 2026.8.9.34

Cesium.NET

This repository contains low-level bindings for Cesium Native used in Evergine. This binding is generated from the CesiumNativeC API header.

Purpose

Cesium Native is a set of C++ libraries for 3D geospatial applications. It provides:

• 3D Tiles streaming and rendering
• Cesium Ion asset access and authentication
• Geospatial coordinate transformations (ellipsoid, cartographic, globe transforms)
• glTF model loading and parsing
• Raster overlay support (Ion imagery, URL templates, TMS, WMS)

This .NET binding exposes the C API surface (CesiumNativeC) as P/Invoke methods, enabling .NET applications and engines like Evergine to leverage Cesium Native's 3D geospatial capabilities.

Go to the original repository for more details: https://github.com/CesiumGS/cesium-native

Features

• Tileset streaming — Load and traverse 3D Tiles tilesets from URLs or Cesium Ion assets
• View-dependent selection — Per-frame tile selection with screen-space error, frustum culling, fog culling, and occlusion culling
• Geospatial math — Ellipsoid, cartographic, globe rectangle, and globe transform operations
• glTF reader — Parse glTF/GLB models from byte buffers with error/warning reporting
• Raster overlays — Ion imagery, URL template (XYZ), TMS, and WMS overlay layers
• Cesium Ion integration — Authentication, asset listing, and token management
• Credit system — On-screen attribution management for data providers
• Renderer resource bridging — Callback-based integration for custom render pipelines

Supported Platforms

• Windows x64, ARM64
• Linux x64, ARM64
• macOS ARM64
• Android ARM64
• iOS ARM64, simulator ARM64
• Browser WebAssembly

Nine runtime identifiers, and every release checks each of them against the real .nupkg before publishing — a failure stops the publish. What that check is worth differs by platform, and the difference is worth knowing rather than glossing:

Mobile is loaded differently from the desktop identifiers, and you do not have to do anything about it: Android carries an ordinary shared library, while iOS links a static archive into your application, which is why the package ships a buildTransitive targets file.

WebAssembly needs no extra setup on your side, but it does work differently: the archive is linked into your application at publish time rather than loaded at run time, and the generated *CallbacksSet.ToNative helpers cannot be used there — AOT rejects a managed method reached from native code unless it is [UnmanagedCallersOnly]. See WasmSmokeTest/ for a host that does it the way wasm requires.