Forum Discussion
Object intersection not working
Hey all,
I'm builing a little 'search and find' mock up but as soon as I add in the 'when object intersects' trigger, the whole thing craps out and preview just sits there trying to load.
Here's the mockup; https://360.articulate.com/review/content/3c1d296d-4f66-4cab-8ad1-867903f207be/review
I've got my scope set up as an image and then added an invisible shape over the crosshairs and grouped the two of them together.
Here is how my trigger is set up;
I'm guessing the problem is simply that the invisible shape doesnt like to be in a group for that particular trigger to work...
Any ideas how I can figure out a workaround, I've tried;
- 'mouse hovers over'
- 'object dropped on'
But not getting anwhere!
Thanks :)
Hello Everyone!
I wanted to share some great news! We are no longer seeing this bug that prevented the Object Intersects trigger from working when intersecting with an object that was part of a grouped object in a Storyline course.
Please make sure that you are using the current version of Storyline 360 (3.72.29699.0). This guide walks you through installing, updating, and opening Articulate 360 apps.
Please let us know if you're still encountering the issue and we'd be happy to continue troubleshooting with you in a support case.
I am experiencing this issue, but I am not using groups for the drag item or drop location. The project works fine as long as the drag item is dropped on the correct drop location, but if it doesn't, then it stall out.
I have constructed my own D&D scenario with triggers and variables since the native D&D feature doesn't allow for pulling the score out.
But try as I might, I cannot get the project to work as inevitably there will be at least one wrong answer.
Can anyone help?Hi, Alan.
Thank you for sharing the recording of what you're experiencing! I tried to create something similar on my end, but I couldn't replicate the issue.
Would you be comfortable sharing your .story file either publicly here or privately through a support case so we can see what's going on and help you troubleshoot?
HI Maria,
I have submitted the case #02785865.
I am experiencing this problem as well. I have tried recreating the event, the object, as well as rearranging the layers of what is on top. I have included a video (no sound).
Groups in Storyline add an extra DIV ( actually 2 if you check your console ) surrounding the group of elements in your HTML. Thus accessing it and targeting it with triggers, actions etc. makes it more complicated. As you can see in the added image... with and without a group. The group makes an extra DIV around your element...most of the times Storyline triggers will behave well...Javascript triggers for sure need work to target elements that are in that group.
I'm also experiencing this same problem. The work around you've mentioned though doesn't work for me as the grouped object makes up the background of the entire slide.
Here's a thread I created on it:
Hi Alyssa & Katie,
I have just stumbled upon this bug while working on a project. I was wondering, is there any progress update on fixing this issue?Thank you,
Stefan
Hi Stefan,
Thank you for letting us know! I am sorry that you are experiencing this issue in your project. May I ask if you could share a screen recording of the issue? This would help our team greatly!
In the meantime, the workaround that Alyssa shared should help:
The workaround is to change the condition to intersect with the group itself, instead of a specific object from within the group.
Please keep us updated and let us know if you have any questions!
Hi there, Emily!
I appreciate you circling back with your findings, and sorry to hear that this problem has resurfaced.
I found the conversation where you were knee-deep in troubleshooting on this with Cleo, and have reopened the case so we can have a second look.
He'll be in touch soon, as we're happy to work with you further on this!
Moring Leslie,
Unfortunatley it's still not working for me, as soon as I set up the triggers and go to preveiw the slide I'm stuck with a blank white screen and nothing happening.
:(Hi Emily,
Good news! We fixed the issue you reported where an object intersects trigger did not work when the object intersected an object which was part of a grouped object.
Install the latest Storyline 360 update to take advantage of all the recent features and fixes.
If the problem happens again, please record a Peek 360 screencast for me, and I'll be happy to help!Hey Emily,
Thanks for also opening a case! It looks like we've got a bug in Storyline 360 where the "Object Intersects" trigger does not work when the object is intersecting another object within a group.
The workaround is to change the condition to intersect with the group itself, instead of a specific object from within the group.
We'll keep you posted on our progress with this bug!
