[x3d-public] Thoughts for x3d.py str() calls
John Carlson
yottzumm at gmail.com
Tue Oct 17 03:29:40 PDT 2023
I don't see it as an error as long as skinCoord comes before skin. What
if the Coordinate isn't even in HAnim? That's what's really the issue
here, hunting through the whole scenegraph for a stupid Coordinate. Easily
fixed by keeping a cache/map/lookup table in x3d.py. No, we can't just
reuse a variable that we store in the Blender exporter (we actually tried)
in a map, because if we set the USE, then the DEF will be erased when we
try to export.
Why is what you say an error? Huh? Perhaps I didn't read the specification
well enough?
We currently have skin IFS coord with a DEF and skinCoord with a USE, but
unfortunately, x3d.py puts out skinCoord before skin, so x3d.py must be
modified. That's error we're trying to address here. You pointing out
non-existing errors doesn't help.
I wish you guys would pull your heads out of the ivory tower for once.
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231017/4f8181bf/attachment.html>
More information about the x3d-public
mailing list