Custom Attribute driving Position Script Controller

[PEN]

I think that we will need more information about what you are doing and how you are trying to do it. There is no reason why you shouldn't be getting real time feed back in the spinners.

[twohot]

It WOrKs! Here is the final result:

Solved the problem using Wire Parameters. That wasn't the initial setup. However, I can't help wondering if the first approach was really out-of-line. I had the Custom Attribute applied to the Box (as is) and a Position Script Controller applied to the Sphere. The script controller had something like this:
[ 0, 55*cos($box01.modifiers[1].angleYZ), 55*sin($box01.modifiers[1].angleYZ) ] for [x,y,z] - where $box01.modifiers[1].angleYZ is the Parameter linked to the spinner
When I scrubbed the Spinners, nothing happened. When I leave the value of the spinner (AngleYZ) on something other than zero and reevaluate the script, I get a feedback for just that value and that's it...nothing again! Was that method entirely wrong or did I miss something?

[PEN]

When using script controllers you must create variables that are assigned a reference to the track or node that you are using in the expression. This will make them update in real time.

[twohot]

When using script controllers you must create variables that are assigned a reference to the track or node that you are using in the expression. This will make them update in real time.
Thank you very much PEN

I was assigning controllers to the variables (not tracks); and all the while wondering why MAX won't give me access to the Parameters. The Position Script approach is now functional!. Note:Assigning nodes gave similar results as with controllers.

VERY GRATEFUL:)

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.