[x3d-public] Discussion from the X3D WG Meeting Nov 30 2018

[Andreas Plesch]

Great summary. Let me just add to my comment where I mentioned three.js.
Three does import glTF into its own representations and scene graph. The
internals of the imported glTF scene become fully accessible if needed.
This is made easier because the glTF binary data are already similar to
three data. For example, it also has a BufferGeometry object. It also has a
PhysicalMaterial.

Andreas



>
> Message: 1
> Date: Fri, 7 Dec 2018 12:33:39 -0500
> From: "vmarchetti at kshell.com" <vmarchetti at kshell.com>
> To: X3D-Public <x3d-public at web3d.org>
> Subject: [x3d-public] Discussion from the X3D WG Meeting Nov 30 2018
> Message-ID: <0CACC0A4-8232-4129-8862-2FAE1096A9BB at kshell.com>
> Content-Type: text/plain;       charset=utf-8
>
> Discussion on X3D WG Meeting on glTF and X3D Specification
>
> Attending Michalis Kamburelis. Dick Puk, Vince Marchetti, Nicholas Polys
>
> Supporting Material:
> X3d-public mailing list
> http://web3d.org/pipermail/x3d-public_web3d.org/2018-November/009594.html
> http://web3d.org/pipermail/x3d-public_web3d.org/2018-November/009594.html
>
>         ? Plesch Nov 20:
> But the fact of the matter is that it is used increasingly as an exchange
> and
> asset format (there are many exporters and importers). It is also the
> case that many/most importers translate glTF into their native data
> structures first, due to convenience (three.js does that, for example)
> before uploading to the GPU
>
>
>
> Michalis:
> X3D needs PBR
> PBR is the only coloring mechanism in core glTF2
> Others available only as extensions.
>
> X3D should have a mesh-efficient node [ compatible with glTD ]
>
> Can have one one mesh with Phong shading, one with PBR: This is possible
> with shaders. Graphic artists will say this is incorrect.
>
>
> PABI:
> Proposal: Implement a ?PhysicalMaterial? node which will substitute for
> the Material node as a field of the Appearance node
>
> Approach: Implemented as a code extension to open source browswe (X3DOM,
> X_ITE, Xj3D)
>
>
> Example:
> Proposal: Implement a ?gltFMesh? node which acts as a Geometry node
> similar to TriangleSet, but as URL field to retrieve glTF or glb  content.
>
> Approach : Direct implementation in as an open source extension fo x3dom
> code, potentially to be added to X3DOM master code
>
> Benefits: Faster, smaller downloads, transmission of mesh-like geometry.
>
> Proposal: Implement ?Image Based Lighting? node, ?Physical Light Source?,
> related to the cube map.
>
>
> Indeed. If we have
>
> - BufferGeometry (node that can be placed in "Shape.geometry",
> compatible with glTF mesh)
> - PhysicalMaterial (node that can be placed in "Appearance.material",
> compatible with glTF material using PBR)
> - EnvironmentLight (to cast light as a cubemap, hopefully useful with
> both PBR PhysicalMaterial and Phong Material)
>
> ... then we're ready to easily import at least static glTF models in X3D.
>
> See also various notes from my [wiki]
>
> https://github.com/michaliskambi/x3d-tests/wiki/Include-PhysicalMaterial-and-PhysicalEnvironmentLight-in-the-official-X3D-specification
> :)
>
>
> Submitted Dec 7 2018
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
> ------------------------------
>
> End of x3d-public Digest, Vol 117, Issue 14
> *******************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20181212/530b6435/attachment.html>