martinr Found a timeScale 0 bug. Made a test case: https://github.com/smaren/spine-runtimes/blob/timescale-0-bug-2/spine-ts/webgl/demos/timescalebug.js Issue happens when setting timeScale to 0 of both current and next trackEntries in a frame where the next call to update would start next. This causes division by 0 follow by multiplication by 0 which is NaN
Mario Thanks for reporting and the reproduction case. I've created an issue here: https://github.com/EsotericSoftware/spine-runtimes/issues/1290
