Collada Importer (Composition by dust)

Author: dust
License: Public Domain
Date: 2011.08.07
Compatibility: 10.6, 10.7
Required plugins:
none... qc native

This patch demonstrates how to load a colloda file in quartz composer without using the mesh importer patch. You have more control over the types of component you can import. This is an example of getting texture coords but its certainly possible to get skinned meshes tangents, animations etc...

dust's picture
Re: Collada Importer (Composition by dust)

mesh package.

ColladaImport.zip951.42 KB

cybero's picture
Re: Collada Importer (Composition by dust)

That's a really good example of how to deal with a single texture mesh and thereby obtain its texture coordinates. Of course, it will need to be adjusted to suit the bewildering variety of dictionary entries to be found in different .dae files.

For instance, loading of multiple textures.

What would be really cool is to have some sort of .dae XML format reader that output the structure[s] within, without crashing Quartz Composer, which is what I find happens when I seek to extract all meshes from a Mesh Importer patch :-). Something like a .dae reader /feedback patch that auto populates as per the inherent structure of the file.

Really useful example post, dust. Thanks for sharing.

dust's picture
Re: Collada Importer (Composition by dust)

thanks cybero. you can change the component index to select various asset components. i think parsing out the name of the component would be good idea just to know what your dealing with. also instead of hard wiring the uv map like i did. probably the uv should be with iterations so any model could be loaded up.

its interesting you mention the all the different entries. thats not such a problem i guess in an application context. it would be easier to make a plugin i guess to traverse the xml graph than dealing with it in qc by hovering over tool tips.

its a start..