Storyline 360 - intersect with motion path doesn't behave as expected
We've been excited about the new intersect triggers built in to Storyline 360. These, in theory, allow us to create some cool games/interactions that make use of 'hit detection'.
We have an issue though.
Our expected behaviour would be that when a shape intersects another while travelling along a motion path, that it should be possible to trigger another move along a motion path from it's current location (if the 2nd motion path uses a relative start point).
This doesn't happen though. Instead, the first motion path is forced to complete (although even that jumps to the end point), before the next motion path commences.
Please see this example. The oval has 2 motion paths, a standard "right" line path, and a relative line angled diagonally up.
Is there a way round this. Is this intentional in design? To allow for proper gamified hit detection it should be possible to stop a current motion path in order to move off on another (relative to current position).