search

mgear-dev / mgear4

mGear v.4.x.x (python 3 ready) https://mgear4.readthedocs.io
MIT License
266 stars 94 forks source link

RBF Manager: import errors when 'drivenControlName' is null #149

Closed dmunix closed 1 year ago

dmunix commented 2 years ago

There seem to be an issue that stops the import of rbf files if the driven node is not a transform node. This was introduced with this rigbits commit ( which is now on mgear4 as well ) which checks if the node that was connected to the "scale" attribute to the RBF exists in scene.

This scale attribute is automatically connected to a new "RBF Multiplier" attribute created by the RBF Manager during the setup of new driven node and stored by the metadata under the "drivenControlName" key. The problem is that unless the driven node is a transform ending in "_driven", the metadata related to it during the export of a rbf setup is set to "null", resulting in the cmds.objExists to error.

miquelcampos commented 1 year ago

Thanks for the feedback @dmunix I have added the bug ticket to the current WIP project

miquelcampos commented 1 year ago

fixed in #150