<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=utf-8"><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.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@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="#954F72"><div class=WordSection1><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don, looked at sourceforge. Won’t extra CDATA sections be interpreted as shader code? Don’t you want <!--<span style='font-family:Wingdings'>à</span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>?</p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:brutzman@nps.edu">Don Brutzman</a><br><b>Sent: </b>Monday, April 24, 2017 12:56 PM<br><b>To: </b><a href="mailto:holger.seelig@yahoo.de">Holger Seelig</a>; <a href="mailto:yottzumm@gmail.com">yottzumm@gmail.com</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: Updated SimpleShader.x3d example</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>cc: list</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 4/21/2017 11:48 AM, Holger Seelig wrote:</p><p class=MsoNormal>> </p><p class=MsoNormal>> The example will now work with Cobweb. As the Appeareance »shaders« field can hold multiple shaders I added a second ComposedShader after the existing one for Cobweb.</p><p class=MsoNormal>> </p><p class=MsoNormal>> > http://www.web3d.org/x3d/content/examples/Basic/Shaders/SimpleShaderIndex.html</p><p class=MsoNormal>> [...]> Am 18.04.2017 um 11:35 schrieb yottzumm@gmail.com:</p><p class=MsoNormal>>> [...]</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> I don’t think this Cobweb version is working on the X3D examples website:</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> http://www.web3d.org/x3d/content/examples/Basic/Shaders/SimpleShaderIndex.html</p><p class=MsoNormal>>><o:p> </o:p></p><p class=MsoNormal>>> I think it may have something to do with some gl_ shader variables not</p><p class=MsoNormal>>> being available. Try replacing with x3d_ for cobweb, and declaring them</p><p class=MsoNormal>>> in the shader (I don’t think it will work otherwise, but I could be</p><p class=MsoNormal>>> wrong). You will probably have to provide modified shader code in</p><p class=MsoNormal>>> addition to the normal glsl shader. If providing an alternate URL for</p><p class=MsoNormal>>> cobweb will work, I would do it—I am unsure what would happen. We may</p><p class=MsoNormal>>> have to provide an alternate URL for each X3D vendor. Sigh!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for the improvements gentlemen. I've tuned this up a bit further (naming conventions, c14n canonicalization) and checked it in.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also "quoted" some of the MFString entries, where more than one string value was present, but we likely have more work to do there. Not yet runnable by me.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>X3D-Edit isn't handling ShaderPart url/script correctly, will work on that.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Latest shared version maintained online at:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>http://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/content/examples/Basic/Shaders</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/content/examples/Basic/Shaders/SimpleShader.x3d</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>