Support for new X3D 4.0 audio nodes #80
Comments
michaliskambi
added a commit
to castle-engine/castle-engine
that referenced
this issue
Nov 1, 2023
…es that we can only read/write but don't handle in any other way This makes is easier to support more nodes "only read/write", like geo or textureprojector or X3D 4.0 audio nodes, without confusing CGE devs See castle-engine/castle-model-viewer#80
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
x3dtovrml.exe validation needs to support new X3D 4.0 audio nodes
Example:
C:\x3d-code\www.web3d.org\x3d\content\examples\X3dForAdvancedModeling/AudioSpatialSound//AllAudioGraphNodesTest.x3d processing with X3dToX3dvClassicVrmlEncoding stylesheet ClassicVRML validation: tovrmlx3d.exe AudioSpatialSound//AllAudioGraphNodesTest.x3dv --validate --enable-downloads tovrmlx3d: Warning: VRML/X3D: Error when reading, will skip the rest of X3D file: Error at line 33 column 23: Invalid X3D node content (probably unknown or not allowed field, prototype or VRML 1.0-style children) inside "Appearance": got "AcousticProperties"The text was updated successfully, but these errors were encountered: