I'll have to do some digging with the pixi-spine dudes to get an answer to that i think, can't see anything from a glance. I'll maybe just put a message to them directly to see if they can take a look at this thread or something. Since you got our provided spine file working using spine-ts then yeah it seems the issue is with PIXI somewhere. I sent the file to another developer who works with spine and PIXI and he said he is seeing the same problem so it's definitely not just an issue with our environment. Thanks for investigating that; I'll try get back to you with some more info or let you know if we manage to find something on PIXI's side.

Hey - think we managed to clear it up over with the pixi-spine guys.

Thanks again for the help, can check out the conversation over at github if you're interested.
(https://github.com/pixijs/pixi-spine/issues/327)

Can consider this issue closed

Hey - thanks for looking into that. Weird, but yeah we don't see the issue in Skeleton Viewer with a spine file which breaks in PIXI as well, so yeah i guess that rules out the JSON having issues..

I'll show an easier example of the issue and include the spine file we're using for it:

In skeleton viewer:

In PIXI:

Maybe this means that the issue is actually with pixi-spine itself .. which i was looking into and initially raised an issue on their github, but was mentioned to bring it here too:
pixijs/pixi-spine327

I'm really not 100% sure how to go about dealing with this issue now .. it's not urgent but has meant we've had to do some weird workarounds for some animations.. If possible could we try the spine you exported on that demo link, so and see if it behaves similar to the bug we're seeing in PIXI..? Might help to narrow it down even more if that demo which you said is working doesn't work in.

I'm running into a weird issue when using extreme values in the graph editor in my spine animations. The easing sometimes seems to not be being used, and instead it's just defaulting to use a linear easing instead. Seems if i reduce the strength of the easing, the issue resolves - and also it only seems to be on certain animations which is causing it, but when the issue does happen it's reproducible 100% of the time.

Below I'm showing a few images of the easing being used, the expected result and actual result in a test scenario.

Ease applied in spine:

Expected output as seen through spine app:

Link: https://gyazo.com/010754e8cdf2dd2c0d2d4968b793a55b

Actual output as seen through outputted file:

Link: https://gyazo.com/f208ce5899f1c27cda1f2722e2c2f512

After doing some digging, I've noticed that on these situations, the curve property exported in the .json is set to 0, instead of a proper curve value - which i think is meaning it's using a linear ease instead. Below you can see two files, one with an extreme curve in the graph editor, and one with a more subtle curve:

Extreme:

Subtle:

My idea is that one of the curve values is so steep it's becoming 1, or 0, which is causing something to think it's a linear curve instead. For reference, we're using spine on webgl applications, specifically in PIXI using the pixi-spine library to render the output, but i think this issue will be seen everywhere if the condition is met.