Non-Spatial Objects

These objects are for “programming” -- making objects interactive.

Logic objects

These objects are for comparing the value of things to make decisions

• AndGate
• OrGate
• NandGate
• XorGate
• SimpleSequencer - an object that steps through a number of outputs

Variables objects

Thes objects are for storing the value of something

• Value
• IntegerValue - a whole numner
• FloatValue - a decimal numer
• BoolValue - true or false
• Vector3fScaler - stores three float values
• Vector3fValue - stores three float values. A vector is a set of 3 related numbers, typically an X,Y,Z position
• Euler - stores a rotation: pitch, yaw and roll
• Material - stores a material, which contains color
• String - stores test characters (for resource locators and text in TextQuads)
• color3f - stores a color

Array Objects

Arrays are an ordered list of variables, used to store several items. A complete set of Arrays of the above variables, which can be iterated though, presenting a current value to wiring. This enables you to, say, switch the resource locator on a mesh though a set, either from a timer or from a button.

• IntegerArray
• FloatArray
• BoolArray
• Color3fArray
• StringArray
• EulerArray
• Vector3fArray
• MaterialArray

Offsets

A vector is a set of 3 related numbers, typically an X,Y,Z position, or rotation specification. Offset allows adding one vector to another to do something like change the position.

A complete set of offsets – these are dataflow components – wire something like a position and it will present at the output a value offset by the value of the offset. Or they can be used “get” style.

• IntegerOffset
• FloatOffset
• Color3fOffset
• EulerOffset
• Vector3fOffset
• Vector3fRandomOffset

Splitters

Mux (takes a complex type like Vector3f in input and splits it into 3 values, x, y, z in output) and DeMux, which performs the reverse. Allows you to process just one component of a complex type in wiring, and then turn it back into a vector type.

• EulerMux
• EulerDemux
• Color3fMux
• Color3fDemux
• Vector3fMux -- unpacks a vector into 3 individual values
• Vector3fDemux

Interpolators

A set of interpolators which “tween” values between two end values (start and end). These exist for things which make sense to tween = Integers, floats, Vector3f, Euler, and Color3f.

• IntegerInterpolator
• FloatInterpolator
• Color3fInterpolator
• EulerInterpolator
• Vector3fInterpolator - Given two vectors, and an amount float that ranges from zero to one, this outputs an altered vector that is interpolated between the two vectors based on the amount.

Resource objects

• Resource
• Spawner

Triggers

• FloatTrigger - fires a message when a float number is equal to another
• Trigger - fires a message
• IntegerTrigger- fires a message when an integer number is equal to another
• ProximityDetector - sends a message when an object gets close to another object

Random

Random generates a random number. Two variants for random offsets are also implemented. Use these to add noise to movement.

• Random->RanFloat - random number
• Random->RanVec3

Teleport

• Reparenter - changes the parent of an object. Objects, by default have the zone as their parent. This object enables you to set another object as the parent - typically a Composite object.
• Teleport - Contains a destination location, orientation and zone. When its Go method triggered, it moves the user to that destination

There are five properties of the Teleport object that are relevant to where the user will be placed and how their viewpoint will be rotated:

1. TargetZone
2. TargetPosition
3. TargetRotation
4. SendRotation
5. SendPosition

• If the TargetZone property has a value (the name of that zone) then we are going to switch to that zone. If it is empty, we stay in the current zone.
• SendPosition and SendRotation must be true (checked) for TargetPosition and TargetRotation respectively to have any effect. If teleporting within the current zone, you must set one or both of these to be true.
• If SendPosition is true, then when the user arrives in the new zone, the SpawnPosition of that zone is overridden and the user is positioned at the TargetPosition
• If SendRotation is true, then when the user arrives, the SpawnRotation of that zone is overridden and the users eyes are forced to look in the direction specified by the TargetRotation property.
• If both SendPosition and SendRotation are false, then the user arrives at the SpawnPosition and SpawnRotation specified in the target zone.

Timer objects

• OneShotTimer - sends a message after a delay
• Timer - sends periodic messages

Controllers

The new controller objects are easier to use – just hook up “controlOut” on a controller/mover to “controlIn” on an object being controller and it will automatically “just work” once you set its running property to true. If you want to go old school and use data flow type wiring to modify the output of a controller (say using offsets) appropriate “output” outputs also exist on the various controllers to wire to things like splitters, interpolators, etc.

• EllipseMover2 – move things on ellipses
• RotationContoller2 – controls rotation
• WaypointMover2 – moves things around on waypoints, replaces previous embedded functionality
• LookAtController2 – look at things – ie giant eyeballs follow something you drag.
• ScannerController2 – move things back and forth in a line
• SineController2 – move things on Sine waves (with adjustable phase – so can do Sin, Cos or anything between)

Debugging

• EdgeDebugger – wire something like positionChanged output to this and observe the values on the wire using the PropertyEditor – it adds values for the values inside the parameter node

Next: Animated_Objects