We are happy to announce the release of X3DOM 1.8.3! This release contains a handful of new features and improvements along with a number of bug fixes since the last release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project.
For a detailed list of changes see the changelog on Github.

New Features

• Add basic support for webXR
• Add support for PointProperties
• Add support for glTF draco extension
• Add support for EXPORT/IMPORT statements
• Add bboxDisplay field for X3DBoundedObject and x3dom custom fields bboxMargin and bboxColor

Fixes and Enhancements

• Automatic sortType based on auto texture channel count
• MovieTexture: autostart, ios and removal
• Support url field change for AudioClip
• Better indices for textured IFS with creases
• Ensure correct children order after ExternProto instancing
• Allow smooth creaseAngle during coord updates for IFS
• and more…

Get It!

Grab the frozen 1.8.3 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are happy to announce the release of X3DOM 1.8.2! This release contains a handful of new features, improvements along with a number of bug fixes since the last release.
We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project.
For a detailed list of changes see the changelog on Github.

New Features

• New Exploration Modes.
• Experimental support for X3D prototypes.
• Added X3D 4.0 support for visible field, enhanced viewpoint options and Point Properties and cylinder/code options.
• Automatic origChannelCount detection.
• New NPM based build system.

Fixes and Enhancements

• Improved support for shadow & transparency on text.
• Animation improvements for shapes and viewpoints and play controls.
• Improved event and TouchSensor support.
• Improved support for addition / removal of nodes from the tree.
• Replaced deprecated MutationEvents with a MutationObserver.
• Make it possible to run x3dom in strict mode.
• Text node improvements.
• More robust collisions in walk mode.

Changes

• Remove support for compressed BinGeo files & Zlib.
• Remove support for ImageGeometry.
• Remove support for MultiPart.
• Remove support for ExternalShape/ExternalGeo and glTF 1.0.
• Remove support for loading single components.

Get It!

Grab the frozen 1.8.2 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are happy to announce our new X3DOM 1.8.1 Release. This release mainly contains fixes and corrections since the last 1.8.0 release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project.

Fixes, Improvements, Changes

• TextureCoordinateGenerator COORD mode
• Re-enable x3dom-log text selection.
• Fix for Debug-Log: ‘v’-key does not display ‘fieldOfView’.
• Background fixes
• enable Nurbs texCoord field
• various example fixes
• more robust shader parsing
• allow queued ComposedShader url loading
• ComposedShader fixes for VR
• PixelTexture parsing

Get It!

Grab the frozen 1.8.1 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are really happy to announce our special 10 Year anniversary release of X3DOM! This release contains multiple new Features, many new Nodes and a big list of fixes, improvements and changes.

We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project over last ten years!

New Features

• WebGL 2.0 support
• glTF 2.0 support (Example)
• Physically-based materials & lighting
• WebVR integration
• Nurbs support
• HAnim CPU skinning
• and much more …

Fixes & enhancements

• Improved caching
• Bounding box fixes
• Documentation Updates
• and many more fixes and enhancements by the X3DOM core team and the X3DOM community.

The full changelog can be found here.

Get It!

Grab the frozen 1.8.0 version here. The cutting-edge development version (nightly build of git head) can be found here.

As every year, we are happy to announce our special Christmas release of X3DOM! This release mainly contains fixes and corrections since the last release, but also improvements and fundamental changes.

We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project since so many years!

New Features

• Secure X3DOM delivery over HTTPS
• Added basic glTF Binary (GLB) support to the ExternalShape-Node [Example] (thanks to: skluge)
• New GeoLOD-Node (thanks to: andreasplesh)

Fixes, Improvements and Changes

• New RequestManager for all X3DOM related downloads
• Stopped Flash support and removed the Flash-backend
• General Navigation and Turntable improvements (thanks to: skluge)
• Exposed canvas event handlers (thanks to: DimitarIlievCenterMine)
• Added compatibility with python 3 and 2 for manage.py (thanks to: aarbelaiz)
• Many small fixes and enhancements by the X3DOM core team and the X3DOM community.

Get It!

Grab the frozen 1.7.2 version here. The cutting-edge development version (nightly build of git head) can be found here.

