Reality

AugmentedReality/Virtual
App 1at

3.6 Java 3D Scene Graph

components of a Java 3D scene diagram. A virtual world or universe
Fig.361 shows the main
of scene graphs, typically one per application. It has a locale node that anchors
has a collection
associated with a Jocale are live and therefore
multiple branch diagrams to the world. Only topics
rendered in the scene. Deleting the branch diagramreverses the process.
AVtuale
Unverse

Behavior
Content Locale View
branch branch
Behavior
handler
code
Brencheoup EBranchGroU
Ambient
light
Dir
TransiomGroup
TransfomGroup/
TransfornGroup// TranskornGroup/TransfomGroup
VeanvastD
Shapeto Shape3D Shape3D ViewPlatfom
Physica Physical
Appearance)Geametry Appearance Geometry body environment

Fig. 3.6.1t Java 3D Scene graph

Each branch graph hasa group node called
BranchGrpup that defines compatible subgraphs
and acts like the gluc that holds the elements of the
branch together. A group node places and
aligns leaf nodes inlo a transformation group node. A
Switch node allows you to choose between
mukiple subgraphs within a group and specify the level of
sct determine the order in which detail. Finally, the nodes in the ordered
branch leaf nodes (objects) are rendered.
Java 3D's scene graph traversal order is
less structured. Leaf nodes have no
Therefore, unlike WTK,
contain information or child nodes and either
reference node component objects. A very
ViewPlatform which sets the position and orientation of the important keaf node is the
vitual camera in the world. The
Java
TECHNICAL PUBLICATIONS- an up-thrust for
knowiedge
 315
Augmented Reality / Vtual Really VRPogrning
the user to navieate
3D application manipulates the value of his ViewPlatform node to allow
View object (described later in thi
through the virtual world. AViewPlatform together with a
3D view model.
chapter)form aJava 3Dplatform independent
nodes contain information about the virtual object's geometry and appearnnce
Shape3D leaf
the bounding box needed for collision detection,Other leaf nodes
(described above), as wellas predefined behaviors, fog and iniverse
point, drectional),
specify lighting conditions (ambient,
background colors. her VRML,WRL Gle
virtual hand to the virtual world, we nced to load that
If we need to add a segnent ofthe virtual hand
shows how to load each
following exampl
into the scene graph. The hierarchy between these segments (nodes).
individualy and how to define aparent-child

3.6.1Sensors and Behaviors via a'set of 6DOF input devices

programmed in Java 31D is provided
Input for simulations Unlike WTK, Java 3D does not support trackers'or
environment" class.
specified in the "'physics provides an input device interface with which
VR-specific input devices. Instead, theAPI Users then define methods
for
other must be linked.
driveis (written' in C/CH+ by developers) querying its status.
device as well as setting and
closing and readingaþarticulardevice, versatility of th Java 3D
opening, independence and
approach is taken to preserve the illustrated by the fact that input device
The above APL. This generality is
as'a high-level graphics allows the simulation to be driven by
platform This
data from both real and virtual devices. Altematively, the sinulation
interfacesaccept nser actions.
as is norinally donewhen replaying Finally, the user can create
a
data stored in files, (remote sensing).
d¡ta from a network connection tuming the mouse intoa vutual tracker
can read and 6D tracker data,
mouse data
"translator" betwecn2D
device. device object. The latest data from
associated with each input The
One or more sensor
objects are
SensorRead objects placed in a circular buffer.
contained in a series of an integer array of
each sensor object is data (or less) with a timestamp and
SensorRead object contains his 6DOF averaging sensor data and making predictions
the task of
pushbutton values. Java 3D simplifies data. The button value indicates whether
the
providing time-stamped
based on existing data by
state, or trigger state.
button is in button-down state, button-down
devices and output to graphic and audio displays are linked to Java
Input from simulated input
describes the type of graphics display (CRT, Sterco HMD or CAVE) used
3D View objects. This
Canvas3D objects
in the simulation specified by PhysicalEnvironment. Each view has one or more

TECHNICAL PUBLICA TIONS-an up-thrusttor knowledge

AugrertedRoality/VhaRealiy 3-16
which it
is drawn. This VR Programrring
Screen areas in area is part of the
sclectthe
initial position relativedisplay's scIeen caled
that describes the user's
Sereen3D.The
View object also
tracker's availability and position as to the display Screen,
andthe height and I PD) are
deternined by the display
policy. The usets
characteristics(such as specified by the PhysicalBody.
unNerse

Behavior
Content
branich Locale View
Behavior branch
handler
code
BranciGoUD BranchSrcp
Ambient
TransforrnGroup
TransforrmGroup
FTransiormGroup/TiansforinGroup/TransiormGroup/

Shape3D Shape Shape3D ViewPlatorm

Appearanca Geometry AppearancaGeometry

\VewCanvas3D) VemCavastD)

Physical
(Physical Physical Physical envionent
environment bocy
body

and multiple views

Fig. 3.6.2 Java 3D
scene graph for single ViewPlatform node

knOwiedge
up-thrustfor
TECHNCAL.PUBLUCATIONS -an
Agnented Reality/Vital Realily 3-17 VR Programming
nerse

Behavior
Content Locale View
branch branch
Behavior
handle
code
CBancbroup
Ambient
Tr£nsformGroup
TransformGroup
TransformGroup/Tran_fomGroup TransformGroup

Shape3D ViewPlatform NenPlatforrn

Shape30D Shape3D
AppearanceGeometry Appearance Geometry

ViewCanvas3D

Physical Physical (Physical Physical

body environnent body environmert
Fig. 3.6.3 Java 3D scene graph for multiple ViewPlatform nodes
This View model provides a clean separation between the virtual world (provided by the
ViewPlatform node) and the actual he 1/0 device used for interaction. This separation allows
simulation code to be preserved even if the /0 device changes and is central to Java 3D portabiliy.
Multiple users can be tracked simultaneously and assigned to the same location in the vimual
workd. This is the case shown in Fig. 3.6.2, with multiple views and his ViewPlatform Conversely,
One user can control multiple ViewPlatfoms, as shown in Fig. 3.6.3. Each ViewPlatform node has
s oWn Her View (and Screen3D), allowing the user to teleport between remote locations in the
Virtual world, each corresponding to a different ViewPlatform.
the adjacent area of the virtual
A ViewPlatform node bas an activation radius that represents simulation Java 3D
through thÃ
world. Reposition the activation radius as the user moves that
planned boundary of the vitualobject
recognizes when the activation radius intersects the (such as spheres
er bexes) th¡t
bounding volumes activation adius tiggers a
Iepresents the motion. These are user-specified ViewPatforn
with the
sarTound objects with behaviors. An intersection knowiece
for
an up-thrust