Dial Intersection
Jul 03, 2018
Hi,
I'm trying to create an interaction that triggers a variable change based on whether or not an object in motion is intersecting a triangle on a dial that can be swung by the user. I've attached a file to illustrate this: on the first slide, the ball is stationary and on the second it follows a motion path. The condition is never met on the first slide and only met on the second after the circle moves across where the triangle originates at.
I'm guessing I can probably go back to my project and set up a bunch of different states and accomplish the same thing, but that gets clunky, and at the moment I don't have a guarantee that it would work . Has anyone else tried anything like this? Is there a reason this shouldn't work? Can it be fixed?
Thanks,
Aaron
8 Replies
There is no file attached.
Oops. Here it is.
The issue on slide 1 can be fixed, see attached. Because you are moving the dial needle with the oval being stationary you always know the dial`s current variable value and can use that value to `assume` an intersect. The behaviour on the second slide doesn`t make sense to me. The intersect works, but only with the dial`s original position. Moving the dial out of the path of the oval still triggers an intersect but with the dial`s original position, NOT its current position. To me, that`s a bug.
Thanks, Michael. I have a really intense slide set up and I've been sandboxing this problem in the project I uploaded. For the big project, I have objects moving, otherwise I'd 'assume' the intersect. I ended up creating a triangle with 36 different states, and depending on the state, it will correctly show an intersection, with motion. I'm linking it to the dial (I'm married to the dial at this point) via the dial's variable and putting it under my background. I did discover a few things though, for anyone else interested:
1. Storyline reads transparency in the alpha layer in a .png file as part of the object for intersection purposes, even if you can't see it.
2. I don't know that dials were intended to be used as intersecting objects - they don't show up in the menu if you try a drag and drop interaction, which seems like what the intersection feature was built on.
3. Any shape created in Storyline as a 'shape' will register an intersection with a second object when their boundaries intersect, and only then, as opposed to transparent alpha layers.
4. I had some problems with intersecting shapes when I chose "No fill". As long as there was a solid color, even with some transparency, things worked well.
That glitch does seem like a bug, but I wasn't sure if anyone else had even attempted what I'm doing. I really don't know.
Hi Aaron,
I don't believe I've seen examples of what you're trying to attempt, but I saw you also opened up a case and were working with Anna on this issue too.
I'll give her a heads up about the things you and Michael have already uncovered!
Thanks, Ashley. I want to say thanks for so much that I've seen you help with on here. I've learned a LOT from these forums, and your presence is greatly appreciated.
To be perfectly honest, I'm not sure that anyone has even attempted what I'm putting together. I looked at the periodic table that Phil put together for some understanding of what's possible, but I feel like I'm in uncharted waters. I appreciate the help.
Thanks, Aaron for the kind words. 😀
Sadly this specific setup is a bit outside my realm of expertise, and it looks like you're one of the first to attempt it too! If you do get it set up, I 'd love for you to share what the final result is. Our team is always looking for new examples to share and highlight.
Hello!
I wanted to update this thread and share the bug that was reported, the value of the T/F variable intersect does not change to T even if the oval (shape) intersects with underlay (shape) if the states of the underlay is set to No Fill, is not occurring in our latest update for Storyline 360. If you're noticing this bug, please make sure you're using Storyline 360 (Build 3.61.27106.0) or later.
If you need to reach our Support Team, you can reply in this discussion or reach out privately in a support case.