Great news! I am very interested in what could have caused this, so if you find something let me know so I can see if it’s something I can protect Ragdoll against.
@Geordie_Martinez Did you make any progress on this? I’ve gotten another bug report that sounds awfully similar to this, but it’s not clear what Python modules were involved here.
Not yet. I’m in crunch mode so just using the vanilla maya to record it. I plan on attacking this problem next week though.
Do you have a list of external and/or builtin module imports I can try? For example if you’re importing a module called numpy and include your own version, but we have our own version and ours is first in the python path I can just compare and find the culprit.
Another user dug a little deeper into this and found that in their case it was due to their rig having nodes written in Python participate in the Maya evaluation of the rig. Such as a squash and stretch node, or something that would be evaluated during recording.
I haven’t yet replicated this, and it’s not entirely clear why it only happens during record (and also caching) but not during regular playback, since the mechanics are all the same. But is it possible your rig also had a Python node in it?
It might take some detective work to find out, but one way would be to look at your Plug-in Manager for any plug-in that registers a new node type, and then search for that node type in your rig.
- Find .py plug-in
- Find dependency node
- Search for the type
- Select it, to see where it fits into the rig and what it does.
1 Like
Hi @marcus, just curious, are there any environment variables that Ragdoll Dynamics sets during baking? Just thinking there might be a way to disable any expression node during Ragdoll baking.
Hey @backwheelbates, welcome to the forums! 
No, there are no environment variables being set. I can make one, that could be useful. There’s a new release dropping in the next few days, I’ll include it there.
Give this new release a try, I found at least a few cases where it froze at 0% that got squashed with this update.