So, this ties in to another thread I’d started about load orders for scripted plugins, etc…
I’m trying to come up with a way to connect the parameters of a custom attribute to the parameters of several other objects. The use case here is this:
A slider control on an object is connected to the radius2 parameter of an ngon spline, and the weight values of two lookat constraints.
My experience thus far says that I can’t quite stick node references in the parameters of the custom attribute, as it seems reading those values works fine, but setting them is difficult or impossible. However, while referencing the necessary nodes in a local variable inside of the rollout works, I have to load my scene twice, since I get Custom Attribute definition loading exceptions (saying it doesn’t know what nodes I’m referencing in the rollout) the first time, but none the second time. Everything works fine on the second load. I’m assuming that the nodes of the scene are being loaded in such a way that the custom attribute definition gets parsed before all of the scene’s nodes are loaded.
My question is this: Should I be putting these references in the custom attribute, or should I be figuring out some kind of controller script for each of the referenced nodes that updates values when the slider in the custom attribute changes? If the references are supposed to be in the CA, how do I set them up so that I won’t be throwing errors and having to load twice every time?
I can’t seem to find anything in the documentation that gives a clear view of how I should be proceeding here.