I had the same problem with my ragdoll example some time ago.
Were you using Shade-C in that example by an chance? If so, that would helps us in narrowing down the error source. If you were using Shade-C, could you try removing it from the example and see if the bug still appears?
i.e. you overwrite some memory or something like that
That's an option we also thought about but as there's lots and lots of code to go through we hoped there might be another (simpler) reason for this behaviour. Oh well...
Oh and happy birthday!
