Based on the information provided and the contexts from the Spine forums, it seems like the issue you're encountering with loading binary exports in Phaser with Spine 4.1 might be related to a couple of potential factors. Firstly, ensure that both your Spine editor and the Phaser Spine runtime are indeed compatible and both are using version 4.1, as mismatches between editor and runtime versions can lead to issues like the ones you're experiencing. The Phaser runtime for Spine is designed to work with exports from the corresponding version of the Spine Editor, as indicated in the context from the Spine forums about version compatibility.
The error messages you're seeing, such as "offset is outside the bounds of the DataView" and "Physics constraint data name must not be null," suggest that there might be an issue with how the binary data is being interpreted by the runtime. This could be due to a discrepancy in the expected format between the exported data and what the runtime is capable of parsing, possibly because of a recent update or change in the binary export format in Spine.
Given that JSON exports are working correctly, this further points towards a specific issue with the binary export or loading process rather than a general compatibility issue between your Spine assets and the Phaser runtime. It's also worth noting that during beta phases, as mentioned in one of the contexts, there can be changes to export formats that might not yet be supported by all runtimes, although you mentioned using the stable version of Spine.
To troubleshoot this issue, you might want to:
- Double-check the versions of both your Spine Editor and Phaser Spine runtime to ensure they are indeed compatible and both are version 4.1.
- Consider using JSON exports as a temporary workaround if they are working correctly for your needs, as suggested in one of the forum contexts.
- Keep an eye on updates to both the Spine Editor and Phaser Spine runtime for any fixes or changes that might address this issue.
Unfortunately, without specific details on updates to the binary format or known issues with the Phaser runtime for Spine 4.1, it's challenging to provide a definitive solution. However, these steps should help in narrowing down the cause of the problem.
