Post

OrientationChaser

OrientationChaser

Overview

OrientationChaser generates a series of 4-tuple axis-angle SFRotation values that progressively change from initial value to destination value.

The OrientationChaser node belongs to the Followers component and requires at least level 1, its default container field is children. It is available from X3D version 3.2 or higher.

Hierarchy

1
2
3
4
5
+ X3DNode
  + X3DChildNode
    + X3DFollowerNode
      + X3DChaserNode
        + OrientationChaser

Fields

SFNode [in, out] metadata NULL [X3DMetadataObject]

Information about this node can be contained in a MetadataBoolean, MetadataDouble, MetadataFloat, MetadataInteger, MetadataString or MetadataSet node.

Hint

SFRotation [in] set_value [-1,1] or (-∞,∞)

set_value resets current value of this node.

Warning

  • It is an error to define this transient inputOnly field in an X3D file, instead only use it a destination for ROUTE events.

SFRotation [in] set_destination [-1,1] or (-∞,∞)

set_destination resets destination value of this node.

Warning

  • It is an error to define this transient inputOnly field in an X3D file, instead only use it a destination for ROUTE events.

SFRotation [ ] initialValue 0 1 0 0 [-1,1] or (-∞,∞)

Initial starting value for this node.

SFRotation [ ] initialDestination 0 1 0 0 [-1,1] or (-∞,∞)

Initial destination value for this node.

SFTime [ ] duration 1 [0,∞)

duration is the time interval for filter response in seconds.

Hint

  • duration is a nonnegative SFTime duration interval, not an absolute clock time.

SFBool [out] isActive

isActive true/false events are sent when follower-node computation starts/stops.

Warning

  • It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.

SFRotation [out] value_changed

Computed output value that approaches within tolerance of destination value, as determined by elapsed time, order and tau.

Warning

  • It is an error to define this transient outputOnly field in an X3D file, instead only use it a source for ROUTE events.

Advice

Hint

  • ROUTE value_changed output events to a <Transform> node’s rotation field, for example.

See Also

This post is licensed under CC BY 4.0 by the author.