mirror of
https://github.com/Relintai/pandemonium_engine.git
synced 2024-12-24 12:47:12 +01:00
45 lines
2.9 KiB
XML
45 lines
2.9 KiB
XML
|
<?xml version="1.0" encoding="UTF-8" ?>
|
||
|
|
<class name="PathFollow2D" inherits="Node2D" version="3.5">
|
||
|
|
<brief_description>
|
||
|
|
Point sampler for a [Path2D].
|
||
|
|
</brief_description>
|
||
|
|
<description>
|
||
|
|
This node takes its parent [Path2D], and returns the coordinates of a point within it, given a distance from the first vertex.
|
||
|
|
It is useful for making other nodes follow a path, without coding the movement pattern. For that, the nodes must be children of this node. The descendant nodes will then move accordingly when setting an offset in this node.
|
||
|
|
</description>
|
||
|
|
<tutorials>
|
||
|
|
</tutorials>
|
||
|
|
<methods>
|
||
|
|
</methods>
|
||
|
|
<members>
|
||
|
|
<member name="cubic_interp" type="bool" setter="set_cubic_interpolation" getter="get_cubic_interpolation" default="true">
|
||
|
|
If [code]true[/code], the position between two cached points is interpolated cubically, and linearly otherwise.
|
||
|
|
The points along the [Curve2D] of the [Path2D] are precomputed before use, for faster calculations. The point at the requested offset is then calculated interpolating between two adjacent cached points. This may present a problem if the curve makes sharp turns, as the cached points may not follow the curve closely enough.
|
||
|
|
There are two answers to this problem: either increase the number of cached points and increase memory consumption, or make a cubic interpolation between two points at the cost of (slightly) slower calculations.
|
||
|
|
</member>
|
||
|
|
<member name="h_offset" type="float" setter="set_h_offset" getter="get_h_offset" default="0.0">
|
||
|
|
The node's offset along the curve.
|
||
|
|
</member>
|
||
|
|
<member name="lookahead" type="float" setter="set_lookahead" getter="get_lookahead" default="4.0">
|
||
|
|
How far to look ahead of the curve to calculate the tangent if the node is rotating. E.g. shorter lookaheads will lead to faster rotations.
|
||
|
|
</member>
|
||
|
|
<member name="loop" type="bool" setter="set_loop" getter="has_loop" default="true">
|
||
|
|
If [code]true[/code], any offset outside the path's length will wrap around, instead of stopping at the ends. Use it for cyclic paths.
|
||
|
|
</member>
|
||
|
|
<member name="offset" type="float" setter="set_offset" getter="get_offset" default="0.0">
|
||
|
|
The distance along the path in pixels.
|
||
|
|
</member>
|
||
|
|
<member name="rotate" type="bool" setter="set_rotate" getter="is_rotating" default="true">
|
||
|
|
If [code]true[/code], this node rotates to follow the path, making its descendants rotate.
|
||
|
|
</member>
|
||
|
|
<member name="unit_offset" type="float" setter="set_unit_offset" getter="get_unit_offset" default="0.0">
|
||
|
|
The distance along the path as a number in the range 0.0 (for the first vertex) to 1.0 (for the last). This is just another way of expressing the offset within the path, as the offset supplied is multiplied internally by the path's length.
|
||
|
|
</member>
|
||
|
|
<member name="v_offset" type="float" setter="set_v_offset" getter="get_v_offset" default="0.0">
|
||
|
|
The node's offset perpendicular to the curve.
|
||
|
|
</member>
|
||
|
|
</members>
|
||
|
|
<constants>
|
||
|
|
</constants>
|
||
|
|
</class>
|