Storyline 360 - intersect with motion path doesn't behave as expected
Nov 16, 2016
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.
https://360.articulate.com/review/content/d9ff3e97-926f-4ee2-99ad-df56be2839c0/review
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).
11 Replies
Hi Adam, Here's the work around. Treat your motion path like a limit. Make it a tiny distance, and conditionally test against a variable as it moves in an animation complete loop. If the variable changes( ie. collision) then set it on it's new path. This is the basic set up. Hope this helps.
Hi Richard.
This works well for line-based motion paths but wouldn't for long arcs.
I do think this is something that really should be possible with just using a normal motion path with a relative paths for the reaction to an intersect trigger.
I have been using the same workaround that Richard described. It `kind of`works, but it changes the dynamics of the initial motion path and for fastmoving collisions it`s just not useable.
Hello Adam! Happy to hear you're trying out Storyline 360! You mentioned that you'd like to have the possibly of triggering another move along a motion path when a shape intersects another moving shape. Would you be able to add in a Feature Request on the ability to trigger that kind of motion path? We take feature requests seriously, especially given that we are able to roll out frequent updates to Storyline 360.
Hi Alyssa
I have added this as a feature request as suggested.
Great! Thanks, Adam :)
Hi Alyssa and Adam
Do you know, if that request has already been realized in an recent update of Storyline 360 or will be soon?
To be honest, I don't understand the workaround which has been posted by Richard completely.
Not to my knowledge Matthias.
Hi Matthias! Thanks for checking in. I don't have any updates to share at this point on that feature. Hopefully Richard can share a bit more about his workaround for us!
Is there any notion from Articulate that they would consider investigating this as part of the 360 roadmap? I would still argue the existing behaviour is not what one would expect.
Hi Adam,
We're still tracking this feature request, but it's not on our roadmap at this time. In case you're interested, here's an inside look at how a feature makes it on to our roadmap.
This discussion is closed. You can start a new discussion or contact Articulate Support.