[SOLVED] Solution for program slow-down when using 'Translate Bone'

[EHCB]

Hi! This year I've started experiencing a really bizzare issue in Moho 12. It only happens on certain documents, but the ones for which it is - it occurs with 100% regularity.

When I select 'Translate Bone' the program slows to absolute unworkable crawl, like 'click on bone... wait 20 seconds... bone is selected... click on bone again and move mouse... wait 20 seconds... laptop fan starts complaining... now the bone has moved'-speeds.
When I manage to get another tool selected (like "Manipulate Bones") then everything speeds back up to normal and I can use the tool as intended.

Does anyone have any suggestions for dealing with this? Is there a cache somewhere I can delete? It's really stopped my project dead in it's tracks.

[synthsin75]

This menu script might help: http://www.lostmarble.com/forum/viewtop ... 12&t=32714

[Greenlaw]

Yes, try the script from the thread above.

The problem you're seeing is likely caused by unwanted keyframes existing thousands of frames before frame zero. I think Moho is trying to evaluate the interpolation from those frames to the current frame, which is probably why you see the slow down. There's no known explanation for how the keyfames appear there, and thankfully it's a rare occurrence. One theory is that it can happen after a crash, but because it doesn't happen after every crash, it's still a mystery.

Anyway, this problem can be fixed manually, but it's MUCH easier with Synthsin75's tool.

[Greenlaw]

Probably not related but maybe worth mentioning: If you like pressing and holding keys to temporarily switch tools, that can affect rig performance. For example, if you press and hold T to temporarily switch to the Transform Bone tool, it will slow down a rig using IK and other 'heavy' features. If this is the case, avoid the press and hold trick when animating a rig. A quick tap on T to fully switch tools should be fine.

[hayasidist]

When I select 'Translate Bone' the program slows to absolute unworkable crawl, like 'click on bone... wait 20 seconds... bone is selected... click on bone again and move mouse... wait 20 seconds... laptop fan starts complaining... now the bone has moved'-speeds.

if you're in a position to share one of the problem files that might help understand the cause ... if not, then it would be really helpful to know if the recommended tool finds (and resolves!!) problems.

[EHCB]

Thank you so much, everyone! That was incredibly fast, specific and helpful!

I ran the script, got this result:


And now everything works great!

[synthsin75]

Ah, that's so satisfying to see my script solve the problem. Thanks for posting the image. I'm glad it helped.

[EHCB]

Ah, that's so satisfying to see my script solve the problem. Thanks for posting the image. I'm glad it helped.

You're incredibly welcome! Thanks so much for writing the thing!

[hayasidist]

@EHCB Really glad the issue is solved - It would be tremendously helpful if we could tie down how those rogue keys got there. They're really close to the default location for shape creation (-1 million). I'm wondering if you've used the sequencer at all to shift the layers "top" vector or "layer11" bone? (I've tried that experiment here, but I don't get rogue keys - so that might only be part of the causative sequence)