Try this. Make sphere, select it, then in the MXS Listener type in:
$[4][1].custAttributes
And it returns:
<CustAttrib array for deleted node>
Anyone have any idea what this is all about?
This is what I get
-- No ""printstack"" function for undefined
I wouldn’t use indexed access to node properties unless you are looping through them and doing lots of testing. The reason that I say this is they can change depending on different states.
Good to know, thanks. Still, it’s weird that you and I are getting two different results with (supposedly) the same setup.
I get what Jon gets:
<CustAttrib array for deleted node>
Fresh started max(2008), new sphere, run code.
-Johan
It seems like accessing the custom attributes via the subanim on both [3] transform and [4] baseobject return an empty attr array. Other subanims don’t. Weird… max9 does it also…
Looking further, if I assign a spacewarp mod, it also picks up on [2], so I guess that any controller has an empty cust attr array, for the purpose of assigning custum attributes to them. It looks like a base property of an controller.
The weird thing is the deleted node message… maybe it gets its array from some special class on creation that gets deleted afterwards!? Just guessing here…
-Johan
seems that all animatable tracks returns that, …
in the case of an sphere, all tracks without controllers returns :
<CustAttrib array for deleted node>
but tracks with controllers returns :
#CustAttribs()
in max, it is not possible to delete a controller, otherwise it would return <CustAttrib array for deleted node> again
the deleted node woud be the controller itself that hasn’t been assigned?