Jump to content

Nuke getAssets


tokejepsen

Recommended Posts

Hey,

I'm looking to add import functionality with the Vectorfield node. Everything is in place but ftrack-connect-nuke discover code for getting the scripts assets seem a bit hardcoded; https://bitbucket.org/ftrack/ftrack-connect-nuke/src/74ea5d8ba0589256b035a375152641ed9c6c9376/source/ftrack_connect_nuke/connector/nukecon.py?at=master&fileviewer=file-view-default#nukecon.py-32

I'm up for doing a PR, but wanted to discuss this a bit further first.

Was the original thought behind limiting the search of the nodes, for optimization? Maybe there has been complains about the performance when search all nodes for the "componentId" knob?

Link to comment
Share on other sites

I think it is partly a performance thing but the code that you refer to is quite old and should be re-evaluated.

Once we are done with refreshing the publishing part of Connect integrations we will look at import and later the asset manager. The goal would be to come up with something that is more flexible and easy to extend.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...