How can I monitor the performance of my XML3D application?

A nice way is to use the stats counter from: https://github.com/mrdoob/stats.js/

In the WebGL version, one can use the framedrawn event to update the counter, e.g:

var stats = new Stats(); stats.domElement.style.position=’absolute’; stats.domElement.style.left=’0px’; stats.domElement.style.top=’0px’; var targetElement = … targetElement.style.position=’realtive’; targetElement.appendChild(stats.domElement); var myxml3d = document.getElementById(“myxml3d”); myxml3d.addEventListener(“framedrawn”, function(e) { stats.update(); }, false);

In the native version, one . . . → Read More: How can I monitor the performance of my XML3D application?

Chromium XML3D updated

There is a new version of chromium-xml3d for Windows and Ubuntu available. Apart from several bugfixes (including XML3DRotation::toMatrix) the new version contains other changes, most notably:

Faster OpenGL rasterization on GPU (now it is the default) Most recent changes from the original Chromium project . . . → Read More: Chromium XML3D updated

XML3D Cinema4D exporter plug-in

In addition to our blender exporter, we now offer an XML3D exporter plug-in for Maxon’s Cinema4D R12. As usual it is available on github under the following URL: https://github.com/xml3d/Cinema4D-Exporter.

. . . → Read More: XML3D Cinema4D exporter plug-in

WebGL Best Practice

If you intend to create XML3D scenes that also run with WebGL, it’s necessary to follow some basic rules:

Add the necessary JS scripts in the header section of the XHTML document: <script src=”http://www.xml3d.org/xml3d/script/xml3d.js” type=”text/javascript”/>

This should be the first script reference in the header section. If you want to be able to run the . . . → Read More: WebGL Best Practice

How to get started with XML3D

Here are some easy steps to get started with XML3D! . . . → Read More: How to get started with XML3D