|
Hi guys,
I have an optical device that I’m trying to add animatable / recordable parameters to.
For example, say I am using the optical marker data for facial mocap. I would like my device
to expose higher level properties like eye closure, so I can use it in a relation constraint. And drive a character parameter with it.
I’ve tried a few things:
1. Creating an Out animation node on the device itself. This works to an extent, but when I reload a scene after saving, (a) the connection does not get saved [the node is there, but it is disconnected from its target] , and (b) nor does the data. I suppose I would have to do this manually in FbxStore() and FbxRetrieve(), but I’d much rather do this in a way that has MB do this for me.
2. Creating an animation node on a model template. That is, calling AnimationNodeOutCreate(), and then binding a new model template to this (and of course adding the model template to the ModelTemplate property’s children set). Creating a model binding creates a new model, but the new model does not bear any of the animation nodes when I drag it into the relation view.
3. Creating a property on the model template. Same result as 2.
4. Creating a property on the model binding during ModelTemplateBindNotify().
Same result as 2.
Does anyone know the proper way to go about doing this?
Thanks,
Eric
| 
