<html 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 http-equiv=Content-Type content="text/html; charset=iso-8859-2"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></style></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Thanks for suggested improvements to FACTOR prose. I’ve applied this, we will review (and likely accept/resolve) during tomorrow morning’s regular X3D meeting.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We’re not accepting any functional changes (such as deprecation) at this stage. Possible for 4.1 of course. Am expecting that getting good rendering implementations available to everyone will encourage authors to apply some of these lesser-known techniques. Addition of glTF-rendering palette certainly helps too!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Doug and Michalis, your dedicated work to improve X3D4 specification is much appreciated. Thanks again. <o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>-- <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span> <span style='font-size:10.0pt;font-family:"Courier New"'>faculty.nps.edu/brutzman<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> x3d-public <x3d-public-bounces@web3d.org> <b>On Behalf Of </b>Michalis Kamburelis<br><b>Sent:</b> Thursday, June 16, 2022 9:47 AM<br><b>To:</b> GPU Group <gpugroup@gmail.com><br><b>Cc:</b> X3D Public Mailing List (x3d-public@web3d.org) <x3d-public@web3d.org><br><b>Subject:</b> Re: [x3d-public] [x3d] Spec Comment by on 19775-1: X3D Architecture - V4.0<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Nice idea for profiles :) <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>There is a "Full" profile of X3D already which for me roughly equates already to "Crazy Permutation Prototyping Profile".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>To be serious, I do not think that X3D spec should include everything possible for prototypes. This makes design hard, understanding (by authors, implementors) hard and actual implementations hard. X3D is already the biggest 3D spec (at least looking at open and semi-open specification formats -- looking mostly at X3D, glTF, Collada, Wavefront OBJ, STL) and it's kind of a problem. The (unfortunately somewhat correct) perception of X3D is that it is "everything and a kitchen sink" model format. Actually X3D is even a set of specifications ( <a href="https://www.web3d.org/standards" target="_blank">https://www.web3d.org/standards</a> ) and I think most practical implementations deal at least with 4 X3D specs (nodes, classic encoding, xml encoding, H-Anim for skinned animation). This is too much :)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Compare this to glTF, which is like "carefully chosen feature set of really important things, the rest is in extensions".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>You need to have some experience with X3D to actually realize that you don't really use these 150+ nodes from X3D spec in reality. Majority of X3D models are using like 10-20 of most common X3D nodes.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I believe the right solution is to be careful with what we put in spec, but at the same time encourage the extension process. This middle ground is actually used by OpenGL, glTF, and probably many others. It is <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- design a specification around the core important concepts<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- leave the uncertain things (uncertain whether they are useful, uncertain whether this format is the right place to define it etc.) to extensions. This also leads to "formalize" vendor-specific extensions a bit, this way vendors have a common place to talk about vendor-specific features and maybe easier reach consensus "hey, this makes sense, let's all do this".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>And then you drive the evolution of the standard by extensions. Extensions may be vendor-specific. Extensions may become "approved by central body (Web3D consortium -- well, in practice, people on this list)" -- which means "we reviewed it, it makes sense, we welcome implementors to test it. And finally extensions are the primary way to introduce new features to spec (this is how most of OpenGL evolution happened, I think; even ground-breaking additions, like shaders, started as just an extension at one point).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>And I think we're actually already somewhat doing it in X3D, just not in a formalized fashion. That is, most X3D browsers have a set of vendor-specific extensions, and they are documented. CGE, FreeWRL, X3DOM, X_ITE, InstantReality --- we all have our vendor-specific documentation of "X3D + our additions". And other browsers look at it, sometimes implement it too, and sometimes these things do get upgraded to core spec features. Or at least they inspire -- like CommonSurfaceShader from X3DOM/InstantReality, that in the end was *not* included in X3D 4, but instead we took ideas from it and transformed them to fit within "new Material in X3D 4".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>> Example I'm trying cubemaps to get regular texture treatment, including multitexturing, and (stretch) combining cubemaps with 2D textures in a multitexture. Why, where is the 'market demand'? There is none. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Actually for this specific case, there is a use :) The GeneratedCubeMapTexture is essentially a way to do mirrors (on curved objects). It makes sense to mix it with regular (base/diffuse) texture which is usually 2D. It's not physically correct to just multiply mirror into base/diffuse parameter like that, but it remains I think the easiest way to get cool-looking mirror effect. Like<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal>Shape {<br> appearance Appearance {<br> material Material {<o:p></o:p></p></div><div><p class=MsoNormal> diffuseTexture MultiTexture {<o:p></o:p></p></div><div><p class=MsoNormal> ImageTexture { url "..." }<o:p></o:p></p></div><div><p class=MsoNormal> GeneratedCubeMapTexture { update "ALWAYS" }<br> }<o:p></o:p></p></div><div><p class=MsoNormal> } <o:p></o:p></p></div><div><p class=MsoNormal> geometry Teapot {<br> texCoord MultiTextureCoordinate {<o:p></o:p></p></div><div><p class=MsoNormal> texCoord [<o:p></o:p></p></div><div><p class=MsoNormal> TextureCoordinate { ... set of 2D points ... }<br> TextureCoordinateGenerator { mode "WORLDSPACEREFLECTIONVECTOR" }<o:p></o:p></p></div><div><p class=MsoNormal> ]<o:p></o:p></p></div><div><p class=MsoNormal> }<br>}<o:p></o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Disclaimer:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- above is untested<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- I used there CGE extension WORLDSPACEREFLECTIONVECTOR, <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcastle-engine.io%2Fx3d_implementation_cubemaptexturing.php&data=05%7C01%7Cbrutzman%40nps.edu%7Cf63c2bc632174712206d08da4fb7f87b%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637909949723831121%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=WyDi6RzEUUg2uuWdQxupJZDluBRGLwOuP0Wv4Wo%2BhVA%3D&reserved=0" target="_blank">https://castle-engine.io/x3d_implementation_cubemaptexturing.php</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- there should be (or is?) probably a better way to do this, without MultiTexture. Because just multiplying mirror*normal diffuse is not really a correct solution.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Michalis<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>czw., 16 cze 2022 o 14:14 GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>> napisał(a):<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p class=MsoNormal>Thanks Michalis great someone knows openGL. <o:p></o:p></p><div><p class=MsoNormal>-Doug<o:p></o:p></p><div><p class=MsoNormal>deprecation > I see x3d as something for prototyping, so it would have some rarely-used-in-practice features, and allow crazy permutations, which game engine designers could try and pick the things they need for their game engine. Perhaps there could be a Game Engine Profile for things actually used at scale? Example I'm trying cubemaps to get regular texture treatment, including multitexturing, and (stretch) combining cubemaps with 2D textures in a multitexture. Why, where is the 'market demand'? There is none. Except clearing out special cases in the code makes it more general, more crazy permutations possible. Perhaps there could be a Crazy Permutation Prototyping Profile which still has full permutations of Multitexturing?<o:p></o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Thu, Jun 16, 2022 at 5:12 AM Michalis Kamburelis <<a href="mailto:michalis.kambi@gmail.com" target="_blank">michalis.kambi@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal>1. I interpreted the "FACTOR" in CGE/view3dscene just like FreeWRL. That is, "FACTOR" indicates to use MultiTexture.color / MultiTexture.alpha. I see I even call it "constant factor" in CGE/view3dscene code, to make a point that it is constant for the whole "execution" of this MultiTexture calculation.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I think this was invented to correspond to old fixed-function OpenGL "glTexEnvv(GL_TEXTURE_ENV, GL_TEXTURE_ENV_COLOR, ...)".<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I believe the spec should be fixed, the existing sentence indeed is incorrect, as there are no "factors at particular stages". <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal>The texture argument is the factor (color, alpha) from the texture provided for the current stage of the MultiTexture node.<o:p></o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal>The texture argument is the factor from MultiTexture node <i>color</i> and <i>alpha</i> fields.<o:p></o:p></p></div><div><p class=MsoNormal>"""<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>2. There's no alignment here with glTF -- glTF doesn't have MultiTexture. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>And, also because there are numerous problems with X3D MultiTexture unfixed for many years and it doesn't seem it is used by authors, I proposed in <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcastle-engine.io%2Fx3d_multi_texturing.php&data=05%7C01%7Cbrutzman%40nps.edu%7Cf63c2bc632174712206d08da4fb7f87b%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637909949723831121%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=pZjdj1uJB8NWoV%2FU1manN9jbWTsCnw%2FqXtG8U11XKg4%3D&reserved=0" target="_blank">https://castle-engine.io/x3d_multi_texturing.php</a> and <a href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmichaliskambi%2Fx3d-tests%2Fwiki%2FDeprecate-some-unused-and-badly-specified-MultiTexturing-specification-pieces&data=05%7C01%7Cbrutzman%40nps.edu%7Cf63c2bc632174712206d08da4fb7f87b%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C637909949723831121%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=DI1%2FfSql2qIqlQO6LGgHSLqPVeW%2BKjd1mI3xjsRfELQ%3D&reserved=0" target="_blank">https://github.com/michaliskambi/x3d-tests/wiki/Deprecate-some-unused-and-badly-specified-MultiTexturing-specification-pieces</a> that we just deprecate parts of it (leaving only some core functionality subset, to just sum and multiply textures).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Michalis<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>śr., 15 cze 2022 o 18:48 Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> napisał(a):<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks Doug… am not sure. Have shared with x3d-public for further scrutiny.<o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Michalis, when defining FACTOR, can we say things more clearly to ensure good alignment with glTF approaches?<o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>-- </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a></span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span> <span style='font-size:10.0pt;font-family:"Courier New"'><a href="http://faculty.nps.edu/brutzman" target="_blank">faculty.nps.edu/brutzman</a></span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;border-color:currentcolor currentcolor'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b> GPU Group <<a href="mailto:gpugroup@gmail.com" target="_blank">gpugroup@gmail.com</a>> <br><b>Sent:</b> Wednesday, June 15, 2022 9:28 AM<br><b>To:</b> Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>><br><b>Cc:</b> <a href="mailto:x3d@web3d.org" target="_blank">x3d@web3d.org</a><br><b>Subject:</b> Re: [x3d] Spec Comment by on 19775-1: X3D Architecture - V4.0<o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Sorry I was reading the committee draft, SELECT arg2 has been corrected in Draft International Standard. <o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>But the confusion on the other one, FACTOR is still there<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>in freewrl looks like we've been using Multitexture.color and .alpha when source is FACTOR.<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>And those values are provided once by Multitexture for all stages<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hypotheses:<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>H0: freewrl has been doing it wrong<o:p></o:p></p></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>H1: spec is unclear<o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 summary="" width=1155 style='width:866.2pt;border-collapse:collapse'><tr><td style='border:groove windowtext 3.0pt;padding:6.0pt 6.0pt 6.0pt 6.0pt'><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:13.5pt'><span style='font-size:9.0pt;font-family:"Courier New";color:black'>"FACTOR"</span><o:p></o:p></p></td><td style='border:groove windowtext 3.0pt;border-left:none;padding:6.0pt 6.0pt 6.0pt 6.0pt;border-color:currentcolor'><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:13.5pt'><span style='font-size:10.0pt;font-family:"Verdana",sans-serif;color:black'>The texture argument is the factor (color, alpha) from the texture provided for the current stage of the MultiTexture node.</span><o:p></o:p></p></td></tr></table></div></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Jun 14, 2022 at 2:35 PM Brutzman, Donald (Don) (CIV) <<a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid windowtext 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt;border-color:currentcolor currentcolor currentcolor rgb(204,204,204)'><div><div><p>Thanks Doug. Entered as Mantis 1397<o:p></o:p></p><p> <o:p></o:p></p><p>* Mantis 1397: Fix typo Table 18.3 — Multitexture values for mode field<o:p></o:p></p><p>* <a href="https://www.web3d.org/member-only/mantis/view.php?id=1397" target="_blank">https://www.web3d.org/member-only/mantis/view.php?id=1397</a><o:p></o:p></p><p>* <a href="https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/texturing.html#t-MultitextureModes" target="_blank">https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-CD1/Part01/components/texturing.html#t-MultitextureModes</a><o:p></o:p></p><p> <o:p></o:p></p><p>Change applied in git, ready for editor review/resolution (when Dick and I next get together). This should make it time for ISO DIS submission, they are currently reviewing figures prior to acceptance.<o:p></o:p></p><p> <o:p></o:p></p><p>all the best, Don<o:p></o:p></p><p>-- <o:p></o:p></p><p>Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><o:p></o:p></p><p>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></p><p>X3D graphics, virtual worlds, Navy robotics https:// <a href="http://faculty.nps.edu/brutzman" target="_blank">faculty.nps.edu/brutzman</a><o:p></o:p></p><p> <o:p></o:p></p><p>-----Original Message-----<br>From: x3d <<a href="mailto:x3d-bounces@web3d.org" target="_blank">x3d-bounces@web3d.org</a>> On Behalf Of Spec Feedback<br>Sent: Tuesday, June 14, 2022 1:15 PM<br>To: <a href="mailto:x3d@web3d.org" target="_blank">x3d@web3d.org</a><br>Subject: [x3d] Spec Comment by on 19775-1: X3D Architecture - V4.0<o:p></o:p></p><p> <o:p></o:p></p><p>-- Submitter indicates that this comment may be public: *Yes* --<o:p></o:p></p><p> <o:p></o:p></p><p>Comment on 19775-1: X3D Architecture - V4.0<o:p></o:p></p><p>18.4.3 MultiTexture<o:p></o:p></p><p><a href="https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#MultiTexture" target="_blank"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/documents/specifications/19775-1/V4.0/Part01/components/texturing.html#MultiTexture</span></a><o:p></o:p></p><p> <o:p></o:p></p><p>-----------------<o:p></o:p></p><p>"SELECTARG2" Use color argument 1<o:p></o:p></p><p>Arg2<o:p></o:p></p><p>should be<o:p></o:p></p><p>"SELECTARG2" Use color argument 2<o:p></o:p></p><p>Arg2<o:p></o:p></p><p>-----------------<o:p></o:p></p><p> <o:p></o:p></p><p>Submitted on Tuesday, 2022, June 14 - 1:15pm by (Doug Sanden )<o:p></o:p></p><p>IP: 23.17.48.2<o:p></o:p></p><p> <o:p></o:p></p><p>See: <a href="https://www.web3d.org/node/1694/submission/6179" target="_blank"><span style='color:windowtext;text-decoration:none'>https://www.web3d.org/node/1694/submission/6179</span></a><o:p></o:p></p><p> <o:p></o:p></p><p> <o:p></o:p></p><p>_______________________________________________<o:p></o:p></p><p>x3d mailing list<o:p></o:p></p><p><a href="mailto:x3d@web3d.org" target="_blank"><span style='color:windowtext;text-decoration:none'>x3d@web3d.org</span></a><o:p></o:p></p><p><a href="http://web3d.org/mailman/listinfo/x3d_web3d.org" target="_blank"><span style='color:windowtext;text-decoration:none'>http://web3d.org/mailman/listinfo/x3d_web3d.org</span></a><o:p></o:p></p></div></div></blockquote></div></div></div></div><p class=MsoNormal>_______________________________________________<br>x3d-public mailing list<br><a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><o:p></o:p></p></blockquote></div></blockquote></div><p class=MsoNormal>_______________________________________________<br>x3d-public mailing list<br><a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br><a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><o:p></o:p></p></blockquote></div></div></body></html>