I am thinking, will it be more manageable if we try to reference a <instance_node> instead of the geometry information only? In such case, we will just need to reference a single <node> and all the geometry and material informaiton will be available. Or does <node> is meant for other usage?
And has anyone tried integrating both visual and physics exporters into a single exporter? So far most of the discussions I found are discussing these two topics seperately.
Yup, I did try something on OpenCollada. I started with modifying the dae2ogre to load the scene into Ogre, but stuck somewhere when implementing the animation, due to the SAX nature of loading the file. As I have a tight schedule, so I just fallback to FCollada, which has a more complete importer for Ogre at the moment.
The original url is an absolute path. I have removed the directories portion to shorten the line. I might have made a mistake there
Got it. I roughly get what you mean. Let me try to digest the Collada specs one more time