We are encountering critical issues with the spine-c runtime in version 4.2, which are blocking our production use. Our Spine-based rendering system and product are built directly on top of the official spine-c implementation.
Problem statement
darktint-RGB-Timeline causes fatal errors or incorrect behavior
• Binary file case: Parsing a spine binary that includes darktint-RGB-Timeline results in a fatal crash due to invalid memory access.
• JSON file case: Parsing a JSON file containing darktint-RGB-Timeline does not crash, but produces incorrect rendering results — the timeline appears to be parsed incorrectly or ignored.
spSkeletonBinary_create fails to honor custom scale factor
• When using spSkeletonBinary_create(...) with a custom scale value (e.g., for resolution scaling),
• the animation behaves abnormally:
• Attachment positions and sizes are not scaled.
• The referenceScale does not reflect the custom scale (unlike spSkeletonJson_create(...), which works as expected).
Pull Request of below 2 will fix the issue, but no reply or activity is ongoing over 30 days.
- EsotericSoftware/spine-runtimes2864
- EsotericSoftware/spine-runtimes2863
Runtime information
• Spine Runtime: spine-c v4.2
• Platform: Cross-platform C/C++ engine
• Files tested: .spine → exported to .json and .skel with dark tint timelines (RGB2 not RGBA2) and scale factors
• Expected behavior: spSkeletonBinary_create() should honor the scale factor; timelines should parse and animate correctly.
Please review the above PRs or let us know if there’s any blocker preventing these from being merged. These issues are critical to the integrity of the runtime in production environments, and we are happy to provide test cases or further assistance.
Thanks so much for your time and the amazing work on Spine!