As a special holiday gift, we are happy to announce the release of X3DOM 1.7.1! This release mainly contains fixes and corrections since the last 1.7.0 release. We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project.

New Features

• Compressed Texture Support (Thanks to girier-tsha)
• Integration of the Mapbox Earcut library for better polygon triangulation (Thanks to andreasplesch)
• DepthMappedVolumeStyle Node + DepthMap Support (Thanks to ankit1089 and xperien)

Fixes and Improvements

• Improved text quality (Thanks to andreasplesch)
• Move the ammo.js from x3dom-full.js to the new x3dom-full-physics.js to reduce the download size.
• many small fixes and enhancements by the X3DOM core team and the X3DOM community.

Grab the frozen 1.7.1 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are proud and glad to announce the release of X3DOM 1.7 – as always, thanks to all contributors that made this great achievement possible!

Besides our new, fresh home page, these are the most important changes:

• CommonSurfaceShader now also supports object-space normal maps (in addition to already available tangent-space normal maps) – demo here
• ExternalGeometry node now has a multi-field for the data URL (of type MFString), multiple URLs can be specified as fallback. This is fully backwards compatible with old scenes that specify only a single string.
• Basic TriangleSet implementation, interesting for testing non-indexed rendering (thanks to Yvonne Jung, Fulda University of Applied Sciences)
• alphaClipThreshold attribute in Appearance node to adapt the threshold for X3DOM’s alpha test (for textures with transparency)
• Improvements in geospatial components (support for easting_first, thanks to Andreas Plesch, Harvard University).
• If a viewpoint gets transformed, its center of rotation now gets transformed accordingly (thanks to Andreas Plesch, Harvard University).
• Runtime documentation made available (see here)
• New tutorial about runtime configuration (see here)
• New tutorial about the experimental SSAO implementation (see here)
• Some smaller documentation updates
• Several fixes (thanks to Ander Arbelaiz, Andreas Plesch and Yvonne Jung)

As a special holiday gift, we are happy to announce the release of X3DOM 1.6.2! We would like to thank all users and, of course, all the contributors, that make X3DOM such a great project.

New Features

• Add SplinePositionInterpolator
  Thanks to ankit1089, Toshiba Corporation
  Example here

• Simple SSAO implementation
  Thanks to simonthum and fbrandherm
  Example here
  Tutorial upcoming here

Fixes and Enhancements

• Runtime Documentation updated and new screenshot tutorial

• Many VolumeRendering improvements
  Thanks to aarbelaiz from Vicomtech

• Many Geospatial improvements
  Thanks to andreasplesch from Harvard University, Department of Earth and Planetary Sciences

•  CORS improvements
  Thanks to sharian

• … plus a lot of smaller fixes and enhancements by the X3DOM core team and the X3DOM community 

Grab the frozen 1.6.2 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are proud to announce a 1.6.1 release of X3DOM. This release mainly contains some new features, fixes and corrections since the last 1.6 release. It is a maintenance update and recommended for all 1.6 users.

Features

• ClipPlane support
  • Example available here and documentation here

• TwoSidedMaterial support
  • Example available here and documentation here

• SphereSensor support
  • Documentation available here

Fixes and Enhancements

• Improved GeoOrigin support
• Multi-touch support for TURNTABLE navigation
• Fixed shader removing from appearance
• Moved fog application to the correct place
• Fixed ElevationGrid setAttribute
• Increase X3D compliance: don’t encode urls at sight
• Fixed calculation of bounding box for Flash backend
• Added fog to the Flash backend
• Fixed normal transformation for the Flash backend
• Fixed the check for enabled double-click
• and more…

Grab the frozen 1.6.1 version here. The cutting-edge development version (nightly build of git head) can be found here.

This month, X3DOM celebrates its 4th anniversary!
As a little “present”, we are proud to announce a 1.5.1 release of X3DOM. This release mainly contains fixes and corrections since the last 1.5 release. It is a maintenance update and recommended for all 1.5 users.

Most notable are the fixed bind behavior for transformed Viewpoint nodes, Viewfrustum matrix corrections, basic multi-touch support for other navigation types than examine, two new navigation modes, a beta version of DepthMode, BlendMode and ColorMaskMode, better normal map support in CommonSurfaceShader (if the “OES_standard_derivatives” extension is available), and last but not least support for 32-bit indices given that the new “OES_element_index_uint” extension is available. For a detailed list of changes please also refer to the CHANGELOG file.

