Well, I’ve got the Eulers mystery under control and am proceeding well with my bone-driver code, but have experienced a number of very annoying system slowdowns while using the pydriver.py file I’m writing. At random intervals, not associated with any particular action, although it has always involved moving the bones (manual, keyboard, or timeline control), Blender will freeze, my hard drive will work like crazy, the system page file usage bloats to near maximum (from a norm of around 400Mb to nearly 2 Gb), and my comp is essentially useless. Sometimes Blender recovers after a long time (10-15 minutes), but just as often I have to call up TM and shut it down, and even that takes forever because of the HD activity.
This only started happening when I started writing/using the pydrivers.py file. Nothing in it seems unusual, just the usual number crunching, and except for these intermittent hangups, it works exactly as expected, looks real good in real-time when the Timeline’s running.
So, is this a “known issue”? I have to de-bug the code and tweak the parameters by using pydrivers.py in real time, but these hangups are really killing productivity.
I’d be happy to post the current code if it would help, but this doesn’t seem to be related to its functions, since it usually works fine, and the hangups can occur even when it’s not directly active.