I have two questions about exporting to collada ( with collada DOM 1.4.0 )
I created a daeURI, which is passed as a domAccessor::setSource()'s argument, and setup it.
Code :daeURI uri ; // pPositionArray is the pointer of domFloat_array and already created. uri.setElement( pPositionArray ) ; uri.resolveURI() ; pAccessor->setSource( uri ) ;
The result of above code is :
<accessor count="10" source="file:///testCollada.dae#mesh000-Pos-array" stride="3">
I tested this output file using XSI 5.1 Collada importer, but it didn't work.
So I got rid of the "file:///testCollada.dae" from their URI using text editor, it worked fine.
Is there the right way to make the daeURI without baseURI( like "file:///testCollada.dae" ) or is this a bug of XSI importer?
I am using domInputLocal and domInputLocalOffset to describe <input> schema(the child of <vertices>, <polygons> schema).
But when I use XSI 5.1 Collada Importer, these schemas are ignored. So I replaced them(<InputLocal> and <InputLocalOffset>) with simple <input>.
It worked fine...
In the Collada Specification 1.4.0, there is only the <input> schema's reference.
Is there the way of using <input> schema when I use the collada DOM 1.4.0? Or should I use the <InputLocal> scehma instead of <input> strictly?