Closed EtaLoop closed 3 weeks ago
The parser is complaining that your int_array
contains a -1
in it, which is arguably an integer... but the array also contains a 0.5
later, which doesn't look very integral. I think blender is in the wrong here.
I have some files generated from blender 2.93 and in the same position it will use <float_array>
instead of <int_array>
, and from both the data in the array and the type="float"
references to it I'm quite sure this is a bug in blender, that appears to have since been fixed.
I apologize, I was blinded by the fact that I could visualize it, so I thought it was correct. I replaced 0.5 by 0. As you said, the parser is complaining about -1 in the array (positive numbers works).
Unfortunately a lot of visualizers and importers are somewhat lax, which contributes to the sorry state of specification compliance in the wild. This crate is very near to a collada validator, although I have made some compromises when some "too big to fail" exporter is making wrong .dae files and bug reports to the exporter go nowhere (e.g. 3ds max).
Hello, I tried to parse this collada file with in mesh \, but
Document::from_file
returnOther("parse error")
. I visualized it on online viewer so I guess the file is correct.File: