It would be fickle, because what does “keyable” mean?
In Maya, an attribute of one node can connect to an attribute of another
node. Sometimes, that other node is a animCurveTL which we then perceive as
being “keyed”. But there’s nothing differentiating the animCurveTL.output
attribute from a
On Mon, Jul 26, 2021 at 4:19 AM DGFA DAG's GRAPHIC & FOTO ART <
gerome@gmail.com> wrote:
> Hi,
> when I want to change the texture path I struggle on one point.
> Let say the path is now
> project/create/Maya/sourceimages/room/texture.exr
> There could be a deeper sub folder structure like
>
I've been pushing for "un-keyable" to actually be un-keyable for years.. (
maybe even a decade?)
I'm not exactly sure what the reasoning behind allowing un-keyable
channels to still be keyed is.
-=s
On Mon, Jul 26, 2021 at 3:35 AM Marcus Ottosson
wrote:
> The solution whould be set
The solution whould be set connectable to False, but the problem is that if
you close maya and open a new session it reverts it to keyable, so it
doesn’t really save if you close your session.
Ah that’s a bummer. Now that I think of it, that’s what happens to
setNiceNameOverride too, even when
