X3D V4 Issue Examples
Submitted by Leonard Daly on Thu, 01/07/2016 - 20:58
This page is to illustrate the issues with X3D V3.x running in a browser.
See testing and development notes below,
| Title | Example | Code | Description | Status / Notes |
|---|---|---|---|---|
| Basic Scene | X3D X3DOM |
basicScene.x3d | Static scene of 4 geometric primatives. | Good - Displays correctly in all browsers |
| AnimatedBasic | X3D X3DOM |
animatedBasic.x3d | Basic scene with some keyframe animation | Good - Displays correctly in all browsers |
| DoubleInline | X3D X3DOM |
animatedBasic4.x3d doubleInline.x3d |
The same AnimatedBasic scene Inlined twice | Good - Displays correctly in all browsers |
| DoubleInline-Rate | X3D X3DOM |
animatedBasic4.x3d doubleInline-Rate.x3d |
The same animation using two different cycleIntervals | Good - Displays correctly in all browsers |
| TouchAnimation4 | X3D X3DOM |
touchAnimation4.x3d | Single AnimatedBasic controled by a TouchSensor | X3DOM does not correctly handle MouseOver. It does not recognize non-MouseOver when another object moves in front of the object with the sensor. |
| TouchAnimation-Rate | X3D X3DOM |
touchAnimation4.x3d touchAnimation-Rate.x3d |
Dual AnimatedBasic scenes each separately controlled by a TouchSensor | X3DOM same issue with MouseOver as TouchAnimation4. There is no cross-talk in any of the browsers |
| Script | X3D X3DOM |
controller.js scriptAnimation4.x3d script.x3d |
Double AnimatedBasic scenes separately interacting with an X3D Script | X3DOM fails because there is no Script node |
| Script-Rate | X3D X3DOM |
controller.js scriptAnimation4.x3d script-Rate.x3d |
Dual AnimatedBasic scenes each separately interacting with an X3D Script | X3DOM fails because there is no Script node. There is no cross-talk in any of the browsers. |
| Html | X3D (Not possible) X3DOM |
htmlAnimation.html htmlAnimation4.x3d |
Scene animation controlled by HTML elements | X3D supports this type of interaction; however, it is not publicly implemented in BS Contact. Interaction to the scene needs to go through the X3D API, not DOM API. |
Testing & Development Notes
- All examples use X3DOM V1.7.1.
- The X3D files were hand-built using a template from X3D-Edit and verified in BS Contact Geo B.205-9381L221-May.13.2014
- It is necessary to have an X3D browser installed in your web browser to properly see the X3D versions of these files.
- The X3DOM versions of these tests use an HTML file that Inline's the appropriate X3D file. There is no other X3D code in the HTML file.