<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">X_ITE supports the following extensions:<div><br></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">- KHR_materials_unlit implemented with PhysicalMaterial because of gamma correction.</span></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br></span></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">- </span><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">KHR_materials_emissive_strength - implemented by adding emissiveStrength field to X3DOneSidedMaterialNode.</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">- KHR_lights_punctual - mapped to Point/Spot/DirectonalLight</span></font><br style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><div><br></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">- KHR_texture_transform - mapped to X3D TextureTransform</span></div><div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br></span></div><div><font color="#000000">- KHR_materials_pbrSpecularGlossiness - not really supported, without a </font><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">SpecularGlossinessMaterial node there will be no real support, but PhysicalMaterial </span><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">is more straightforward.</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">Best regards,</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);">Holger</span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div> <br><blockquote type="cite"><div>Am 24.02.2023 um 19:15 schrieb Michalis Kamburelis <michalis.kambi@gmail.com>:</div><br class="Apple-interchange-newline"><div><div>From others:<br><br>1. Blender: they support a number of extensions at import and export:<br>https://docs.blender.org/manual/en/dev/addons/import_export/scene_gltf2.html#extensions<br><br>2. CGE supports ( https://castle-engine.io/gltf ):<br><br>- KHR_materials_unlit - unlit materials. This translates nicely to<br>X3D4 UnlitMaterial.<br><br>- KHR_lights_punctual - define lights (point, spot, directional)<br>within glTF file. These translate nicely to X3D lights (with unbounded<br>intensity in X3D4).<br><br>- KHR_texture_transform - transform (scale, offset, rotate) texture<br>coordinates. These translate to X3D texture coordinate transformation<br>nodes.<br><br>- KHR_materials_pbrSpecularGlossiness - support for alternative<br>specification of material parameters using specular-glossiness. Only<br>partial support — without textures. Extension considered deprecated by<br>Khronos in favor of KHR_materials_specular.<br><br>My most important plans:<br><br>- X3D nodes for binary meshes (I know X3DOM has this already) and then<br>KHR_draco_mesh_compression<br><br>- EnvironmentLight in X3D4, consistent with EXT_lights_image_based ,<br>KHR_lights_environment .<br><br>3. Everyone: As you see, there is a big overlap between all these<br>extension lists (X3DOM, Blender, CGE) and that's good :)<br><br>Some glTF extensions are quite popular and in practice supported by<br>all/most glTF viewers.<br><br>Regards,<br>Michalis<br><br>pt., 24 lut 2023 o 17:56 Andreas Plesch <andreasplesch@gmail.com> napisał(a):<br><blockquote type="cite"><br>On glTF extension below:<br><blockquote type="cite"><br>...<br>4. glTF Extensions.<br><br>Recent email threads have pointed out that X3D 4.0 normatively references<br>glTF 2.0. Meanwhile numerous glTF extensions are available. Nothing<br>prohibits X3D browsers/players/tools from going beyond baseline glTF 2.0 -<br>the "X" in X3D is Extensible. 8)<br><br>There is benefit to software developers, content authors and end users to<br>having a shared strategy on what new features to support. Considering and<br>supporting such a list is further suitable as a Web3D Recommendation as a<br>stepping stone towards future pursuit of X3D 4.1 with International<br>Standards Organization (ISO).<br></blockquote><br><br><blockquote type="cite"><br>Here are a few glTF extensions that have been proposed. Let's discuss which<br>have high value and deserve consideration as part of a shared strategy.<br><br><br><br>* EnvironmentLight<br>* emissiveColor bloom<br>* Draco geometry compression<br>* Human animation<br>* Others?<br><br></blockquote><br>x3dom supports a few extensions:<br><br>"KHR_materials_pbrSpecularGlossiness", (now deprecated and replaced by<br>KHR_materials_specular)<br>"KHR_materials_unlit",<br>"KHR_texture_transform"<br><br>Soon it will also support Draco decompression.<br><br>KHR prefixed extensions are sanctioned by Khronos.<br><br>Here is a complete list:<br><br>KHR_draco_mesh_compression<br>KHR_lights_punctual<br>KHR_materials_clearcoat<br>KHR_materials_emissive_strength<br>KHR_materials_ior<br>KHR_materials_iridescence<br>KHR_materials_sheen<br>KHR_materials_specular<br>KHR_materials_transmission<br>KHR_materials_unlit<br>KHR_materials_variants<br>KHR_materials_volume<br>KHR_mesh_quantization<br>KHR_texture_basisu<br>KHR_texture_transform<br>KHR_xmp_json_ld<br><br>KHR_lights_punctual may be feasible to support, and KHR_xmp_json_ld is<br>about metadata and also should be possible to translate to Metadata<br>nodes.<br><br>EXT_lights_image_based is a multi-vendor extension related to EnvironmentLight<br><br>-Andreas<br><br><br><blockquote type="cite"><br><br><br><br>5. X3D 4.1 feature discussion. (carried over from last week)<br><br><br><br>Many possibilities! The "X" in X3D is Extensible, so pursuit of further<br>evolution is an essential part of our design. We benefit from (but are not<br>limited by) ISO stability, since implementers can experiment with innovative<br>practices and also match Web3D Consortium recommended practices.<br><br><br><br>a. Near term: resolving Sound component differences with Web Audio API.<br>Some noted issues will likely get deferred as X3D 4.1 issues.<br>b. In progress: HAnim2/X3D4 additions for site names, poses, and<br>clothing to provide support for apparel.<br>c. What else? What's next?<br><br><br><br>Wishing best progress. Have fun with X3D! 8)<br><br><br><br>all the best, Don<br><br>--<br><br>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<br><br>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br><br>X3D graphics, virtual worlds, Navy robotics https://<br>faculty.nps.edu/brutzman<br><br><br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230224/a7f27407/attachment.html><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: smime.p7s<br>Type: application/pkcs7-signature<br>Size: 5353 bytes<br>Desc: not available<br>URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230224/a7f27407/attachment.p7s><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>x3d-public mailing list<br>x3d-public@web3d.org<br>http://web3d.org/mailman/listinfo/x3d-public_web3d.org<br><br><br>------------------------------<br><br>End of x3d-public Digest, Vol 167, Issue 76<br>*******************************************<br></blockquote><br><br><br>--<br>Andreas Plesch<br>Waltham, MA 02453<br><br>_______________________________________________<br>x3d-public mailing list<br>x3d-public@web3d.org<br>http://web3d.org/mailman/listinfo/x3d-public_web3d.org<br></blockquote><br>_______________________________________________<br>x3d-public mailing list<br>x3d-public@web3d.org<br>http://web3d.org/mailman/listinfo/x3d-public_web3d.org<br></div></div></blockquote></div><br></div></body></html>