WGerick
05-25-2006, 06:42 PM
Hi there,
for the last week I've been working on my first more complex rig. Finally it all worked out and I got all the controls in, that I needed. Problem is, now that everything is finished, I can hardly work with the rig. Everything is way too slow. Scrubbing the timeslider or especially rotating the pelvis leads to a huge 20 sec lag. (Funny thing is, rotating via the viewport gizmo is almost impossible, whereas using the transform type-in works quite well)
It's not that the rig is extremly fancy. It has some nice features like stretchy spine and neck, which are mostly scripted, but can scripting cause Max to slow down so drastically? There is no skinning, no turbosmooth applied. It's a rig for a robot and all the geometry is simply linked to the bones.
It I think of something like Automatron (http://lotsofrobots.com/automatron/Automatron.htm) by Andy Murdock for "Lots of Robots" this here should be fairly easy. So I must be doing something terribly wrong.
Here is a quick vid of the features (techsmith codec, 29MB):
http://www.derwanja.de/spine.jpg (http://www.derwanja.de/BasicRig.avi)
I used scripting quite a lot. Even when I didn't have to, just to keep things easier to change. For example, I tried wiring the weight of a controller, instead of scripting it, but it worked even slower.
I know it's hard to say something without having a closer look at the actual controls, but are there some general rules? Like, choose scripting over wiring, when trying to do blablabla...
I even tried to use a node-base referencing system, instead of always using a full path name to access a custom attribute, but it left me stuck with quaternions, which caused fliping in the rotations...(http://forums.cgsociety.org/showthread.php?t=361424)
So basicly, I have no idea left. The controls are working better than I thought, but you can't animate anything. Quite frustrating ;)
Any help would be great.
THX in advance...
for the last week I've been working on my first more complex rig. Finally it all worked out and I got all the controls in, that I needed. Problem is, now that everything is finished, I can hardly work with the rig. Everything is way too slow. Scrubbing the timeslider or especially rotating the pelvis leads to a huge 20 sec lag. (Funny thing is, rotating via the viewport gizmo is almost impossible, whereas using the transform type-in works quite well)
It's not that the rig is extremly fancy. It has some nice features like stretchy spine and neck, which are mostly scripted, but can scripting cause Max to slow down so drastically? There is no skinning, no turbosmooth applied. It's a rig for a robot and all the geometry is simply linked to the bones.
It I think of something like Automatron (http://lotsofrobots.com/automatron/Automatron.htm) by Andy Murdock for "Lots of Robots" this here should be fairly easy. So I must be doing something terribly wrong.
Here is a quick vid of the features (techsmith codec, 29MB):
http://www.derwanja.de/spine.jpg (http://www.derwanja.de/BasicRig.avi)
I used scripting quite a lot. Even when I didn't have to, just to keep things easier to change. For example, I tried wiring the weight of a controller, instead of scripting it, but it worked even slower.
I know it's hard to say something without having a closer look at the actual controls, but are there some general rules? Like, choose scripting over wiring, when trying to do blablabla...
I even tried to use a node-base referencing system, instead of always using a full path name to access a custom attribute, but it left me stuck with quaternions, which caused fliping in the rotations...(http://forums.cgsociety.org/showthread.php?t=361424)
So basicly, I have no idea left. The controls are working better than I thought, but you can't animate anything. Quite frustrating ;)
Any help would be great.
THX in advance...
