FChaosPathedMovementInputs

Navigation

API > API/Plugins > API/Plugins/ChaosMover

Frame inputs for all pathed movement Any property that can change during game time must be delivered in this way, only immutable properties can be safely referenced directly on the object they come from (usually the movement mode)

NOTE: MovementStartFrame and LastChangeFrame use integer frame numbers for scheduling and ordering. This is correct in async (fixed-dt) mode, where both server and client share the same synchronized frame counter. In non-async (variable-dt) mode, frame numbers are a local monotonic counter and are NOT synchronized across endpoints. The current implicit assumption is: networked => fixed-dt, variable-dt => standalone only. To support variable-dt networking properly, these fields would need to become FMoverTime.

Syntax

USTRUCT ()  
struct FChaosPathedMovementInputs : public FMoverDataStructBase  
Copy full snippet

USTRUCT () struct FChaosPathedMovementInputs : public FMoverDataStructBase

Inheritance Hierarchy

• FMoverDataStructBase → FChaosPathedMovementInputs

Variables

Public

Functions