How to update extension-spine runtime to 4.2-beta?

britzl · April 24, 2024, 6:51am

Let’s take a look at the changelog for 4.2. We use the spine-c runtime in Defold:

EsotericSoftware/spine-runtimes/blob/4.2/CHANGELOG.md#c

# 4.2

## C

- **Additions**
  - Added physics support
    - Added `spPhysicsConstraintTimeline` and `spPhysicsConstraintResetTimeline`
    - Added `spPhysics` to be passed to `spSkeleton_updateWorldTransform()`
    - Added `spSkeletonData_findPhysicsConstraint()` to query a physics constraint by name
    - Added `spSkeleton_findPhysicsConstraint()` to query a physics constraint by name
    - Added `spSkeleton_physicsTranslate()` to translate all physics constraints by some distances in the skeleton coordinate system
    - Added `spSkeleton_physicsRotate()` to rotate all physics constraints by some distances in the skeleton coordinate system
    - Added `spSkeleton::time` to keep track of time for physics simulations
    - See also breaking changes for `spSkeleton_updateWorldTransform()` and the requirement to call `spSkeleton_update()` to advance
      pyhsics each frame.
  - Added `spInheritTimeline`
  - Added [`spTrackEntry::alphaAttachmentThreshold`](http://esotericsoftware.com/spine-api-reference#TrackEntry-alphaAttachmentThreshold)
  - Removed `const` qualifiers where appropriate
  - Added `spTrackEntry_setMixDuration()` to set the mix duration in conjunction with a delay
  - Added `spTrackEntry_wasApplied()` to check if the entry has been applied

This file has been truncated. show original

There’s a few breaking changes (Esoteric loves to break stuff!), but nothing really big. This means that the bulk of the work will be to introduce the new physics support. It’s hard to say how much time would be required to do the update, probably a week, perhaps a bit more. We would charge $80/h for this kind of public development work, which means that for one week (40 hours) the cost would be $3200. Before we commit to anything we’d obviously do a bit more investigation into the new functionality so that we can provide a more accurate cost of development.

We’ve done similar work in the past. For instance the IronSource SDK integration was sponsored by a few studios that needed the integration for their games. Some of the recent Texture Packer work was also partially sponsored by the community.

And of course the Rive integration was paid for and developed in collaboration with Rive.