Grab the frozen 1.5.1 version here. The cutting-edge development version (nightly build of git head) can be found here.

We are proud to announce the release of X3DOM 1.5. This most recent installment of our popular Declarative3D polyfill shines with lots of new features and a wagon load full of bugfixes.

With version 1.5, X3DOM also overcomes some limits of the scenegraph structure by using new internal structures for culling and fast rendering, decoupled from the frontend graph inside the DOM, which, however, still remains intact as usual.

New Features

• Generally improved traversal and rendering performance with a new transformation and volume caching infrastructure
• Culling techniques for large model rendering (some of them still experimental) – check the video, or see the tutorial
• Improved experimental binary geometry container and encoding
  • BinaryGeometry with more compact encoding that only uses 7 Bytes per triangle (see example) and works nicely on mobile devices
  • POPGeometry for progressive streaming and LOD – see the paper and project page here, or directly check some examples
• Experimental BVH Refiner node, for rendering of large, regular data sets with dynamic LOD (see tutorial and example)
• Shadow support for large scenes and all lights types (see tutorial for more information or click here or here for a demo)
• Convenience object ‘Moveable’ for object manipulation
• Additional X3D component plugins (not part of the HTML profile, i.e. not part of the x3dom.js package)
  • CADGeometry component
  • Geometry3DExt component (ElevationGrid and Extrusion, missing level 4 nodes)

Fixes and Improvements

• Many internal improvements and bugfixes
  
• DOM/Scene update improvements (e.g Route removal implemented)
• Improved picking functionality to enhance trade-off between precision and number of possible ids
• Fullscreen convenience method x3dom.toggleFullScreen()
• RenderedTexture extensions for rendering normal buffer or stereo (currently only for Oculus Rift)

For a detailed list of changes refer to the CHANGELOG file.

Grab the frozen 1.5.0 version here or fly with the cutting-edge development version here.

We have started a new project for online model conversion, which can be found on GitHub, too. It is an 3D model optimization and sharing service especially for the cultural heritage domain. The system is written in Python and allows optimization and conversion of 3D models for Web presentation and sharing these models on the Web. Its main features are:

• Upload and conversion of 3D Models to X3DOM
• Sharing of models on the web (permalinks to converted models)
• Downloadable ZIP packages of converted models
• Triangular Mesh optimization of models
• Converted/Optimized models can be embedded in different templates
• Asynchronous process
• Server-Sent Events for fast status updates
• Upload archives with many models and textures at once

This project was supported by V-Must, an EU-funded project that aims to provide the heritage sector with the tools and support to develop Virtual Museums that are educational, enjoyable, long-lasting, and easy to maintain. The developed code is open-source and you can just grab it from GitHub, where you also find everything to get started.

So finally: 1 day before christmas we did it!

Here is our next stable release after half a year of development

• Version 1.3 of the X3DOM Framework

We have worked on bug fixing and added some new features!

General work we did

• Our participation at the W3C was officially launched.
• We have moved from SF to GIThub.
• We have added some unit tests.
• We have renewed our documentation and added some tutorials.
• We have added component support for X3DOM to hold the core tight and allow (non-)standardized extensions.

Bug fixes & new Features

• We worked much at our flash render backend. After Flash 11 was been released we now can make use of a non beta API and for this, which has made this implementation more stable.
• #9: There is now <x3d src=’foo.x3d’ /> tag support. This allows integration of 3D content like native images. But be careful, this will only work in a client/server environment due the fact that we have to use the XMLHttpRequest functionality.
• #15, #33, #50: We have redesigned our multitouch support. It now works on iOS devices and multitouch setups with Mozilla. For Android and Firefox there seem to be some bugs in the android implementation and this should work only after these bugs are closed.
• #16, #27: We worked on the WebGL-backend, reducing the shader complexity to run on mobile hardware. The shaders are now chosen using a cabs-like system.
• #38: We have added support for billboards.
• #41: We have redesigned our build system.
• #45: We have implemented functionality for reflecting inlined scenes into the namespace of parent scenes. With this it is now possible to access elements from the parent scene to address elements within the inlined scene. Due to the lack of supporting such a concept in the X3D and HTML standard we have made use of a custom extension (see field nameSpaceName).
• #51: We also implemented functionality for inline support in a flash render setup.
• #56: We added support for the the <param> tag. This allows to parameterize the framework at a single point.
• We have extended our triangulation code for generating triangles out of concave geometry.

