When the user clicks one of the wrong items, it is supposed to play a buzz and change the state of the image. That part is working fine.
When the user clicks the correct item, it is supposed to show another slide layer with an explanation. This is NOT working. I have no idea why not. Please help.
I took a look at your file and saw the same thing that Michael mentioned. Deleting picture 4 resolved the behavior you were running into.
Now, onto the why! I saw picture 4 in the timeline, but didn't spot any triggers associated with it? I also saw it was sized quite small and I couldn't resize it...which has me suspecting some element of corruption in the photo. Can you share more about where and how you added this photo into your course? Tracking down the root cause of corruption can be notoriously tricky. In general, I recommend the best practices here for preventing corruption in your .story file, and for any files, you're adding to the course.
Let me know if that sheds any light on your situation! 💡
I have a similar problem, a layer doesn't show anymore, seemingly for no reason despite being called in the base layers start timeline trigger. It was fine previously. I'm afraid I can't attach as the file is too large.
I've refined the problem. The start of base timeline triggers 2 layers, "Timer" and "Lumi" to appear, however if Timer is triggered, Lumi, does not appear, if Timer is not triggered, Lumi does appear.
Oddly, Timer contains a countdown script that also appears in a layer on the master slide (I'm reworking a quiz posted here recently.), but whether Lumi is triggered or not, that layer's actions do not run.
Oddly I was able to combine both layers into a single functional layer, but the difference in timelines meant Lumi's animation loop was restarting before it was finished. I am thinking to try a 'states' based animation instead of a gif and workaround the issue.
7 Replies
Don't ask me why/how, but it seems that Picture 4 somehow "blocks" the layer. I deleted that object in both slides and it now works, see attached.
Sure enough! I have no idea what's going on there but that did it. Many thanks!
If anyone can explain what was going on there, it would be nice to know as to avoid similar confusion in the future.
Hi Benjamin,
I took a look at your file and saw the same thing that Michael mentioned. Deleting picture 4 resolved the behavior you were running into.
Now, onto the why! I saw picture 4 in the timeline, but didn't spot any triggers associated with it? I also saw it was sized quite small and I couldn't resize it...which has me suspecting some element of corruption in the photo. Can you share more about where and how you added this photo into your course? Tracking down the root cause of corruption can be notoriously tricky. In general, I recommend the best practices here for preventing corruption in your .story file, and for any files, you're adding to the course.
Let me know if that sheds any light on your situation! 💡
Hi can i ask how you realized it was picture 4?
I have a similar problem, a layer doesn't show anymore, seemingly for no reason despite being called in the base layers start timeline trigger. It was fine previously. I'm afraid I can't attach as the file is too large.
Import the offending slide into a new project, and attach it.
Hi Walt,
I've refined the problem. The start of base timeline triggers 2 layers, "Timer" and "Lumi" to appear, however if Timer is triggered, Lumi, does not appear, if Timer is not triggered, Lumi does appear.
Oddly, Timer contains a countdown script that also appears in a layer on the master slide (I'm reworking a quiz posted here recently.), but whether Lumi is triggered or not, that layer's actions do not run.
Oddly I was able to combine both layers into a single functional layer, but the difference in timelines meant Lumi's animation loop was restarting before it was finished. I am thinking to try a 'states' based animation instead of a gif and workaround the issue.
Ok so the problem was, I'm an idiot. I recreated the layer and didn't turn of the 'hide other layers' box... so simple... so dumb.