View Full Version : Max: Incredible slow Curve Editor
sidvici 06-09-2009, 11:21 AM Hey Guys,
now, after finishing my first full stretchable rig i realised its almost impossible to work with. The viewport speed seems alright but editing keys in the curve editor is a real pain in the...(u know what). to simply select a key could take up to 10 sec, not to mention moving keys around and waiting for max to update could take 1 -2 minutes! I have no clue what causes this. It has probably to do with the scripts on the bones, i dont know. it seems like when i select controls deeper in the hierarchy the longer max need to calculate and update.
Did you guys ever experienced something like this? What causes this slowdown? How can i speed up my rig?
|
|
Chinwagon
06-09-2009, 12:18 PM
I can't really offer any solutions, I can only join in to gripe about it. It's the one thing that kills any notion of doing animation with any sort of professional complexity and has frustrated me for years.
The trackview has been this way since version 7 (it was actually upgraded to this abysmal speed in version 6) and I haven't heard of any interest by Autodesk in updating it. The really frustrating thing is that max can calculate very complex rigs in real-time, can adjust keyframe numerical values in real-time or near real-time but moving keys on animation curves can take minutes to update. It's also bad at changing values on lots of objects simultaneously but I'll just cut short my rant as it's not really helping you.
My only suggestion is go through your rig from the extremities to the base deleting bits and testing the speed as you go. There should be a point where it gets quick again. That'll be where your slowdown is coming from. If you can live without the feature that's causing the slowdown get rid of it. If not, try experimenting with other ways of achieving the same result that could be more efficient.
Good luck!
:¬)
Just replying to show my concern too. It's slow on keyframed dependencies, and more then 6 tracks with lots of keys (mocap data). I think it's an internal messaging problem, but I'm no programmer. But it can really be a workflow killer.
-Johan
sidvici
06-09-2009, 02:04 PM
hm, this is really annoying. i allways knew the curve editor isnt that fastest, but this is just absurd. just hope i can find the weak spot and pray that the stretchy bones scripts r not the cause. i spend 2 weeks on it to finally get it to work right.
well thx for the condolences anyway :)
Just replying to show my concern too. It's slow on keyframed dependencies, and more then 6 tracks with lots of keys (mocap data). I think it's an internal messaging problem, but I'm no programmer. But it can really be a workflow killer.
-Johan
Yes max has quite a few internal messaging bugs.
CGTalk Moderation
06-09-2009, 02:10 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.
vBulletin v3.0.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.