Collision Detection Not Working For Slider Thumb (Storyline 360) - TEMPORARY FIX

Nov 29, 2017

Unfortunately the latest update to Storyline 360 appears to have broken the functionality of the collision detection feature when using a slider, if the slider thumb is moving automatically...

Much like the discussion in the following thread: , it used to be the case that we could set a trigger for something to happen when 'Object Intersects' selecting a slider and one other object on the stage. With the latest Storyline update this collision is now only detected if it is the user who is manually moving the slider, but not if the slider is programmed to move on its own.

I have a made a quick project to demonstrate this: (the dog is on an invisible slider, try moving it yourself after letting it play once)

I am hoping that Articulate can put this right soon, but in the mean time I do have a fix on the very slim chance anyone else's projects are affected by this.

What you can do is apply an extremely small motion path to your slider to play when your timeline starts, and set this motion path to play over a minute (max time allowed by Storyline). To the user it will not even seem like the slider is actually moving at all, but it is! And it appears that so long as your whole slider is actually moving when the collision occurs, then the collision will be detected as normal. Again here is a demo: 

I realise this is a very niche bug but it did affect one of my game based projects and required a whole afternoon of experimenting/republishing to put right again.

1 Reply
Katie Riggio

Great news, Chris! We fixed the issue you reported where the intersection triggers would be delayed or did not work correctly in the HTML5 output.

Here's how you can update Storyline 360 to see all the latest features and fixes. If this problem resurfaces, please record a Peek 360 screencast for me, and I'll be happy to help!

This discussion is closed. You can start a new discussion or contact Articulate Support.