Closed SerG-Y closed 1 week ago
Hello and thanks for trying the new runtime!
The issues seem quite clear and I have already an idea about what could cause the the lasts two.
I'll let you know as soon as I fixed them!
We just released 4.2.65 that should address all three issues. You probably need to move the destroy after the new button has been created to avoid an empty frame.
Hi guys, first of all, thanks for adding Pixi v8 support, great job!
I encountered a few issues when migrating from PixiJS v7 to v8 (all of these worked fine with PixiJS v7 and pixi-spine v7):
I have prepared an example demonstrating all these issues: v8: https://codesandbox.io/p/sandbox/9yh9cf
working example v7: https://codesandbox.io/p/sandbox/k8jdnc