The input type is described on each line along with the Valuator's factor and offset values that affect the output given the input type. The blue text is the result of routing the outMFString field of each valuator to the string field of a text node.
The values for each type are created by interpolators all fed from a single TimeSensor having a cycle time of 10s.
SFbool | a ScalarInterpolator, set to generate 0.0 and 1.0 values, which change discretely every 2.5s, i.e. 4 times in the 10s cycle, feeds the inSFFloat of a valuator to give an SFBool output. It is this SFBool output that feeds the inSFBool of the valuator under test. |
SFInt32 | a ScalarInterpolator, set to generate continuous values between 0.0 and 10.0 over the 10s cycle, feeds the inSFFloat of a valuator to give an SFInt32 output. It is this SFInt32 output that feeds the inSFInt32 of the valuator under test. |
SFFloat | the ScalarInterpolator, as used to generate the SFInt32 above, feeds directly the inSFFloat of the valuator under test. |
SFTime | the time output field of the TimeSensor feeds the inSFTime of the valuator under test. |
SFVec2f | a PositionInterpolator2D, set to generate continuous values between 0.0 0.0 and 10.0 100.0 over the 10s cycle, feeds the inSFVec2f of the valuator under test. Note: the y value is 10 times the x value and the factors and offsets are set up that way too, i.e. Factor2 and Offset2 are 10 times the values in Factor1 and Offset1 respectively - except for when they are left at default values which for the factor is 1. |
SFColor | a ColorInterpolator, set to generate values between 0.0 0.0 1.0 and 1.0 1.0 0.0, over the 10s cycle, feeds the inSFColor of the valuator under test. Note: Since color interpolation is done is an HSV space (see the VRML spec, on which the MPEG-4 node is based, for more information) the values do not linearly interpolate in the RGB space, where the colors listed above are defined. |
Note: to view the output values it may be helpful to pause the playback as some values can change rapidly.
The above tests do not include SFVec3F. However the test case IBMTouchSensorHitPoint contains an example of this where the output of the hit point is displayed (being 2D the z value is always 0 there though).
Snapshot taken at 5.672s.
![]() |