I’m having some issues with the changes in CCActionInterval which were added to allow for the stackable actions.
On rapid transitions and movement actions (< 1 sec) I am getting positional errors with nodes failing to reach or overshoot their destination.
Rolling back changes in just the startWithTarget and update functions (around line 783 of CCActionInterval.js) makes the incorrect behaviour go away. I haven’t looked too deeply but I think that the issue is the accumulated error built up by taking differences in position based on the time parameter.
My workaround for now is to roll back as I am not stacking movement actions.
I tried looking at setting the position to the endPosition when time is 1 but there is definitely something else going on as that seems to fail in some cases.