[x3d-public] What should this file display (for the experts)?
roy.walmsley at ntlworld.com
Tue May 31 08:24:38 PDT 2016
Thanks for your observations. I too agree that this file should display
three green boxes lined up along the x axis. This is what my own viewer
based on a development X3D extension to Coin3D shows. Similarly, after a
couple of bug fixes, I get the same with the JSON-encoded file.
Both the XML and the JSON encoded files pass the relevant Schema validation.
My own code loads and displays without any errors. I believe the file, in
either encoding, is valid X3D.
I also saw, along with John, the varied display from different players.
Hence we decided to publicize this file as a fairly simple test file
demonstrating nested prototypes.
From: x3d-public [mailto:x3d-public-bounces at web3d.org] On Behalf Of Vincent
Sent: 31 May 2016 16:07
To: John Carlson; X3D Graphics public mailing list
Subject: Re: [x3d-public] What should this file display (for the experts)?
I am not an expert in the PROTO-X side of X3d, but to me it looks like the
correct rendering would be 3 green cubes lined up along the x axis. This is
what InstantPlayer shows after I capitalized the names of the Proto related
nodes ( anyShape --> AnyShape ; three --> Three ). I don't know if this is a
requirement of the standard, but the error messages in the InstantPlayer
console indicated that the original naming generated warnings.
I have attached a copy of the file with the new names.
I still, however, see three cylinders in BS Contact and in view3dscene. The
rendering of three cylinders to me indicates that the myShape field of the
ProtoInstance node is not being set to the green box as declared in the
ProtoInstance node, but is falling back to the default cylinder as specified
in the 'three' ProtoDeclare node.
I note the Xj3D is not rendering anything, and one feature of the Xj3D is
that it demands close compliance to the standard. However, I cannot get the
validator to run in the X3D-Edit Netbeans plugin, and the online validator
appears to be offline right now. It is plausible that a naming or syntax
error is preventing some browsers from instantiating the Protoinstance as
intended, while InstantReality was written to accept some errors and in this
case got it 'right'
More information about the x3d-public