Thanks adp001, print statements causing problems in time-critical code rings a lot of bells ! :)

Having two parameters, 'BigNumber' and 'BigNumberModulo' was a hangover from doing maths with valueOps where it was necessary to split the maths across several separate parameters (like I did with my ERC opening book ). Totally unnecessary if I'm using a callback to do the modulo.

So I'll take out the prints, forget about both valueOpPythonCallback in the CR2 and AddValueOperation(poser.kValueOpTypeCodePYTHONCALLBACK,...), and just use the callback.

---

The 3Dcheapskate (also available in DAZ and HiveWire3D flavours) occasionally posts sensible stuff. Usually by accident.
And it usually uses Poser 11, with units set to inches. Except when it's using Poser 6 or PP2014, or when its units are set to PNU.