TexCoordDamper2D
Overview
TexCoordDamper2D generates a series of 2D floating-point arrays that progressively change from initial value to destination value.
The TexCoordDamper2D 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
+ X3DDamperNode
+ TexCoordDamper2D
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
MFVec2f [in] set_value (-∞,∞)
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.
MFVec2f [in] set_destination (-∞,∞)
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.
MFVec2f [ ] initialValue [ ] (-∞,∞)
Initial starting value for this node.
MFVec2f [ ] initialDestination [ ] (-∞,∞)
Initial destination value for this node.
SFInt32 [ ] order 3 [0..5]
order defines the number of internal filters (larger means smoother response, longer delay).
SFTime [in, out] tau 0.3 [0,∞)
tau is the exponential-decay time constant for filter response in seconds.
SFFloat [in, out] tolerance -1 -1 or [0..∞]
Absolute value for satisfactory completion proximity (-1 lets browser choose).
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.
MFVec2f [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 <TextureTransform> node’s translation field, for example.