Web3D.org - User contributions [en]

Main Page

2007-05-23T16:53:14Z

Giles: /* X3D commmunity info */

== About the Public X3D Wiki ==
* [[Usage Guidelines]]
* [[How to wiki]]
* [[Create New Page]]

== X3D Documentation ==
* [[How-To Guides]]
* [[Node Reference]]
* [[Plug-in and browser compliance]]
* [[Recommendations for browser developers]]

== X3D commmunity info ==
* [[Upcoming X3D events]]
* [[X3D_Implementations]]

X3D Implementations

2006-12-01T21:51:15Z

Giles: Added Heilan, moved Flux to open source

This page lists all known X3D implementations.

Open Source
Carina
CyberX3D
Flux
FreeWRL
Heilan
H3D API
Open ActiveWrl
Open VRML
X3D Toolkit
Xj3D

Commercial
Avalon
Contact
JINX
Octaga
Venues
TGS

Unknown License
MobiX3D
Demotride

X3D Implementations

2006-04-26T18:13:20Z

Giles:

This page lists all known X3D implementations.

Open Source
Carina
CyberX3D
FreeWRL
H3D API
Open ActiveWrl
Open VRML
X3D Toolkit
Xj3D

Commercial
Avalon
Contact
Flux
JINX
Octaga
Venues
TGS

Unknown License
MobiX3D

X3D Implementations

2006-04-07T15:52:34Z

Giles: X3D Implementations

This page lists all known X3D implementations.

Open Source
Carina
CyberX3D
FreeWRL
H3D API
Open ActiveWrl
X3D Toolkit
Xj3D

Commercial

Avalon
Contact
Flux
JINX
Octaga
Venues
TGS

Unknown License
MobiX3D

IndexedTriangleFanSet

2006-02-08T01:38:23Z

Giles: minor fixes

