[x3d-public] How is a shader chosen in X_ITE? Looks like it works (at least at first, and then disappears?)

[Holger Seelig]

I investigated your code further and it now turns out that you have an error in you JavaScript which controls the camera. You do

orientation_changed[0] = new SFRotation(orientations[ov].x, orientations[ov].y, orientations[ov].z, orientations[ov].w);
orientation_changed[1] = new SFRotation(orientations[vc].x, orientations[vc].y, orientations[vc].z, orientations[vc].w);

But orientations are a MFRotation, that means accessing orientations[vc].w will fail, because there is no '.w‘ property, instead SFRotations have a ‚.angle‘ property. Because orientations[vc] returns a SFRotation you can do:

orientation_changed[0] = orientations[ov];
orientation_changed[1] = orientations[vc];

Best regards, Holger.

> Am 04.07.2021 um 08:21 schrieb John Carlson <yottzumm at gmail.com>:
> 
> Handy shortcut for X3DJSONLD devs (install x3dvalidate first): X3DJSONLD/src/main/schema$ node ~/x3dvalidate/x3dvalidate.js ../data/bubbles.json
> 
> Loading schema
> Parsing schema
> Adding schema
> Schema 4.0 added
> Schema 4.0 compiled
> Success reading ../data/bubbles.json
> 
> Starting X3D-Edit 4.0...
> 
> Opening bubbles.x3d...
> 
> Clicking the checkbox...
> 
> Fixed one error...
> 
> Clicking the checkbox again...
> 
> --------- X3D Validator checks commenced for bubbles.x3d ---------
> 
> Performing well-formed XML check...
> Checking file:/home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d <file:///home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d>...
> Well-formed XML check: pass
> 
> Performing DOCTYPE check...
> [X3dDoctypeChecker] success: valid XML declaration found.[X3dDoctypeChecker] success: final X3D 4.0 DOCTYPE found.
> 
> Performing DTD validation...
> Checking file:/home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d <file:///home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d>...
> XML DTD validation: pass
> 
> Performing X3D schema validation...
> Checking file:/home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d <file:///home/coderextreme/X3DJSONLD/src/main/data/bubbles.x3d>...
> XML schema validation: pass
> 
> Performing X3D regular expression (regex) values check...
> 
> Performing X3dToClassicVrml.xslt conversion check...
> 
> Performing X3D Schematron check...
> X3D version 4.0 is approved by Web3D Consortium and focused on interoperabiliity with HTML, glTF Physically Based Rendering (PBR) and Web Audio API, undergoing review by ISO national bodies in 2021. [/X3D, diagnostic]
> 
> --------- X3D Validator checks complete for bubbles.x3d ---------
> --------- X3D Validator online at https://savage.nps.edu/X3dValidator <https://savage.nps.edu/X3dValidator> --------- (Definitely *offline* here!  Thanks to the team that put X3D-Edit together, we have a backup!) 
> 
> 
> 
> Removed "Texture" from containerFields. New file attached.  No difference seen yet.  Sometimes the scene pops up then disappears, and sometimes it doesn't.
> 
> Looking at logs may tell the story. I haven't looked recently.
> 
> Note: x3dom shaders have been commented out locally, but file may still be cached.
> 
> Note:  X3D JSON validator is up and running for X3DV4!  https://coderextreme.net/X3DJSONLD/src/main/html/validator.html <https://coderextreme.net/X3DJSONLD/src/main/html/validator.html>
> Looks like savage.nps.edu website is down?
> 
> John
> 
> 
> 
> On 7/3/21 10:49 PM, John Carlson wrote:
>> X_ITE has disappearing problems with 
>> 
>> https://coderextreme.net/X3DJSONLD/src/main/html/bubbles.html <https://coderextreme.net/X3DJSONLD/src/main/html/bubbles.html> 
>> 
>> The included ../data/bubbles.x3d should be cross-platform--potentially any X3D browser, but only X3DOM and X_ITE are supported.  Please try yours and contribute fixes! 
>> 
>> Problems: scene and geometry show up initially, then disappear, or don't appear at all. I will try removing X3DOM shaders to see what happens. 
>> 
>> There's a small "flower" in the middle of the bubble in Chromium on Linux, which seems to indicated that a fragment shader got invoked which is returns white frag_color. If associated vertex shader doesn't load, I don't think the fragment shader shouldn't, IMO, but others can weigh in.  Others can report seeing this? 
>> 
>> I will try to go over the shaders with a fine-tooth comb tomorrow. 
>> 
>> I'll also run the XML file through validators! 
>> 
>> John 
>> 
> <bubbles.x3d>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20210704/cbddfc52/attachment.html>