I exported JSON files for each Skeleton from the same project and used them in the Pixi Runtime. Some work fine, but others cause the game to freeze without error messages indicating the issue.

I tried switching devices and re-exporting, but the problem persists. However, the specific Skeletons that cause issues are different each time.

Other previous projects still work fine, and there haven’t been any changes to the versions of Spine or Pixi.

How should I resolve this issue?

Spine 4.1.24 version.

Related Discussions
...

It seems like you are experiencing issues with JSON exports from Spine 4.1.24 when using them in the Pixi Runtime. A common cause for such issues is a mismatch between the Spine editor version used for export and the version of the Spine Runtimes used in your project. Ensure that the version of the Spine Runtimes in Pixi matches the version of the Spine editor you are using. If you are using a third-party runtime, consider switching to the official spine-pixi runtime. Additionally, check if the JSON files are complete and correctly formatted, as incomplete or corrupted files can cause runtime issues. If the problem persists, you might want to try exporting in a different format, such as binary, to see if that resolves the issue.

    Spinebot I have checked the Runtime, and there are no issues, just like with the previous ones.

    • Davide님이 이에 답장했습니다.

        • Davide

        • #4개 게시
        • 게시물 영어

        analog2077

        If you are using a 4.1 exported asset, you can only use 4.1 runtimes.
        The only official runtime available for PixiJS 4.1 is esotericsoftware/spine-pixi@4.1, which is compatible only with PixiJS v7.

        Please share the PixiJS version, the Spine runtime you are using, and its version. Note that there is also a pixi-spine version, which is not maintained by us and is also only compatible with PixiJS v7.

        If you are using:

        • pixi.js@7
        • esotericsoftware/spine-pixi@4.1

        There may be an issue that requires debugging. In that case, we need a minimal project that reproduces the bug. If you cannot share it here, please send it to contact@esotericsoftware.com.