Bug when exporting physics animation to unity

KLCL

We are currently experiencing a critical issue with physics animations in Unity.
Within Spine the physics animations works perfectly, but no longer working normally after exported to Unity
After some testing we think it's a bug with Spine export.
We identify that during export, spine will round the weight of the physical constant from 5 decimal point down to 3 decimal point. Any weight value less than 0.0005 became zero, thus the animation no longer works the same way in Unity.
It would be much appreciated if you can fix this bug.

We use our own code and we need the export in binary. The file doesn’t export properly to Unity in json.

Spine Runtime version 4.2

Spinebot

It seems like you are encountering an issue with the precision of exported physics animation data from Spine to Unity, specifically with the rounding of weight values. This kind of precision issue can indeed affect how animations behave when imported into Unity. While you mentioned using your own code and needing binary export, it's important to ensure that both the Spine Editor and the spine-unity runtime versions are compatible. Since you are using Spine Runtime version 4.2, make sure that your Spine Editor is also updated to a compatible version. If the issue persists, consider reaching out to Esoteric Software directly with your project files for further investigation. You can send your project to contact@esotericsoftware.com for a more detailed examination.

Nate

Physics constraints don't have a "weight" property. Which properties are you seeing have a lack of precision?

There is some rounding to 2 or 4 decimal places for JSON, but none of the rounding is to 3 decimals places. Generally JSON should only be used if a human needs to read the data or you are using tools to process the data.

Binary exports do not have any rounding.