For example, if a new attribute p1 has an expression:
pCube1.p1 = `getAttr -t (frame-1) pCube1.translateX`;
this works fine whilst the body is passive, but when it's active, translateX returns the current X position, not the previous frame's.
I can sort of understand why it fails. getAttr would somehow have to access a previous state in the solver.
But a workaround?
(btw, an active rigid body doesn't have a predefined velocity attribute does it?)