New components

With the new component model in X3DOM we have added the first two components, not natively included in our core profile

• The 2D primitive support for the use of elements like rectangles, discs, lines, …
• And finally we have started to support some geo referencing elements from the X3D specification.

We wish you all a merry christmas, a happy new year and that we all make use of our good intentions.

After many months of work, we’re proud to announce the release today of X3DOM 1.2. There’s plenty of cool stuff we have worked on since the last release. You can also swing by the downloads page to grab a copy of the release package.

Major Feature: Flash11/MoleHill Render backend

The new version supports an additional render-backend. The system now looks for a Flash11 plugin if the browser does not provide a SAI-Plugin or WebGL interface. This enables the user to view X3DOM pages, with some restrictions, using the Internet Explorer 9 browser. It utilizes the Adobe Flash MoleHill 3D-API for GPU-Accelerated rendering. To use Adobe Flash-based X3DOM you need the latest Adobe Flash Player Incubator build (11.01.3d).

Our x3dom.swf must either be placed in the same folder as your xhtml/html files, or you can specify a path with the swfpath-Parameter of the X3D-Node. With the X3D-Nodes backend-Parameter you can set Flash as default backend.

• At the moment the Flash-backend is still in an early beta state with most of base nodes working.
• Special features like multiple lights, shadows, CommonSurfaceShader, etc. are being worked on

Additional Changes

• Internal reorganization of sources. Node type have now their own submodule (src/nodes) and are split into groups.
• Text node is partially working now. You can use any font available to the browser. This includes WebFonts of CSS3.
• Added system to pass parameters to runtime. The use attributes with the X3D element will be deprecated in 1.3. Currently supported parameters
• Partially working MT support with on Firefox beta. Experimental.
• It is now possible to directly apply CSS styles to the X3D element.
• Fixed display problem with textures which have dimensions not to the power of two.

Second stable release after almost 7 month.

http://x3dom.org/x3dom/release/x3dom-v1.1.js

Features

Most features from the 1.1. milestone are implemented:

• Unified HTML/XHTML encoding
• HTML5 <canvas>, <img> and <video> as texture element supported
• CSS 3D Transforms
• Shader composition framework
• multiple lights and support for Spot-, Point- and DirectionalLight
• Fog
• LOD
• Support for large meshes
• Improved normal generation
• Follower component

WebGL compatibility

Recently there have been several changes in the WebGL-API (e.g. interface changes in texImage2D() method, replacement of old WebGL array types with the new TypedArray specification, enforcement of precision modifiers in shader code, and changed behavior of NPOT textures). This leads to incompatibilities with previous versions, why the 1.0 X3DOM release does no longer work together with recent browser versions.

HTML Profile

The proposed HTML profile is almost implemented:

Nodes and Components

Fallback model

The fallback-model has changed a bit. We partially support X3D-SAI plugins now and removed O3D as technology.

Next Release

Next release (V1.2) will focus on faster and better basic picking and collision methods to get more HTML-Events and the missing navigation modes (FLY, WALK, LOOKAT).

First stable release of the framework.

http://x3dom.org/x3dom/release/x3dom-v1.0.js

All initially planned features are implemented:

• HTML / XHTML Support
• Monitoring of DOM element add/remove and attribute change
• JS-Scenegraph synchronizer
• ROUTEs
• DEF/USE support
• External Subtree (via X3D Inline)
• Image (Texture), Movie (Texture) and Sound (Emitter) support
• Navigation: Examine
• WebGL Render backend

The proposed HTML profile is partially implemented:

Nodes and Components

The fallback-model is also only partially implemented:

Next release (v1.1) will focus on the following topics:

• WebSG (Web Scene-graph, minimal GLSL-shader based profile)
• CSS updates
• Bindable stack and camera animation
• Navigation: Walk, Fly and Examine
• More Lights/Light-Types