Moho Forum

Not sure if this is a bug or how ASP is supposed to work.

1. Make a smart bone dial. Bone defaults to B#.
2. Action associated with that bone has the same B#.
3. Change the name of the smart bone.
4. Action's name from step 2 doesn't update to reflect step 3.

Is this a bug or is this because Actions match what they're associated with by name string and not some under the hood id?

You are right, but consider sometimes you could want to change the name of a bone precisely to "unbind" its smart actions.
I think a good solution would be if, after changing a bone's name, the software would ask you "This bone has actions associated to it, do you want to also update the actions names?".

Víctor Paredes wrote: I think a good solution would be if, after changing a bone's name, the software would ask you "This bone has actions associated to it, do you want to also update the actions names?".

Yes I like this idea. I'll open a mantis ticket.

Also, I've found that reparenting or unparenting the smart bone will cause the associated action (ie., point movements) to go askew. Adding bones seems to be okay.

As best practices go, I think it's best to finalize the bone names and parenting structure before creating any smart bone actions.

neeters_guy wrote:Also, I've found that reparenting or unparenting the smart bone will cause the associated action (ie., point movements) to go askew. Adding bones seems to be okay.

Yes, that's because the bone angle value is relative to its parent. The software should be smarter in that case too, re-calculating the angles inside the smart bones actions to continue working even if the parent changed.