Hello. We recently switched over to Spine 4 and so have updated the pixi-spine to 3.1.2. Historically we have always manually called the Spine.update method (we have it all wrapped in out own class with some helper methods) but after updating I can see that this is now causing animations to run twice as fast, and in fact commenting it out solves the problem and so obviously there is an auto-call to the update method somewhere.
I am having a hard time finding any reference to what is going on here, maybe there's a global "auto update" setting I can turn off? Can you let me know any more about why this might be happening?
Or is this a new feature in latest runtime maybe?