Skip to main content

Crate pointblitz_core

Crate pointblitz_core 

Source
Expand description

PointBlitz render core: scene, chunk store, GPU buffers, point pipeline, capture.

No window, network or browser API here (decision 0003). Targets (native, web, server) own the device, the surface and the frame loop, and call into this crate.

Re-exports§

pub use camera::Camera;
pub use headless::Headless;
pub use layers::Blend;
pub use layers::Fog;
pub use layers::FrameStyle;
pub use layers::LineRenderer;
pub use layers::LineSet;
pub use layers::Material;
pub use layers::MeshData;
pub use layers::MeshRenderer;
pub use layers::Shading;
pub use layers::TextureImage;
pub use layers::Topology;
pub use layers::begin_pass;
pub use renderer::PointSize;
pub use renderer::Renderer;
pub use scene::Inserted;
pub use scene::Scene;
pub use slots::Applied;
pub use slots::ApplyError;
pub use slots::SlotScene;
pub use slots::UploadMethod;
pub use timer::GpuTimer;

Modules§

camera
Camera in ENU metres (decision 0013): x east, y north, z up.
headless
Offscreen rendering and readback: fixed-viewpoint captures, tests, server-side frames.
layers
SkyLens additions: everything a map-style scene needs next to the points, drawn into one caller-owned pass so points, meshes and lines share a depth buffer.
renderer
The point pipeline: one draw per chunk, instanced quads, reversed-Z depth, no sorting (decisions 0006, 0007, 0013). Slot scenes (decision 0052) are one draw each, through the same shader and size/colour rules.
scene
Chunks on the GPU, grouped in generations (decision 0009).
slots
Points in slots, changed by slot diff messages (decision 0052).
timer
GPU time of a run of frames from pass timestamps (decision 0049).