instantreality 1.0

Component:
Shape
Status:
partly implemented
Structure type:
abstract
Standard:
Avalon

SimulatedAppearance

The SimulatedAppearance node runs a simulation in image space and can be used as an additional appearance of the geometry.

Inheritance

Code

XML encoding
<SimulatedAppearance timeStep='0.4'
timeDelay='0.01'
triggerName='Timer'
sortKey='0'
sortType='auto'
logFeature=''
 />
Classic encoding
SimulatedAppearance {
	timeStep 0.4
	timeDelay 0.01
	triggerName "Timer"
	sortKey 0
	sortType "auto"
	logFeature [""]
}

Interface

Filter: X3D only | Avalon only | All
id Name DataType PartType Default ValueType Description
MFString logFeature MFString inputOutput state, child, parent, route, eventIn, eventOut controls the logging of changes, state: log state changes (e.g. live), child: log child add/remove, parent: log parent add/remove, route: log route add/remove; eventIn: log receiving of events, eventOut: log sending of events: guiView, runtime system should create node-view, guiEdit: runtime system should create node-editeverything: log everything
SFNode metadata SFNode inputOutput MetadataObject container for payload metadata inside MetadataSet element
SFBool pause SFBool inputOnly Trigger to pause/ resume the simulation.
MFNode properties MFNode inputOutput AppearanceProperty holds appearance properties (like material, texture and texture transformation) to be applied to the Shape's geometry
SFNode scene SFNode inputOutput NULL SceneBaseNode Subgraph containing geometry to which simulation shall be applied to
SFInt32 sortKey SFInt32 inputOutput 0 Change render order manually.
SFString sortType SFString inputOutput auto [auto, transparent, opaque] defines the shape type for sorting
SFNode texture SFNode inputOutput Texture Valid values of the texture field are descendants of Texture node
SFTime timeDelay SFTime inputOutput 0.01 Approximate value for dT in update
SFTime timeStep SFTime inputOutput 0.4 Approximate value for dT in simulation
SFString triggerName SFString initializeOnly Timer Name of the dynamic context-slot which is used by the run-time environment (e.g. Jobs) to trigger the node. Life-Nodes will automatically connect the context-eventOutput to the triggerSlot-eventInput Slot.