I want to set a value on a parameter and lock it, then export the model so when it is referenced into a scene the user cannot change its value. The parameter value should only be editable when the TD modifies the rig as a local model. Users using the rig as a referenced model should not be able to modify the parameter value.
Matt From: [email protected] [mailto:[email protected]] On Behalf Of Raffaele Fragapane Sent: Thursday, June 27, 2013 6:33 PM To: [email protected] Subject: Re: Keyable vs. Animatable So you want to lock it in a referenced context? Locks on local are respected once referenced, we do that all the time. Locking after reference I'm not sure it's possible, there's nothing in the delta to contain it that I know of (but I might be wrong). If you're not talking hundreds and hundreds your best bet is a constant expression. That will be respected/carried by the delta. You can actually use quite a few of those with no performance impact, they are fairly cheap and don't really pull anything upstream. On Fri, Jun 28, 2013 at 11:22 AM, Matt Lind <[email protected]<mailto:[email protected]>> wrote: Edit: I want a capability setting that allows a value to be set by a TD, then locked so it cannot be edited by animators or tools used by animators. Matt From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Matt Lind Sent: Thursday, June 27, 2013 6:20 PM To: [email protected]<mailto:[email protected]> Subject: RE: Keyable vs. Animatable I checked the user's guide. siKeyable means the parameter will appear in the 'KP / L' . siAnimatable means the parameter can be animated. I don't understand why the definitions are not in the SDK guide. Anyway, we were locking parameters on character rigs using animation locking and value locking only to discover that the locks are not respected when the parameters are inside of a referenced model. ARGH!!!! (si 2013 SP1 - 32 bit) Sooooo....using Parameter Capabilities, how does one 'value lock' a parameter inside a referenced model? I want to flag a parameter so it's value can be changed by a user, but cannot be animated, and tools can read/respect the flag so it knows not to overwrite the value. Is setting siAnimatable to false enough? Matt From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Edy Susanto Lim Sent: Thursday, June 27, 2013 6:09 PM To: [email protected]<mailto:[email protected]> Subject: Re: Keyable vs. Animatable siKeyable is mainly for the parameter visibility flag in the keying panel I guess.. http://softimage.wiki.softimage.com/sdkdocs/sicppsdk/html/group__siCapabilities.html On Fri, Jun 28, 2013 at 9:01 AM, Matt Lind <[email protected]<mailto:[email protected]>> wrote: What is the technical difference between a parameter flagged as siKeyable vs. siAnimatable? I'm interpreting it to mean Keyable only determines if an FCurve can be set on the parameter whereas Animatable defines whether a parameter can receive any kind of animation data. This sound correct? Matt -- Edy Susanto Lim TD http://sawamura.neorack.com -- Our users will know fear and cower before our software! Ship it! Ship it and let them flee like the dogs they are!
