Activity for John W Carlson
-
John W Carlson posted a comment on ticket #84
Thanks for the great efforts, I will download the stylesheets soon. Yay! John On Thu, Feb 19, 2026 at 11:59 PM Don Brutzman brutzman@users.sourceforge.net wrote: The problem is that X3dToJson.xslt was not handling these as SFNode types. Now fixed. Excerpt: <xsl:variable name="SFNodeType" select=" ($fieldName = 'acousticProperties') or ($fieldName = 'baseTexture') or ($fieldName = 'emissiveTexture') or ($fieldName = 'normalTexture') or ($fieldName = 'occlusionTexture') or ($fieldName = 'metallicRoughnessTexture')...
-
Sure, -acousticProperties is an SFNode (JSON object), but X3dToJson.xslt treats it as an MFNode (JSON array). If you look at the online JSON object (I saved a snippet before for you to look at--pardon the bolding), you will see that it;'s an MFNode. Please remove the [] around the property value for the property name "-acousticProperties", such that the property value becomes an object, and not an array. What it should look like: { "Shape": { "-geometry": { "Box": { } }, "-appearance": { "Appearance":...
-
Just got your email. Thanks. Please close when ready. John On Thu, Feb 19, 2026 at 11:11 AM Don Brutzman brutzman@users.sourceforge.net wrote: I located and added the missing type assignment of SFNode for AcousticPropertis in X3dToJson.xslt stylesheet. Now converting correctly. Thanks for noting this issue. - https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound/AllAudioGraphNodesTest.json https://www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/AudioSpatialSound/AllAudioGraphNodesTest.json...
-
Can we do the same thing for this that we did for #51, -acousticProperties? Change X3dToJson.xslt. See online example that is wrong. This: "-baseTexture":[ { "ImageTexture": { [snip] } } ], [ should become ] "-baseTexture": { "ImageTexture": { [snip] } } ======================
-
Can we do the same thing for this that we did for #51, -acousticProperties? Change X3dToJson.xslt. See online example that is wrong. This: "-baseTexture":[ { "ImageTexture": { [snip] } } ], ================================= Should become this: ~~~ "-baseTexture": { "ImageTexture": { [snip] } } ~~~ ======================
-
PhysicalMaterial.baseTexture should be an object in JSON, not an JSON array
-
Can we do the same thing for this that we did for #51, -acousticProperties? Change X3dToJson.xslt. See online example that is wrong. This: "-baseTexture": { "ImageTexture": { [snip } } ], ================================= Should become this: "-baseTexture": { "ImageTexture": { [snip] } } ======================
-
-acousticProperties should be a JSON object, not a JSON array in X3D JSON
-
Can we get this looked at sooner than later? This is delaying acceptance testing of x3dvalidate.
-
I think you're assuming that X3DJSAIL jar isn't in a folder called X3DJSAIL. If it is in a folder alled X3DJSAIL, it won't be able to find the jar? IDK
-
I think you're assuming that X3DJSAIL isn't in a folder X3DJSAIL. If it is in a folder, X3DJSAIL, it won't be able to find the jar? IDK
-
ERROR_CONFIGURATION_X3DJSAIL X3DJSAIL .jar archive X3DJSAIL/4.0-full/X3DJSAIL-4.0-full.jar not found in
-
I'm sure you are aware of these use cases, even though it appears in a Legacy folder, or just in my code: `<MetadataSet containerField='metadata' name='warnings' reference='HAnim'> <!-- TODO experimental --> <MetadataString containerField='value' name='SymmetricalLeftRight' reference='correction options: ignore, warn, average, left, right, largest, smallest' value='"ignore"'/> </MetadataSet> <Shape DEF='AxisLinesShape'> <!-- RGB lines showing XYZ axes --> <IndexedLineSet colorIndex='0 1 2' colorPerVertex='false'...
-
I'm sure you are aware of these use cases, even though it appears in a Legacy folder, or just in my code: ~~~ `<metadataset containerfield="metadata" name="warnings" reference="HAnim"> <metadatastring containerfield="value" name="SymmetricalLeftRight" reference="correction options: ignore, warn, average, left, right, largest, smallest" value=""ignore""> </metadatastring></metadataset> <shape def="AxisLinesShape"> <indexedlineset colorindex="0 1 2" colorpervertex="false" coordindex="0 1 -1 0 2 -1...
-
I'm sure you are aware of these use cases, even though it appears in a Legacy folder, or just in my code: `<MetadataSet containerField='metadata' name='warnings' reference='HAnim'> <!-- TODO experimental --> <MetadataString containerField='value' name='SymmetricalLeftRight' reference='correction options: ignore, warn, average, left, right, largest, smallest' value='"ignore"'/> </MetadataSet> <shape def="AxisLinesShape"> <indexedlineset colorindex="0 1 2" colorpervertex="false" coordindex="0 1 -1...
-
I'm sure you are aware of these use cases, even though it appears in a Legacy folder, or just in my code: `<MetadataSet containerField='metadata' name='warnings' reference='HAnim'> <!-- TODO experimental --> <MetadataString containerField='value' name='SymmetricalLeftRight' reference='correction options: ignore, warn, average, left, right, largest, smallest' value='"ignore"'/> </MetadataSet> <shape def="AxisLinesShape"> <indexedlineset colorindex="0 1 2" colorpervertex="false" coordindex="0 1 -1...
-
Yes, I was able to verify that the X3dToPython.xslt version worked. I will work towards putting DEF/USE as a constructor parameter. This seems to fix the problem in one case. John On Sun, Feb 8, 2026 at 11:30 AM Don Brutzman brutzman@users.sourceforge.net wrote: There is not a problem with x3d.py Here are two examples showing Python programming with CoordinateInterpolator and CoordinateInterpolator2D - https://www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter07EventAnimationInterpolation/DolphinMorpherIndex.html...
-
This seems like a half decent solution.
-
It's got something to do with the DEF. When I take out the DEF from the Interpolators, I do get key and keyValue. Hmm
-
It's got something to do with the DEF. When I take out the DEF from the Interpolators, I do get key or keyValue. Hmm
-
It's got something to do with the DEF. When I take out the DEF from the Interpolators, I don't get key or keyValue. Hmm
-
For example, interp2.py, attached, works.
-
Here's a fairly short program that shows the issue. Feel free to truncate the keyValue a bit.
-
I've been looking at x3d.py. Nothing pops out.
-
This also fails: $ grep Interpolator flipp.py|cut -c1-100 ScalarInterpolator23 = x3d.ScalarInterpolator(key=[], keyValue=[]) ScalarInterpolator23.DEF = "si" ScalarInterpolator23.key = [0,0.5,1] ScalarInterpolator23.keyValue = [0,1,0] Scene9.children.append(ScalarInterpolator23) CoordinateInterpolator24 = x3d.CoordinateInterpolator(key=[], keyValue=[]) CoordinateInterpolator24.DEF = "ci" CoordinateInterpolator24.key = [0,0.5,1] CoordinateInterpolator24.keyValue = [(-23.495, 90.55, -8.13),(-28.825,...
-
Apparently, this is an invalid way to specify an Interpolator in X3DPSAIL Python app code
-
Apparently, this is an invalid way to specify an Interpolator in X3DPSAIL Python app code
-
Can we push the priority of this up? Thanks!
-
Suggestion is to upgrade the JSON in the archive, to match current X3dToJson.xslt
-
Suggestion is to upgrad ethe JSON in the archive, to match current X3dToJson.xslt
-
Please check carfully the number of DEF= in .x3d versus number of @DEF in JSON
-
Please check carfully the number of DEF= in .x3d versus number of @DEF in JSON
-
Closing, can't duplicate current.
-
Please check carfully the number of DEF= in .x3d versus number of @DEF in JSON
-
Unit test succeeded, performing wider test.
-
x3d.py issue, PixelTexture has no len()
-
texture is an MFNode. I don't know what happens if self.texture is None. This appears to be the problem in my PythonSerializer.js. I am not treating texture as an MFNode! Appearance30.material = Material31 MultiTexture32 = x3d.MultiTexture() MultiTexture32.alpha = 0.8 MultiTexture32.color = [0.9,1,0.2] MultiTexture32.function = ["COMPLEMENT","ALPHAREPLICATE"] MultiTexture32.mode = ["MODULATE","REPLACE","BLENDDIFFUSEALPHA"] MultiTexture32.source = ["DIFFUSE","SPECULAR","FACTOR"] """add multiple texture...
-
Again, no issue with Archive or x3d.py that I know of. I will try to troubleshoot
-
x3d.py issue, PixelTexture has no len()
-
Here's the X3D file I am using:
-
x3d.py issue, PixelTexture has no len()
-
Change http: to https: in X3DPSAIL, x3d.py
-
Another NavigationInfo.type issue
-
Another NavigationInfo.type issue
-
Okay. Here are the examples. I am not pleased yet, and more can be done likely, but I'm going to move on from this for a while.
-
I have given up on the SAXParser as entirely unworkable, and instead provide the Java code. I will provide inputs and outputs in another message. Please review inputs and outputs to see if they meet goals. We should discuss whether spaces should be maintained in single comments output.
-
i am nearly ready to provide more examples in a zip, if needed. I realize this is low priority. It would be good for me to proceed now than later. I am dropping a link here for a reminder. https://github.com/coderextreme/X3DJSONLD/blob/master/src/main/java/comments.sh One thing to do would be to work on buffers instead of standard input and standard output.
-
HAnimPose.py syntax error mismatched ]
-
PhysicalMaterial.baseTexture should be an object in JSON, not an array
-
Here are sample inputs and outputs. I believe these are as expected, except perhaps space preservation in comments, which is likely easily fixed. I can try to come up with more examples as well.
-
I have given up on the SAXParser as entirely unworkable, and instead provide the Java code. I will proved inputs and outputs in another message. Please review inputs and outputs to see if they meet goals. We should discuss whether spaces should be maintained in single comments output.
-
Here's the motivating example, which can be confirmed to work with X3dToPython.xslt (eventually).
-
Replacing Multiline comments with single line comments in Java. Open Source donation
-
Yes, that’s why I filed the ticket! I will try to file a different one that runs in Sunrize without issues. I don’t know if other errors affect schematron or not, I was trying to address the schematron ones, particularly related to Sphere not being in a Shape (legal, I think). If this is better handled by x3d-public, great! John On Sun, Dec 28, 2025 at 10:53 PM Don Brutzman brutzman@users.sourceforge.net wrote: Testing in X3D-Edit X3D Validator reveals error centered on The content of element type...
-
I agree that your ticket captures one aspect of Comment instances, but I fear it doesn’t capture the multi-line aspect of .x3d comments, hence the python output from X3dToPython.xslt will still be invalid from valid .x3d files with multi-line comments.
-
It’s also way too easy to go into an online example and remove a comment, invalidating any error report I have. So I will try to provide actual python and .x3d attachments, in addition to links. Then you can compare online stuff with my attachments. It’s natural for me to provide attachments, but if you provide ways to use stylesheets on links, I’ll go with that. I don’t actually know if X3DJSAIL takes links for conversions or validation. If you’re concerned about me putting strange nodes into .x3d...
-
Yes, the example was intended to run in FreeWRL, that’s why you got shader errors in Sunrize. fw = FreeWRL. John On Sun, Dec 28, 2025 at 10:41 PM Don Brutzman brutzman@users.sourceforge.net wrote: Testing in Sunrize renders nicely but throws many errors. Welcome to X_ITE X3D Browser v12.2.3: Welcome to Sunrize X3D Editor v1.11.15. Couldn't load URL ' https://coderextreme.net/X3DJSONLD/src/main/shaders/freewrl.vs' of ShaderPart. Error: Error in ShaderPart '' in URL ' https://coderextreme.net/X3DJSONLD/src/main/shaders/freewrl.vs',...
-
It’s summarized at the bottom of the ticket. There was a missing DOCTYPE, potentially caused by network errors and blocking on XML Schema on non-web3d sites. I believe the missing DOCTYPE has been fixed, but potential for network blocking when running batch tests still exists. Recommendation is to host all files locally, if possible. John On Sun, Dec 28, 2025 at 10:58 PM Don Brutzman brutzman@users.sourceforge.net wrote: Sorry but this ticket is too complex, and still does not identify a specific...
-
A simple check for “orientationinterpolator” in the attached example doesn’t show any results, as I expected. So if you don’t actually check the files I attach, why should I even attach them???? The reason to attach examples is to provide durability in error reporting, providing links doesn’t show the error. Many people on GitHub require attachments to issues, instead of links. I will continue providing links in hopes that you will look at them. I fully realize that NetBeans can be really crappy...
-
Oh, one more thing, I was debugging an HAnim model at one point in the past and discovered that there was a bug in Java’s Pattern class on particularly long strings or patterns. I think it was a stack overflow hidden by a try/catch. So adding log statements to the catch blocks may reveal that bug again. I believe this is your best bet for finding the issue now. John On Sun, Dec 28, 2025 at 11:33 PM John Carlson yottzumm@gmail.com wrote: Thanks for sleuthing this, Don. My first instinct is to wonder...
-
The point is that “<orientationinterpolator” is not legal Python. If you fixed comments, that works for me. John On Sun, Dec 28, 2025 at 10:35 PM Don Brutzman brutzman@users.sourceforge.net wrote: "orientationinterpolator" is not a legal node name and thus throws errors. Attaching file JinLOA4.x3d is not very helpful, since the current master version might get updated and is always part of the X3D Examples Archive at - https://www.web3d.org/x3d/content/examples/HumanoidAnimation/Characters/JinLOA4Index.html...
-
Thanks for sleuthing this, Don. My first instinct is to wonder if the number of coordinate numbers is properly divisible by 2 or 3. Another thought is that the index fields may extend beyond the *Coordinate points. Since the models pass X3D-Edit, which is likely battle tested, perhaps adding logging to X3DJSAIL temporarily will help elucidate where the issue is. I do like using the GHD of last resort (Got Here Debugger). That was how I found the “final” issue a few months ago. Thanks for pursuing...
-
Don, it doesn’t help to look at the XML/HTML generated by sourceforge from the ticket, you have to look at the attached file. I believe this error was caused by converting a comment to a Python comment. I recommend using a comment class like you do in X3DJSAIL, so we can roundtrip comments. Thanks, John On Sun, Dec 28, 2025 at 10:35 PM Don Brutzman brutzman@users.sourceforge.net wrote: "orientationinterpolator" is not a legal node name and thus throws errors. Attaching file JinLOA4.x3d is not very...
-
Cc’ing Joe. I’m guessing this might be caused by a missing DOCTYPE, but I haven’t investigated it. That’s my go to now for brutzman emails appearing in the log. I’m guessing this model comes out of my HAnimUtilityKit examples, so I can create an alternate, but smaller example with JinLOA1.x3d or similar. But I don’t recall if I still use Layer/LayerSet with those examples. When the missing DOCTYPE example shows up, I start suspecting XML generated by python’s XML output packages (not X3DPSAIL). John...
-
X3D file produces bad python
-
X3DJSAIL converts to Python incorrectly
-
X3D file produces bad python
-
X3D file produces bad python
-
At the time were the words I was looking for. John On Mon, Nov 24, 2025 at 2:36 AM Don Brutzman brutzman@users.sourceforge.net wrote: At the time of the entry, X3D 4.0 was experimental. The W3C Validator remains retired, so there is nothing to fix. [tickets:#78] https://sourceforge.net/p/x3d/tickets/78/ X3D 4.0 schema experimental? Status: open Milestone: X3D4 Created: Mon Nov 24, 2025 03:28 AM UTC by John W Carlson Last Updated: Mon Nov 24, 2025 03:28 AM UTC Owner: Don Brutzman this text looks dated?...
-
Errors in X3D-Edit QA? UniversalJoint
-
note that I took this example as the correct was to do things <balljoint def="PJ_hanim_l_hip" body1="RB_hanim_sacrum" body2="RB_hanim_l_thigh" anchorpoint="0.0961 0.9124 -0.0001"></balljoint> The other way to do it requires USE if RigidBodys are referenced twice. What I plan to do is use use USE for body1, assuming I can use a containerField='body1' with USE. Maybe I'll do that with body2 as well and put the RigidBodys in the collections in the bodies field (done). closing for now
-
X3D 4.0 schema experimental?
-
Note that X3D DTD doesn’t have body1 and body2 : https://www.web3d.org/specifications/X3dDoctypeDocumentation4.0.html#UniversalJoint But they are in tooltips: https://www.web3d.org/x3d/content/X3dTooltips.html#UniversalJoint
-
Errors in X3D-Edit QA? UniversalJoint
-
If I provide you a single X3D file, I’m afraid you will dismiss it as invalid. What I’m trying to get at is the error message is not helpful, and one must go into X3D-Edit to find the correct issue. X3D-Edit reports the issue correctly, X3DJSAIL doesn’t. I will try to address new X3DJSAIL today, but I’m not currently at my desk. John On Wed, Nov 19, 2025 at 12:28 PM Don Brutzman brutzman@users.sourceforge.net wrote: If an issue does not have a single repeatable example, it will be closed. [tickets:#70]...
-
If you have an XML file (which I think I provided), try deleting the XML header or the DOCTYPE header. From below: “Apparently, these 460+ errors were caused by a missing XML and DOCTYPE/Schema headers. That would be better information to provide than numerous confusing ones.” All I’m asking for is a better error message when the XML header or DOCTYPE header is missing, otherwise, I go chasing error messages for issues that don’t exist. I realize X3D-Edit solves this, but not for batch jobs. Perhaps...
-
The diff command below does not do my email justice. There aren’t closed tags in the original. On Wed, Nov 19, 2025 at 11:50 AM John W Carlson yottzumm3@users.sourceforge.net wrote: For example, I provided a diff between a working file and a non-working file: $ diff data/ArchHalf.new.go.x3d ../data/ArchHalf.new.go.x3d 1c1< <x3d profile="Interchange" version="4.0"></x3d> <!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 4.0//EN" " https://www.web3d.org/specifications/x3d-4.0.dtd"><x3d profile="Interchange"...
-
For example, I provided a diff between a working file and a non-working file: $ diff data/ArchHalf.new.go.x3d ../data/ArchHalf.new.go.x3d 1c1< <x3d profile="Interchange" version="4.0"></x3d> <!DOCTYPE X3D PUBLIC "ISO//Web3D//DTD X3D 4.0//EN" "https://www.web3d.org/specifications/x3d-4.0.dtd"><x3d profile="Interchange" version="4.0"></x3d> The files are in the zips. There’s no haystack, all is laid out. Yes, you will have to unpack zips in separate folders. Yes, you will have to type in long java...
-
validation success produces errors?
-
I looked for MultiTextureTransform, but it didn’t have the same complexity of Texture methods. I may be able to convert over a glTF file. There are many things that I don’t know about in this model. It looks like the container fields are hanging off of Material and PhysicalMaterial, so probably our best approach would be to search for the containerFields with the appropriate values in the archive. I can do that another time. I need to talk to Joe about what to do for tomorrow. John
-
These containerFields didn't make it into X3DJSAIL output
-
Also get skinNormal and other skin Normals ordered right with respect to DEF/USE. I can't attach my example. (Too big). I am using GraalJS and JRuby to avoid Java's size limitations.
-
HAnimHumanoid.normal should be skinNormal
-
Corrected Python included
-
HAnimHumanoid.normal should be skinNormal
-
Another thing you’re probably aware of is Holger’s x3d-tidy requires specifying .x3dj. I believe that .json should remain an option in X3DJSAIL. Putting the default in the properties file is good. Changing X3DJSAIL properties is a good idea, just realize my code is spread across many folders, so setting the properties file full path in an environmental variable is desirable, if not already done. What I will attempt to do in X3DJSONLD is use an environmental variable for the extension, some work is...
-
X3DJSAIL toFileJSON() needs to allow for .x3dj suffix in addition to .json
-
X3DUOM please take action!
-
Thanks, I was understandably confused! John On Fri, Sep 12, 2025 at 1:15 AM Don Brutzman brutzman@users.sourceforge.net wrote: I think my prior response was mistakenly posted to this ticket. Apologies for confusion. [tickets:#71] https://sourceforge.net/p/x3d/tickets/71/ ParticleSystem and Shader node validation problems Status: open Milestone: X3D4 Created: Tue Sep 09, 2025 09:11 PM UTC by John W Carlson Last Updated: Fri Sep 12, 2025 06:12 AM UTC Owner: Don Brutzman Attachments: fwparticleflowers.x3d...
-
I'll probably make a point of needing more X3D PhysicalMaterial nodes in the archives. Oh, I see a bunch in the Advanced Modeling section. Time to look at the latest.
-
Feel free to post the Sunrize scene to the archives, but if you want to use the images, please talk to Paul Debevec about licensing. https://pauldebevec.com/Probes/ (Light Probe Image Gallery). I asked him, and he was very gracious, and I just have to put a note on my website. Obviously, you would want to credit him for the images in the scene, if it's in the archives. The credit is also in the X3DJSONLD LICENSE file. If you want a source of CubeMap/Skybox closer to home, I recommend X3DOM: https://x3dom.org/x3dom/example/x3dom_composedShaderPoints.html...
-
Here's the file to test in Sunrize. I realize I may need https for images. That's one thing that X3D-Edit could mention?
-
Sorry, being a little pushy. Here's something that actually views in Sunrize! Castle doesn't have ParticleSystems. I haven't tried X3DOM. The FreeWRL version doesn't work yet. but this one does, as is evidenced by this video attached, and a video of the X3D-Edit log alongside. I will attach the tidied .x3d file soon as well!
-
I will try the </> button in the futuer.
-
Human work is actually still needed. If you want to tell me which button to press in SourceForge to get unformatted text, that would be great.
-
Here's the actual X3D-Edit QA log, with schematron false positives, AFAICT. Thanks, John
-
Please actually check this file by hand, guided by X3D-Edit reports, and balancing the standard in the other hand. I haven't found a problem yet, but I'm a dummy!
-
To be clear, that "all elements in lower case" has nothing to do with my sample file. I wouldn't trust what sourceforge does with HTML or markup. Please investigate the file, don't trust the log. I will attach a tidied file in a bit. John On Wed, Sep 10, 2025 at 11:30 AM Don Brutzman brutzman@users.sourceforge.net wrote: The diagnostics reveal (awkwardly) that the offending nodes are all lower case. That is what causes XML DOCTYPE and Schema errors too. Recomend using X3D Tidy (the sweeping broom...
-
This file should be worth validating by hand to check X3D-Edit
1 >
