I was surprised to see custom properties on objects aren't exported to Collada. Seems a natural fit for the <extra> elements. Does anyone have any views on how these should be best laid out? Where is it best to request such a feature?

Does that seem reasonable? It's easy enough to parse when using the Collada DOM, for instance. I'm not sure exactly what the "tips" are supposed to be, are they just there to allow string values associated with each property in addition to numbers?

Hi rboerdijk! I mentioned this to one of the developers while we were talking about other Collada issues, after I got no replies here. It sounded like he was interested, though evidently lots of other stuff came up first. There was apparently a group of people working on Collada stuff but they never even replied to my emails. I was tempted to add the feature myself, but I switched what I was working on and don't have an immediate need for this now.

However, a recent post on the Blender developer blog mentioned one of the interns was going to be focusing on Collada. I'm hoping this issue has been scheduled along with the other obvious omissions, though the blog post sadly only mentions animation...

Hello, I am using 2.57.1.
I see collada still does not export properties.I wish the feature could be considered, it would consistently streamline asset pipeline.

So far, I have been experimenting with putting everything in the object name but this is a very dirty solution and it is incompatible with some more advanced features in the proprietary solution I am using.

Ideally, I would like a way to explicitly export properties for other formats but I guess that's just not feasible.