If you use textures, BinaryGeometry, Inline nodes etc., please make sure to test your scenes with a local server. As a workaround you can also disable all web security mechanisms in your browser. How to do it is described here: http://x3dom.org/docs/dev/notes/cors.html#developing-locally Chrome users please see this screenshot: [img]http://x3dom.org/temp/chrome.png[/img].
2013-03-15 10:59:56 PDT in x3dom
BinaryGeometry created with the saI or sac option only supports texCoords in [0,1]. So, if you have texCoords outside this range use the sa option instead.
2013-03-15 10:51:10 PDT in x3dom
You need at least IE 9.
2013-01-29 02:36:24 PST in x3dom
Hi, you cannot use self-closing tags in .html, this only works in .xhtml. Therefore, you indeed always have to write a close tag, since otherwise the Browser doesn't correctly parse your file. Hence, this behavior is as expected...
2013-01-23 13:42:44 PST in x3dom
Here is a little example with a similar problem: http://x3dom.org/x3dom/example/x3dom_uiEvents.html.
2013-01-06 01:57:06 PST in x3dom
Brightness mainly depends on the Material properties, probably diffuse/specularColor have too high values.
2012-12-15 00:49:27 PST in x3dom
When the viewpoint is bound once, then nothing changes, see x3d spec. Instead call the x3dom runtime method resetView().
2012-12-10 12:43:10 PST in x3dom
Hi, the reload approach is only for replacing complete x3d scenes -- see my comment in the corresponding issue. However, there was a bug in the update system which is fixed now. So, please try again (with the latest dev version) -- changing the geometry should work now.
2012-12-09 07:08:06 PST in x3dom