struct
FPointCloudBudget
What happens when the cloud is full, stated as data rather than left to a clamp somewhere. Pages are the resource that actually runs out: the GPU pool is maxPoints / kPageCapacity pages and a chunk holds one page per kPageCapacity of its points, so a sparse chunk costs one page and eviction frees a predictable amount.
- Module
- Game
- Header
#include "PointCloud/PointCloudAccumulator.h"- Namespace
Mowo
Properties
| Type | Name | Description |
|---|---|---|
uint32_t | maxPoints | Default 2000000. |
float | quantizeStep | Dedup grid. Two rays that land within this distance of each other on the same surface produce one point, which is what stops a player standing still and holding the trigger from eating the whole budget. It also absorbs last-ulp differences between two machines re-tracing one shot. Default 0.01f. |
float rangeQuantizeSteps[8] = | The dedup grid per scanner range band (the record's 3-bit range): a far scan keeps one point per 8 cm, a normal one per 4 cm, a precise one per 1.5 cm. 0 falls back to quantizeStep, which is what band 0 — a cloud that never sets a range — uses. Bands never dedup against each other, so a precise pass adds detail over a far one instead of being eaten by it. | |
float | lodNearDistance | Default 12.0f. |
float | lodFarDistance | Default 90.0f. |
float | lodFarFraction | Default 0.125f. |
uint32_t | minRankCeiling | Decimation floor — a chunk is never thinned below 1/16 of its density. Past that the cloud stops reading as a surface and eviction is honest. Default 16. |
uint32_t | ephemeralCapacity | The decaying half. Its points share the component's SSBO but sit PAST the last page, in the space PointCloudComponent::ephemeralCapacity allocated on top of maxPoints — carving them out of the page pool would shrink the persistent budget of every cloud that already exists. 0 drops dynamic hits. Default 32768. |
uint32_t | ephemeralLifetimeTicks | Default 180. |
Generated from PointCloud/PointCloudAccumulator.h via game.json · Nov 5, 2026Version 1.0.0