<pre>IndexedTriangleFanSet : X3DComposedGeometryNode {
MFInt32 [in] set_index [] [0,∞) or -1
SFNode [in,out] color NULL [X3DColorNode]
SFNode [in,out] coord NULL [X3DCoordinateNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFNode [in,out] normal NULL [X3DNormalNode]
SFNode [in,out] texCoord NULL [X3DTextureCoordinateNode]
SFBool [] ccw TRUE
SFBool [] colorPerVertex TRUE
SFBool [] normalPerVertex TRUE
SFBool [] solid TRUE
MFInt32 [] index [] [0,∞) or -1
}</pre>
An IndexedTriangleFanSet represents a 3D shape composed of triangles that
form a fan shape around the first vertex declared in each fan as depicted in
<a href="#f-TriangleFanSet">Figure 11.1</a>. IndexedTriangleFanSet uses the indices in its index field to specify the
triangle fans by connecting vertices from the coord field. An index of "−1"
indicates that the current fan has ended and the next one begins. The last fan
may be (but does not have to be) followed by a "−1".Each
fan shall have at least three non-coincident vertices.

The IndexedTriangleFanSet node is specified in the local coordinate system
and is affected by the transformations of its ancestors. Descriptions of the 
color, coord, normal, and texCoord fields are provided
in the Color, Coordinate, Normal, and TextureCoordinate nodes, respectively. If
values are provided for the color, normal and texCoord

fields, the values are applied in the same manner as the values from the 
coord field and there shall be at least as many values as are present in the
coord field. The value of the colorPerVertex field is ignored and
always treated as TRUE. If the normal field is not provided, normals
shall be generated as follows:
<ul>
<li>If normalPerVertex is TRUE, the normal
for each vertex shall be the average of the normals for all triangles sharing
that vertex.</li>

<li>If normalPerVertex is FALSE, the normal
shall be generated for the current triangle based on the ccw field.</li>
</ul>

The solid field determines whether the IndexedTriangleFanSet is visible when viewed
from the inside.

==Authoring Tip==
This node is designed for getting geometry to the graphics card very efficiently. You must
provide normals for this to work right. The fallback paths without normals will not be nearly as fast.

IndexedTriangleFanSet

2006-02-08T01:37:16Z

Giles:

<pre>IndexedTriangleFanSet : X3DComposedGeometryNode {
MFInt32 [in] set_index [] [0,∞) or -1
SFNode [in,out] color NULL [X3DColorNode]
SFNode [in,out] coord NULL [X3DCoordinateNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFNode [in,out] normal NULL [X3DNormalNode]
SFNode [in,out] texCoord NULL [X3DTextureCoordinateNode]
SFBool [] ccw TRUE
SFBool [] colorPerVertex TRUE
SFBool [] normalPerVertex TRUE
SFBool [] solid TRUE
MFInt32 [] index [] [0,∞) or -1
}</pre>
An IndexedTriangleFanSet represents a 3D shape composed of triangles that
form a fan shape around the first vertex declared in each fan as depicted in
<a href="#f-TriangleFanSet">Figure 11.1</a>. IndexedTriangleFanSet uses the indices in its index field to specify the
triangle fans by connecting vertices from the coord field. An index of "−1"
indicates that the current fan has ended and the next one begins. The last fan
may be (but does not have to be) followed by a "−1".Each
fan shall have at least three non-coincident vertices.

The IndexedTriangleFanSet node is specified in the local coordinate system
and is affected by the transformations of its ancestors. Descriptions of the 
color, coord, normal, and texCoord fields are provided
in the Color, Coordinate, Normal, and TextureCoordinate nodes, respectively. If
values are provided for the color, normal and texCoord

fields, the values are applied in the same manner as the values from the 
coord field and there shall be at least as many values as are present in the
coord field. The value of the colorPerVertex field is ignored and
always treated as TRUE. If the normal field is not provided, normals
shall be generated as follows:
<ul>
<li>If normalPerVertex is TRUE, the normal
for each vertex shall be the average of the normals for all triangles sharing
that vertex.</li>

<li>If normalPerVertex is FALSE, the normal
shall be generated for the current triangle based on the ccw field.</li>
</ul>

The solid field determines whether the IndexedTriangleFanSet is visible when viewed
from the inside. <a href="rendering.html#CommonGeometryFields">11.2.3 Common
geometry fields</a> provides a complete description of the solid field.

==Authoring Tip==
This node is designed for getting geometry to the graphics card very effeciently. You must
provide normals for this to work right. The fallback paths without normals will not be nearly as fast.

Node Reference

2006-02-08T01:34:36Z

Giles:

==List of Nodes==

*[[Anchor]]
*[[Appearance]]
*[[Arc2D]]
*[[ArcClose2D]]
*[[AudioClip]]
*[[Background]]
*[[Billboard]]
*[[BooleanFilter]]
*[[BooleanSequencer]]
*[[BooleanToggle]]
*[[BooleanTrigger]]
*[[Box]]
*[[CADAssembly]]
*[[CADFace]]
*[[CADLayer]]
*[[CADPart]]
*[[Circle2D]]
*[[Collision]]
*[[Color]]
*[[ColorInterpolator]]
*[[ColorRGBA]]
*[[Composed3DTexture]]
*[[ComposedCubeMapTexture]]
*[[ComposedShader]]
*[[Cone]]
*[[Contour2D]]
*[[ContourPolyline2D]]
*[[Coordinate]]
*[[CoordinateDouble]]
*[[CoordinateInterpolator]]
*[[CoordinateInterpolator2D]]
*[[Cylinder]]
*[[CylinderSensor]]
*DirectionalLight
*Disk2D
*ElevationGrid
*EspduTransform
*Extrusion
*FillProperties
*FloatVertexAttribute
*Fog
*FogCoordinate
*FontStyle
*GeneratedCubeMapTexture
*GeoCoordinate
*GeoElevationGrid
*GeoLocation
*GeoLOD
*GeoMetadata
*GeoOrigin
*GeoPositionInterpolator
*GeoTouchSensor
*GeoViewpoint
*Group
*HAnimDisplacer
*HAnimHumanoid
*HAnimJoint
*HAnimSegment
*HAnimSite
*Image3DTexture
*ImageCubeMapTexture
*ImageTexture
*IndexedFaceSet
*IndexedLineSet
*IndexedQuadSet
*[[IndexedTriangleFanSet]]
*IndexedTriangleSet
*IndexedTriangleStripSet
*Inline
*IntegerSequencer
*IntegerTrigger
*KeySensor
*LineProperties
*LineSet
*LoadSensor
*LocalFog
*LOD
*Material
*Matrix3VertexAttribute
*Matrix4VertexAttribute
*MetadataDouble
*MetadataFloat
*MetadataInteger
*MetadataSet
*MetadataString
*MovieTexture
*MultiTexture
*MultiTextureCoordinate
*MultiTextureTransform
*NavigationInfo
*Normal
*NormalInterpolator
*NurbsCurve
*NurbsCurve2D
*NurbsOrientationInterpolator
*NurbsPatchSurface
*NurbsPositionInterpolator
*NurbsSet
*NurbsSurfaceInterpolator
*NurbsSweptSurface
*NurbsSwungSurface
*NurbsTextureCoordinate
*NurbsTrimmedSurface
*OrientationInterpolator
*PackagedShader
*Pixel3DTexture
*PixelTexture
*PlaneSensor
*PointLight
*PointSet
*Polyline2D
*Polypoint2D
*PositionInterpolator
*PositionInterpolator2D
*ProgramShader
*ProtoInstance
*ProximitySensor
*QuadSet
*ReceiverPdu
*Rectangle2D
*ScalarInterpolator
*Script
*ShaderPart
*ShaderProgram
*Shape
*SignalPdu
*Sound
*Sphere
*SphereSensor
*SpotLight
*StaticGroup
*StringSensor
*Switch
*Text
*TextureBackground
*TextureCoordinate
*TextureCoordinate3D
*TextureCoordinate4D
*TextureCoordinateGenerator
*TextureMatrixTransform
*TextureTransform
*TextureTransform3D
*TimeSensor
*TimeTrigger
*TouchSensor
*Transform
*TransmitterPdu
*TriangleFanSet
*TriangleSet
*TriangleSet2D
*TriangleStripSet
*Viewpoint
*VisibilitySensor
*WorldInfo

Appearance

2006-02-02T17:00:58Z

Giles:

* [[Node Reference]]
==Appearance==

<pre>
Appearance : X3DAppearanceNode {
SFNode [in,out] fillProperties NULL [FillProperties]
SFNode [in,out] lineProperties NULL [LineProperties]
SFNode [in,out] material NULL [X3DMaterialNode]
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFNode [in,out] texture NULL [X3DTextureNode]
SFNode [in,out] textureTransform NULL [X3DTextureTransformNode]
}
</pre>

The Appearance node specifies the visual properties of geometry. The value for each of the fields in this node may be <code>NULL</code>. However, if the field is non-<code>NULL</code>, it shall contain one node of the appropriate type.

The material field, if specified, shall contain a Material node. If the material field is <code>NULL</code> or unspecified, lighting is off (all lights are ignored during rendering of the object that references this Appearance) and the unlit object colour is (1, 1, 1). Details of the X3D lighting model are in 17 Lighting component.

The texture field, if specified, shall contain one of the various types of texture nodes (see: Texturing component). If the texture node is <code>NULL</code> or the texture field is unspecified, the object that references this Appearance is not textured.

The textureTransform field, if specified, shall contain a TextureTransform node as defined in 18.4.8 TextureTransform. If the textureTransform is <code>NULL</code> or unspecified, the textureTransform field has no effect.

The lineProperties field, if specified, shall contain a LineProperties node as specified in 12.4.3 LineProperties. If lineProperties is <code>NULL</code> or unspecified, the lineProperties field has no effect.

The fillProperties field, if specified, shall contain a FillProperties node as specified in 12.4.2 FillProperties. If fillProperties is <code>NULL</code> or unspecified, the fillProperties field has no effect.
==Example==
This example shows a simple appearance containing a red material.
<pre>
#X3D V3.0 utf8

PROFILE Interchange

Shape {
appearance Appearance {
material Material {
diffuseColor 1 0 0
}
}
geometry Box {}
}
</pre>

* [[Node Reference]]

X3DMetadataObject

2006-02-01T18:07:24Z

Giles:

==X3DMetadataObject==

<pre>
X3DMetadataObject {
SFString [in,out] name ""
SFString [in,out] reference ""
}
</pre>

This abstract interface is the basis for all metadata nodes. The interface is inherited by all metadata nodes.

The specification of the reference field is optional. If provided, it identifies the metadata standard or other specification that defines the name field. If the reference field is not provided or is empty, the meaning of the name field is considered implicit to the characters in the string

Box

2006-01-30T16:15:15Z

Giles:

*[[Node Reference]]
==Box==
<pre>
Box : X3DGeometryNode {
SFNode [in,out] metadata NULL [X3DMetadataObject]
SFVec3f [] size 2 2 2 (0,∞)
SFBool [] solid TRUE
}
</pre>

The Box node specifies a rectangular parallelepiped box centred at (0, 0, 0) in the local coordinate system and aligned with the local coordinate axes. By default, the box measures 2 units in each dimension, from -1 to +1. The size field specifies the extents of the box along the X-, Y-, and Z-axes respectively and each component value shall be greater than zero. Figure 1 illustrates the Box node.
<center>http://www.web3d.org/x3d/specifications/ISO-IEC-19775-X3DAbstractSpecification/Images/box.gif Figure 1 - Box node</center>

Textures are applied individually to each face of the box. On the front (+Z), back (-Z), right (+X), and left (-X) faces of the box, when viewed from the outside with the +Y-axis up, the texture is mapped onto each face with the same orientation as if the image were displayed normally in 2D. On the top face of the box (+Y), when viewed from above and looking down the Y-axis toward the origin with the -Z-axis as the view up direction, the texture is mapped onto the face with the same orientation as if the image were displayed normally in 2D. On the bottom face of the box (-Y), when viewed from below looking up the Y-axis toward the origin with the +Z-axis as the view up direction, the texture is mapped onto the face with the same orientation as if the image were displayed normally in 2D. TextureTransform affects the texture coordinates of the Box.

The solid field determines whether the box is visible when viewed from the inside.
==Authoring Tip==
The size of a box cannot be changed after its creation. In order to change its size you need to place it in a Transform node and change its scale field.
==Implementation Tip==
The size field is made initializeOnly so implementations can optimize memory and bus bandwidth under the covers. All instances with the same size can share the same geometry instance.
*[[Node Reference]]

Anchor

2006-01-27T21:15:12Z

Giles: Initial Entry

==Anchor==

<pre>Anchor : X3DGroupingNode {
MFNode [in] addChildren
MFNode [in] removeChildren
MFNode [in,out] children [] [X3DChildNode]
SFString [in,out] description ""
SFNode [in,out] metadata NULL [X3DMetadataObject]
MFString [in,out] parameter []
MFString [in,out] url [] [url or urn]
SFVec3f [] bboxCenter 0 0 0 (-∞,∞)
SFVec3f [] bboxSize -1 -1 -1 [0,∞) or −1 −1 −1
}

</pre>

The Anchor grouping node retrieves the content of a URL when the user activates
(e.g., clicks) some geometry contained within the Anchor node's children.
If the URL points to a valid X3D file, that world replaces the world of which
the Anchor node is a part (except when the parameter field, described
below, alters this behaviour). If non-X3D data is retrieved, the browser shall
determine how to handle that data; typically, it will be passed to an appropriate
non-X3D browser.

Exactly how a user activates geometry contained by the Anchor node depends
on the pointing device and is determined by the X3D browser. Typically, clicking
with the pointing device will result in the new scene replacing the current
scene. An Anchor node with an empty url does nothing when its children
are chosen. A description of how multiple Anchors and pointing-device sensors
are resolved on activation is contained in
<a href="pointingsensor.html#Concepts">20.2 Concepts.</a>

More details on the children, addChildren, and removeChildren
fields can be found in <a href="group.html#Concepts">10.2 Concepts</a>.

The description field in the Anchor node specifies a textual description
of the Anchor node. This may be used by browser-specific user interfaces that
wish to present users with more detailed information about the Anchor.

The parameter  field may be used to supply any additional information
to be interpreted by the browser. Each string shall consist of "keyword=value"
pairs. For example, some browsers allow the specification of a "target" for
a link to display a link in another part of an HTML document. The parameter
field is then:

<pre>Anchor {
parameter [ "target=name_of_frame" ];
...
}

</pre>

An Anchor node may be used to bind the initial Viewpoint node in a world by
specifying a URL ending with "#ViewpointName"
where "ViewpointName"
is the DEF name of a viewpoint defined in the X3D file.

EXAMPLE

<pre>Anchor {
url "http://www.school.edu/X3D/someScene.wrl#OverView";
children Shape { geometry Box {} };
}

</pre>

specifies an anchor that loads the X3D file "someScene.wrl" and binds
the initial user view to the Viewpoint node named "OverView" when
the Anchor node's geometry (Box) is activated. If the named Viewpoint node is
not found in the X3D file, the X3D file is loaded using the default Viewpoint
node binding stack rules (see <a href="navigation.html#Viewpoint">23.3.5
Viewpoint</a>).

If the url field is specified in the form "#ViewpointName"
(i.e. no file name), the Viewpoint node
with the given name ("ViewpointName")
in the Anchor's run-time name scope(s) shall
be bound (set_bind <code>TRUE</code>).
The results are undefined if there are multiple Viewpoints with the same name
in the Anchor's run-time name scope(s). The results are undefined if the Anchor
node is not part of any run-time name scope or is part of more than one run-time
name scope. See <a href="../concepts.html#Runtimenamescope">4.4.7 Run-time
name scope</a> for a description of run-time name scopes.
See <a href="navigation.html#Viewpoint">23.3.5 Viewpoint</a>, for the Viewpoint transition
rules that specify how browsers shall interpret the transition from the old
Viewpoint node to the new one. For example:

<pre>Anchor {
url "#Doorway";
children Shape { geometry Sphere {} };
}
</pre>

binds the viewer to the viewpoint defined by the "Doorway" viewpoint
in the current world when the sphere is activated. In this case, if the Viewpoint
is not found, no action occurs on activation.

More details on the url field are contained in
<a href="../concepts.html#URLs">9.2.1 URLs</a>.

The bboxCenter and bboxSize fields specify a bounding box that
encloses the Anchor's children. This is a hint that may be used for optimization
purposes. The results are undefined if the specified bounding box is smaller
than the actual bounding box of the children at any time. The default bboxSize
value, (-1, -1, -1), implies that the bounding box is not specified
and if needed shall be calculated by the browser. More details on the bboxCenter
and bboxSize fields can be found in <a href="group.html#Boundingboxes">

10.2.2 Bounding boxes</a>.

==Example==
<pre>
#X3D V3.0 utf8

PROFILE Immersive

Anchor {
description "A test anchor"
url ["anchor_dest.x3dv" ]
children [
Shape {
geometry Box {}
}
]
}
</pre>

Node Reference

2006-01-27T21:05:56Z

Giles: Changed to list

==List of Nodes==

*[[Anchor]]
*Appearance
*Arc2D
*ArcClose2D
*AudioClip
*Background
*Billboard
*BooleanFilter
*BooleanSequencer
*BooleanToggle
*BooleanTrigger
*Box
*CADAssembly
*CADFace
*CADLayer
*CADPart
*Circle2D
*Collision
*Color
*ColorInterpolator
*ColorRGBA
*Composed3DTexture
*ComposedCubeMapTexture
*ComposedShader
*Cone
*Contour2D
*ContourPolyline2D
*Coordinate
*CoordinateDouble
*CoordinateInterpolator
*CoordinateInterpolator2D
*Cylinder
*CylinderSensor
*DirectionalLight
*Disk2D
*ElevationGrid
*EspduTransform
*Extrusion
*FillProperties
*FloatVertexAttribute
*Fog
*FogCoordinate
*FontStyle
*GeneratedCubeMapTexture
*GeoCoordinate
*GeoElevationGrid
*GeoLocation
*GeoLOD
*GeoMetadata
*GeoOrigin
*GeoPositionInterpolator
*GeoTouchSensor
*GeoViewpoint
*Group
*HAnimDisplacer
*HAnimHumanoid
*HAnimJoint
*HAnimSegment
*HAnimSite
*Image3DTexture
*ImageCubeMapTexture
*ImageTexture
*IndexedFaceSet
*IndexedLineSet
*IndexedQuadSet
*IndexedTriangleFanSet
*IndexedTriangleSet
*IndexedTriangleStripSet
*Inline
*IntegerSequencer
*IntegerTrigger
*KeySensor
*LineProperties
*LineSet
*LoadSensor
*LocalFog
*LOD
*Material
*Matrix3VertexAttribute
*Matrix4VertexAttribute
*MetadataDouble
*MetadataFloat
*MetadataInteger
*MetadataSet
*MetadataString
*MovieTexture
*MultiTexture
*MultiTextureCoordinate
*MultiTextureTransform
*NavigationInfo
*Normal
*NormalInterpolator
*NurbsCurve
*NurbsCurve2D
*NurbsOrientationInterpolator
*NurbsPatchSurface
*NurbsPositionInterpolator
*NurbsSet
*NurbsSurfaceInterpolator
*NurbsSweptSurface
*NurbsSwungSurface
*NurbsTextureCoordinate
*NurbsTrimmedSurface
*OrientationInterpolator
*PackagedShader
*Pixel3DTexture
*PixelTexture
*PlaneSensor
*PointLight
*PointSet
*Polyline2D
*Polypoint2D
*PositionInterpolator
*PositionInterpolator2D
*ProgramShader
*ProtoInstance
*ProximitySensor
*QuadSet
*ReceiverPdu
*Rectangle2D
*ScalarInterpolator
*Script
*ShaderPart
*ShaderProgram
*Shape
*SignalPdu
*Sound
*Sphere
*SphereSensor
*SpotLight
*StaticGroup
*StringSensor
*Switch
*Text
*TextureBackground
*TextureCoordinate
*TextureCoordinate3D
*TextureCoordinate4D
*TextureCoordinateGenerator
*TextureMatrixTransform
*TextureTransform
*TextureTransform3D
*TimeSensor
*TimeTrigger
*TouchSensor
*Transform
*TransmitterPdu
*TriangleFanSet
*TriangleSet
*TriangleSet2D
*TriangleStripSet
*Viewpoint
*VisibilitySensor
*WorldInfo

Anchor

2006-01-27T21:05:37Z

Giles:

Convert VRML97 To X3D

2005-11-20T18:39:12Z

Giles:

== Convert VRML97 To X3D ==
This article documents how to convert a VRML97 file to a VRML Classic Encoding X3D file.

'''Change the header from #VRML V2.0 utf8 to:'''

<nowiki>#X3D V3.0 utf8</nowiki>

'''Add a profile statement:'''

PROFILE Immersive

=== Scripting ===
This section details how to convert scripting.

'''Change field declarations from eventIn, field, exposedField, eventOut to:'''

inputOnly, initializeOnly, inputOutput, outputOnly

==== Ecmascript ====
This section shows details on converting vrmlscript/javascript scripts to ecmascript.

'''Change vrmlscript/javascript scripts to ecmascript, url "javascript:" becomes:'''

url "ecmascript:"

'''Change methods to properties'''
Functions like Browser.getCurrentFrameRate() are now ecmascript properties. So they become Browser.currentFrameRate

Other functions that have changed are:
#getName() became '''name'''
#getVersion() became '''version'''
#getCurrentSpeed() became '''currentSpeed'''
#getCurrentFrameRate() became '''currentFrameRate'''
#createVrmlFromString() became '''createX3DFromString'''
#createVrmlFromURL() became '''createX3DFromURL'''
#setDescription() became '''description'''

Some functions have moved from the Browser object to the X3DExecutionContext object:
#addRoute() is now '''Browser.currentScene.addRoute()
#removeRoute() is now '''Browser.currentScene.removeRoute()
#createVrmlFromString is now '''createX3DFromString'''
#getWorldURL() became '''worldURL'''

==== Java ====
Java scripting will need to be converted to the new SAI interfaces. A more detailed writeup of this process will follow.

How-To Guides

2005-11-20T18:16:41Z

Giles:

== How-To Guides ==

* [[ConvertVRML97 To X3D]]

Main Page

2005-11-20T18:14:37Z

Giles: /* Public X3D Wiki Usage Guidelines */

== Public X3D Wiki Usage Guidelines ==
* [[Usage Guidelines]]

== How-To Guides ==
* [[How-To Guides]]