Undo-ing Set Driven Keys Bug

[Anonymous]

Hey guys,

Running Maya 2017 v5 - Student License. Currently updating to Version 5.

I'm going to be referencing some things and typing abbreviations instead.

SDK = Set Driven Keyframe

Has anyone else run into an issue where undo-ing SDKs will not delete all nodes connected with the driven object attributes?

For example, when you use the SDK window and use more than one driver, Maya creates blendedNodes to allow multiple drivers to affect the same attribute. These nodes are incredibly helpful to allow multiple SDK-driven attributes on one object. But I've encountered what I think is a bug...

WHEN you undo the creation of these SDKs, the blended nodes specifically for the translate (and sometimes visibility) attributes do not go away. In fact, the animCurves that are created become disconnected from the driver but stay connected to the blendedNodes and then of course the object's attributes.

This will eventually create a messy scene if a user consistently undo-s SDKs. In addition, the nodes left behind are still affecting the attributes, and it's only obvious when they are selected. Selecting the blendedNodes or the animCurves refreshes the connection and the values affect the attributes on the object (not a desired behavior, especially since the values can alter what is considered "default"). The object can be a mesh or a joint -- same exact bug occurs when undo-ing the SDKs.

Anyone else run into this issue or is this just me?

[sean.heasley]

Hi @Anonymous

I'm having a bit of trouble reproducing this issue on my machine.

When you get a chance, can you please possibly post some screenshots and/or video of your issue?

If you need a video capturing program, Screencast is a great option that we use here at Autodesk

Let me know if anything happens!

[sean.heasley]

Hi @Anonymous 

Just wanted to check in to see how things were going. Are you still having this issue?

If your issue is resolved, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

[Anonymous]

Hey Sean,

Sorry for the delay, bit of a chaotic week.

I've got a screen recording.

The issue seems to only occur on the translate attributes. Not entirely sure why. I've also encountered the Visibility attribute holding onto a remnant on a joint (rather than a mesh).

See if you can reproduce it then. It's definitely halting my progress on another script I'm developing.

Thanks!

[sean.heasley · Accepted solution]

Hi @Anonymous

Thanks for the in depth video with reproducible steps!

I was able to reproduce this issue so I went ahead and logged this with our dev team to work on a fix!

I'm also gonna do some quick testing and see if this occurs in 2018 or if it has been fixed!

*Edit*

I just tried this in 2018.2 and it looks like it has been fixed!

[Anonymous]

Hey Sean,

Let me know the results. Thanks for posting this bug. I haven’t tested this in 2016, I was using this version for a long time.

Looking forward to your results.

[Anonymous]

Awesome news, thanks for the update Sean.

Cheers

[Anonymous]

Hey Sean,

I got Maya 2018 and reproduce the issue. Updated it to 2018.2 and was able to reproduce the issue again. I don't believe this issue has been resolved.

Let me know when there is a fix available.

Thanks

[sean.heasley]

Hi @Anonymous

Strange, I wasn't able to reproduce it the first time but now I'm able to reproduce it.

I went ahead and re-opened the log on this with our dev team so they know its not fixed and can work on a fix!