struct

FLidarShot

One trigger pull, and the entire replication payload for it. A shot is re-traceable from these bytes alone: every ray direction is a pure function of (seed, tick, rayIndex) and the shot's frame, with no RNG state carried between rays and no dependence on frame rate or on how many shots came before. Sending this instead of the resulting points is the difference between tens of bytes and megabytes per trigger pull.

Module
Game
Header
#include "PointCloud/LidarTrace.h"
Namespace
Mowo

Properties

TypeNameDescription
Vec3origin
Vec3directionDefault Vec3(0.0f, 0.0f, -1.0f).
floatconeRadiansDefault 0.12f.
floatrangeDefault 40.0f.
uint32_trayCountDefault 256.
uint32_tseedDefault 0.
uint64_ttickDefault 0.
floatdensityFalloff>1 concentrates rays toward the axis (a tight dot in the middle, sparse at the rim); 1 spreads them uniformly over the cap. This is the knob that separates a focused scanner from a floodlight without changing ray count. Default 1.0f.
ELidarPatternpatternDefault ELidarPattern::Cone.
uint8_trangeBandThe scanner's range band (1 far, 2 normal, 3 precise; 0 none): the points it makes carry it, and it picks their dedup grid. Default 0.
floatwaveSpeedA Fill's reveal speed in metres per second, 0 for a shot that lands at once. A Fill paints a whole room; landing it in one frame is a flash, so its hits are released outward from the origin at this speed. Default 0.0f.
Generated from PointCloud/LidarTrace.h via game.json · Nov 5, 2026Version 1.0.0