<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-2">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1191914487;
mso-list-type:hybrid;
mso-list-template-ids:-344007272 -156056882 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:16;
mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoPlainText>Michalis, apologies our mail crossed. Thanks for excellent and thorough explanation.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Am keen to keep things aligned as you and Holger (two leading implementers) think best.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Wondering: are there any further clarifications to add to specification, preventing ambiguous interpretation? For example, perhaps adding a sentence:<o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>X3D4, Texturing component, 18.2.3 Texture coordinates<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-DIS/Part01/components/texturing.html#TextureCoordinates<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>“<span style='background:yellow;mso-highlight:yellow'>Texture coordinates are reapplied or else recomputed (if initially NULL) whenever the corresponding vertex-based geometry changes</span>.”<o:p></o:p></li></ul><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Also wondering: might precomputation and addition of texture coordinates be an option in your converter? Given continued inconsistencies of Blender export to X3D, this might be especially helpful as we try to achieve consistent X3D browser rendering for advanced HAnim skin examples. If that is possible, Joe and I will be happy to update texture coordinates and test relevant X3D HumanoidAnimation example models accordingly.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>Castle Game Engine: Convert everything to X3D<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>https://castle-engine.io/convert.php<o:p></o:p></li></ul><p class=MsoPlainText><o:p> </o:p></p><ul style='margin-top:0in' type=disc><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>HumanoidAnimation (HAnim) X3D Examples Archive<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>https://www.web3d.org/x3d/content/examples/HumanoidAnimation<o:p></o:p></li></ul><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>all the best, Don<o:p></o:p></p><p class=MsoPlainText>-- <o:p></o:p></p><p class=MsoPlainText>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></p><p class=MsoPlainText>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p class=MsoPlainText>X3D graphics, virtual worlds, Navy robotics https:// faculty.nps.edu/brutzman<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-----Original Message-----<br>From: x3d-public <x3d-public-bounces@web3d.org> On Behalf Of Michalis Kamburelis<br>Sent: Wednesday, January 4, 2023 8:00 AM<br>To: Holger Seelig <holger.seelig@yahoo.de><br>Cc: X3D <x3d-public@web3d.org><br>Subject: Re: [x3d-public] X3DCanvas vs x3d-canvas, X_ITE - conversion stylesheet results</p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>view3dscene and Castle Game Engine recompute the texture coordinates at runtime, potentially each frame. Which, as I understand, is also what X_ITE does. Testing with latest view3dscene (https://castle-engine.io/view3dscene.php), our results match X_ITE on <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeSkeletonSkinSiteSaluteWalkX_ITE.html"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeSkeletonSkinSiteSaluteWalkX_ITE.html</span></a><o:p></o:p></p><p class=MsoPlainText>.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>In short I think that<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- view3dscene, Castle Game Engine and X_ITE are all correct with respect to spec here. We had this discussion 11 years ago already (see thread "Announcement: view3dscene 3.8.0" in your MUAs). From what I recall, back then I also confirmed that InstantReality on desktop also recalculates texture coordinates. But BS Contact did it differently.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- I think this is a sensible behavior in general, see below why. I see it doesn't match what Joe expected in this case, but IMHO the resolution is just "you should assign texture coordinates explicitly if you want them to stick, i.e. use TextureCoordinate".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Details:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The texture generation based on bbox is treated by view3dscene/CGE as just an implicit use of TextureCoordinateGenerator, with mode="BOUNDS", see<o:p></o:p></p><p class=MsoPlainText>https://castle-engine.io/x3d_implementation_texturing_extensions.php#section_ext_tex_coord_bounds. And TextureCoordinateGenerator can change coordinates at each frame.<o:p></o:p></p><p class=MsoPlainText>The idea is that such texture generation can be done on GPU, right at rendering, so yes -- it can change each frame and this is a feature.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If you want the texture coordinates to stay unchanged, then just generate texture coordinates in your authoring tool. This is a normal workflow in my experience, artists routinely UV unwrap and assign textures this way to characters. 3D artists do not really depend on automatic texture generation at all in my experience, they also assign texture coordinates explicitly in Blender or such.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I'm not saying this is some final decision, but I'm saying this ("texture generation happens each frame, and may be done on GPU right at rendering") is how I understood the X3D spec and I think it makes sense. This way texture generation in X3D is a nice feature for some use-cases (if model is static, or if you want the texture to "flow").<o:p></o:p></p><p class=MsoPlainText>If you want the texture to "stick", then you should just assign texture coordinates in 3D authoring tool, like in normal 3D workflow.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If we really want to (but I would discourage from it) we could change X3D spec to have a different behavior, but in this case the X3D spec would really have to be precise *when* should texture generation to be recomputed (at start? and/or caused by some input events?), how it is related to TextureCoordinateGenerator. Holger in last mail raised correct points -- they are some moments when you *have* to recompute the coordinates (like when number of points changes) anyway. Trying to specify when to recompute, and when not to recompute, feels like a "Pandora's box". Better to follow what we have now, and just say "they can be recomputed at each frame".<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So making the texture generation only at certain moments<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- is an additional work for X3D browsers, where they cannot use GPU (easily),<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- is a work that duplicates what typically 3D authoring tools, like Blender, are doing.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- you want the texture to stick -> map texture in Blender,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>- you want the texture to move -> rely on X3D texture generation at runtime.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Regards,<o:p></o:p></p><p class=MsoPlainText>Michalis<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>śr., 4 sty 2023 o 16:35 Holger Seelig <<a href="mailto:holger.seelig@yahoo.de"><span style='color:windowtext;text-decoration:none'>holger.seelig@yahoo.de</span></a>> napisał(a):<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Hi Joe, but this is not what spec say, reading it strictly. Your approach has some caveats. The text coords should be calculated once. But what happens when the number of coords changes, or the num triangles or quads, or polygons. It is no more easy to determine when the tex coords should be regenerated.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Holger<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Am 04.01.2023 um 16:06 schrieb Joseph D Williams <<a href="mailto:joedwil@earthlink.net"><span style='color:windowtext;text-decoration:none'>joedwil@earthlink.net</span></a>>:<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> >> "The longest dimension of the bounding box defines the S coordinates, and the next longest defines the T coordinates."<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Hi Holger, I certainly agree with this, but not during animation. We would use the default mapping once, for the default pose, then the same after animation begins. Again, the way it is showing is a neat effect, but not realistic, since the texture should stay mapped to the default pose, not recomputed at each frame.<o:p></o:p></p><p class=MsoPlainText>> Thanks,<o:p></o:p></p><p class=MsoPlainText>> Joe<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> From: Holger Seelig<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, January 3, 2023 3:15 AM<o:p></o:p></p><p class=MsoPlainText>> To: X3D<o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [x3d-public] X3DCanvas vs x3d-canvas,X_ITE - conversion <o:p></o:p></p><p class=MsoPlainText>> stylesheet results<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> X_ITE does exactly what is documented here <a href="https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/geometry3D.html#f-IndexedFaceSettextureDefaultMapping"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/geometry3D.html#f-IndexedFaceSettextureDefaultMapping</span></a> to automatically calculate tex coords.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> >> "The longest dimension of the bounding box defines the S coordinates, and the next longest defines the T coordinates."<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> In your example the longest dimension is as we can see the Y-axis, but <o:p></o:p></p><p class=MsoPlainText>> the next longest dimension will change when the IFS is animated, <o:p></o:p></p><p class=MsoPlainText>> sometimes it is the X-axis and sometimes it is the Z-axis. (You can <o:p></o:p></p><p class=MsoPlainText>> see a flip)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Second, because the IFS is animated the tex coords will always change. <o:p></o:p></p><p class=MsoPlainText>> (You see the texture moving)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Here are the lines how X_ITE does the calc: <o:p></o:p></p><p class=MsoPlainText>> https://github.com/create3000/x_ite/blob/ad74f5212dae83c436bf0fc25eb4ac471301ae50/src/x_ite/Components/Rendering/X3DGeometryNode.js#L357<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Please have a look at it. I cannot find a bug.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Best regards,<o:p></o:p></p><p class=MsoPlainText>> Holger<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Am 02.01.2023 um 18:58 schrieb Joseph D Williams <<a href="mailto:joedwil@earthlink.net"><span style='color:windowtext;text-decoration:none'>joedwil@earthlink.net</span></a>>:<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Humanoid Animation X3D Examples Archive, Skin, Joe Skeleton Skin Site <o:p></o:p></p><p class=MsoPlainText>> Salute Walk (web3d.org)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Notice how skin moves around with animations.<o:p></o:p></p><p class=MsoPlainText>> I still think this is because browser does not honor textCoords, Do I need to make a change to get thisto work right when it works correctly in others. As I recall from past, xite doesn’t autogenerate texcoords and needs repeat for every point?<o:p></o:p></p><p class=MsoPlainText>> Thanks,<o:p></o:p></p><p class=MsoPlainText>> Joe<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> From: Brutzman, Donald (Don) (CIV)<o:p></o:p></p><p class=MsoPlainText>> Sent: Saturday, December 31, 2022 2:42 PM<o:p></o:p></p><p class=MsoPlainText>> To: Holger Seelig<o:p></o:p></p><p class=MsoPlainText>> Cc: X3D<o:p></o:p></p><p class=MsoPlainText>> Subject: Re: [x3d-public] X3DCanvas vs x3d-canvas,X_ITE - conversion <o:p></o:p></p><p class=MsoPlainText>> stylesheet results<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> [related topic: upgrading "X3D to X_ITE" stylesheet, to match your <o:p></o:p></p><p class=MsoPlainText>> announcement]<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Holger, thanks for all of the amazing work that you continue to accomplish.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> After finishing much other work, I’ve finally been able to update the (newly renamed) X3dToX3domX_ITE.xslt stylesheet to support your use of <x3d-canvas> element.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Apologies for delays reaching this point. The new version of X_ITE looks good!<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Hoping that you can confirm I’m using your publishing patterns correctly. Might you please check HTML/CSS source for the following developmental example. If there are better ways of doing things please advise.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> X3D Example Archives: Humanoid Animation, Skin, Joe Skeleton Skin Site <o:p></o:p></p><p class=MsoPlainText>> Salute Walk <o:p></o:p></p><p class=MsoPlainText>> <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS</span></a><o:p></o:p></p><p class=MsoPlainText>> keletonSkinSiteSaluteWalkIndex.html<o:p></o:p></p><p class=MsoPlainText>> <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS</span></a><o:p></o:p></p><p class=MsoPlainText>> keletonSkinSiteSaluteWalkX_ITE.html<o:p></o:p></p><p class=MsoPlainText>> <a href="https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Skin/JoeS</span></a><o:p></o:p></p><p class=MsoPlainText>> keletonSkinSiteSaluteWalk_X_ITE.png<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> One thing I was not able to figure out… if you unzoom the JoeSkeletonSkinSiteSaluteWalkX_ITE.html page (using 4-arrow button in upper left) there is space for X_ITE Console, to appear as before in prior version. However this feature is no longer working. Am happy to correct it, or omit it, as appropriate.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> <div><o:p></o:p></p><p class=MsoPlainText>> <h3>X_ITE Console</h3><o:p></o:p></p><p class=MsoPlainText>> <p class="x_ite-console"/><o:p></o:p></p><p class=MsoPlainText>> </div><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Hmm, reviewing: another thing is that the stylesheet link is still there but without apparent harm. Will try removing that later.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Having fun with X_ITE, X3D and HTML5! 8)<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> all the best, Don<o:p></o:p></p><p class=MsoPlainText>> --<o:p></o:p></p><p class=MsoPlainText>> Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu"><span style='color:windowtext;text-decoration:none'>brutzman@nps.edu</span></a><o:p></o:p></p><p class=MsoPlainText>> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p class=MsoPlainText>> X3D graphics, virtual worlds, Navy robotics https:// <o:p></o:p></p><p class=MsoPlainText>> faculty.nps.edu/brutzman<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> -----Original Message-----<o:p></o:p></p><p class=MsoPlainText>> From: x3d-public <<a href="mailto:x3d-public-bounces@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public-bounces@web3d.org</span></a>> On Behalf Of Holger <o:p></o:p></p><p class=MsoPlainText>> Seelig<o:p></o:p></p><p class=MsoPlainText>> Sent: Tuesday, November 1, 2022 8:04 AM<o:p></o:p></p><p class=MsoPlainText>> To: X3D <<a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a>><o:p></o:p></p><p class=MsoPlainText>> Subject: [x3d-public] X3DCanvas vs x3d-canvas, X_ITE<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> With version 6.0.0, X_ITE uses the new element name <x3d-canvas>, lowercase and with dash. Because X_ITE uses the Custom Element API from JavaScript now. This has the advantages that the element can be created with document.createElement, and is then immediately ready to use :). Other advantage is that the CSS file must not be included anymore.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> For compatibility the old name can still be used, but we encourage all users to update to the new tag name.<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> Best regards,<o:p></o:p></p><p class=MsoPlainText>> Holger<o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> x3d-public mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"><span style='color:windowtext;text-decoration:none'>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>><o:p> </o:p></p><p class=MsoPlainText>> _______________________________________________<o:p></o:p></p><p class=MsoPlainText>> x3d-public mailing list<o:p></o:p></p><p class=MsoPlainText>> <a href="mailto:x3d-public@web3d.org"><span style='color:windowtext;text-decoration:none'>x3d-public@web3d.org</span></a><o:p></o:p></p><p class=MsoPlainText>> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org"><span style='color:windowtext;text-decoration:none'>http://web3d.org/mailman/listinfo/x3d-public_web3d.org</span></a><o:p></o:p></p></div></body></html>