struct
ScanMeshComponent
How an entity appears to the LiDAR scan (audit S4). Without one, a static mesh scans as its render triangles and a moving one is not in the scan scene at all. With one, an authored scan mesh can stand in for the render mesh (the render mesh is the wrong resolution for a 1.5 cm precise band, the collider the wrong content), a moving body is traced as a live instance, and an animated character gets a capsule per bone that follows its pose.
- Module
- PointCloud
- Header
#include "PointCloud/ScanMeshComponent.h"- Namespace
Mowo- Reflection
- Reflected by MowoHeaderTool
Properties
| Type | Name | Description |
|---|---|---|
bool | enabled | Default true. |
bool | exclude | Invisible to the scanner: glass the design wants to see through, a trigger volume that happens to carry a mesh. Default false. |
std::string | scanMesh | A dedicated scan mesh (a model asset); empty scans the render mesh. |
int32_t | scanTag | Scan response tag; -1 takes the collider's surface type. Default -1. |
EScanMeshLayer | layer | Auto: static bodies are the static world, moving ones props, characters (anything with bone capsules) characters. Default EScanMeshLayer::Auto. |
bool | dynamic | Traced where it is every frame, not where it was when the scene was built. On by default for any body that is not static. Default false. |
bool | boneCapsules | A capsule per bone of the entity's animator, posed every frame. Default true. |
float | capsuleRadiusScale | Default 1.0f. |
Constructors
| Signature | Name | Description |
|---|---|---|
ScanMeshComponent() = default | ScanMeshComponent |
Function details
ScanMeshComponent
C++
ScanMeshComponent() = defaultGenerated from PointCloud/ScanMeshComponent.h via pointcloud.json · Oct 26, 2026Version 1.0.0