It also seems that it shouldn't be too difficult to update the integration, and although I doubt it would be as easy as a cut and paste job - it doesn't seem like it would be a monumentally mammoth task either. We'd be happy to work with YoYo Games to keep the Spine integration more up-to-date, but for that we'd have to be able to work engine/editor side.Ĭlick to expand.So as you can see there seems to have been some kind of lack of clear communication of the current runtimes and versioning etc from Esoteric which they have said they will clear up, and the latest runtimes are in fact all up to date with the latest editor release v3.5.51. Writting a runtime in GLM would be to slow, and their engine and editor code aren't available to us, so we can't do much regarding integration. It's a bit of a suboptimal situation in so far, as we aren't in a position to help with the intergration in Gamemaker. (There are changes betweem 3.5 and 3.6 regarding attachment vertex world position calculations which will require slight modifications to their renderer). I'd go so far and say an update should really just be a copy & paste job. For what it's worth, our API has not changed significantly betweem 3.4 and 3.5. We'll fix this on our end.Īs for the porting effort: I can't comment on how YoYo Games uses their resources, and we have no insight in how they use our runtimes internally, e.g. It's our fault not being more upfront about what versions the runtimes support, so I would not blame YoYo Games for this hiccup. I guess we should have made this more clear. All runtimes in the master branch are up to date with the latest editor release (3.5.51) as indicated in each runtimes README.md. The release page Russel referred to isn't the latest.

Esoteric software spine api