Hi @catherinemcginnis! Thanks for sharing the information here!
Hey there - no problem
Just an fyi - the beta with this fix hasn’t been released yet, so it’s in the next (116) one which should be out fairly soon. Feel free to test away. I tested Sven as well and he seemed to be ok as well.
Take good care! Catherine
Cool to see Autodesk QA getting out in the community userbase.
So which would be the safe move here, stay in 2020.1 till this is fixed?
Stay in 2020.0 launch version or older until update 3 hopefully.
We are still in 2019, but willing to move forward. I don’t know if 2020.0 would be the right move because I remember there was some serious bug fixing in Maya with 2020.1. I don’t know we’ll wait a little bit longer though. Hopefully 2020.5 is around the corner and (that would be great) also python3 support.
Good news this has been fixed on 2020.3 (haven’t tested myself so don’t shoot me )
Wow that’s a massive improvement for me!
It does work great here with 2020.3
Awesome, its finally fixed
I am glad they fixed it. Where in the change log do they reference it? is it referred to as something different?
@Jerome
I think is this one: EM manipulation not working when some channels do not have keys MAYA-105404
Hello! first time poster here so I guess I’ll at least start by saying hi! eheh I’ve been using mGear for a little over a month now, I think the tool is doing wonder, I’m first of all an animator and by no means a coder, but so far I’ve been having a really fun time learning everything and setting up my project.
I’m currently on Maya 2020.3 and I still am experiencing hardcore performance issues like the one mentioned in the posts above. Do we have a hint at something that could cause a drop in performance post 2020.3
Parallel with EM State set to Ready. Currently on Maya 2020.3 - mGear version 3.6.0
Apologies if you need more informations, I’ll gladly post everything needed to help debunk this
Hello @fredG
welcome to the forum!
do you have redshift3D installed?
can you profile the rig with the profiler tool?
Hello Miquel,
Thanks for the quick reply. I do not have redshift3D installed. Is it a necessary tool I missed to consider in mGear’s installation?
Thanks,
no, no! Redshift is a renderer like Arnold. But add some stuff to the scene and makes the rig evaluation very slow.
About the performance drop, is hard to tell without more data.
Can you profile the rig? send sample data? or create a video to show the issue?
Cheers,
Miq
Hi, I ran the profiler over a test animation, here’s the link:
https://drive.google.com/file/d/1sW0-HEYaGsiN-bQiJ_FG0M5Iv_z9jmaD/view?usp=sharing
Bear with me if this isn’t done correctly! This is my first time using profiler ^^’ I’ll gladly run any more tests needed.
I will mention, the rig is a simple biped (custom) and the issue seem to be coming from the spine, I am able to freely move around the arms and legs, but the spine seems to just kill the performance as soon as I manipulate it.
Thanks,
yep as I was guessing you have something that is killing the performance. and is not the rig.
If you don’t have Redshift, maybe is something else. But you will need to find it.
Do you have any plugins installed?
I have posted this video on my other youtube channel about the redshift issue
Maybe helps to find the issue on your side

Hi Miquel,
Thanks again for helping with this, I’ll update this thread if I find anything relevant on my side for anyone that might encounter an issue. I’m pretty much running Maya barebone with ngSkintool and mGear so I guess I will have to dig further.
Video was helpful, thank you.
Have you got some history on your mesh(es)? Are you using anything heavy like wrapDeformer, closestPointOnSurface, rivets, or any other things you haven’t mentioned?
If you delete all your geometry, is the rig still slow on its own?
Any animation plugins that would install callbacks or scriptJobs that monitor what you have selected?
Have you tried with fresh preferences? (You don’t have to delete the prefs folder. Just shut down Maya, temporarily rename the prefs folder, and restart Maya, just to see.)