unreal.ChaosPathedMovementInputs¶
- class unreal.ChaosPathedMovementInputs¶
Bases:
MoverDataStructBaseFrame 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.
C++ Source:
Plugin: ChaosMover
Module: ChaosMover
File: ChaosPathedMovementTypes.h
Editor Properties: (see get_editor_property/set_editor_property)
last_change_frame(int32): [Read-Only]movement_start_frame(int32): [Read-Only]props(ChaosMutablePathedMovementProperties): [Read-Only]