Forum Discussion
Triggers Stopped Working! Please Help!
Nice looking project.
I think these triggers on the Drone left layer belong on the base layer, because that's where the objects are, and deactivating them allows the left navigation arrow to work.
It will save you some time and clutter if you delete these triggers:
If you want to hide a layer when its timeline ends, there is a setting for that in the layer properties (Setting icon at the lower right of screen).
I notice you have a lot of groups. There is an old saying in the theater: "Anyone who puts kids or animals on the stage deserves what happens to them." That means that no matter how well-behaved, or well-trained you think they are, at some time they are going to revert to their true nature, and you can only hope it doesn't happen during a performance. The SL correlation is: "Anyone who uses groups deserves what happens to them." That means that no matter how well-behaved or how well-trained you hope they are, groups don't play nicely with anything, and especially not states, clicking on, and triggers. Sooner or later, you are likely to have problems with them.
The navigation buttons work fine. They appear not to work because the Flying in and Drone left layers hide everything below them until they close, and their timelines are set to 36 sec.
- MathNotermans-93 years agoCommunity Member
I have to disagree with Walt on the use of groups. It is the only way to create some clean overview in a complexer Storyline project. Although he is correct that states and groups, especially when having multiple elements with different states in a group behave badly in groups. But this is a bug in Storyline.... Articulate should fix this asap.... ok the bug is in Storyline for more then 5 years , nevertheless it is an acknowledged bug and it should be fixed.
I kept myself from using groups in SL due to the fact that you couldnot add/change elements easily. Now that is fixed and im using groups all the time. But indeed keep in mind that all states in groups act together as it is now. I do hope Articulate fixes this quickly, so you can use multiple states and buttons inside groups.
Getting back to Walt's ultimate message 'Stay away from groups'... you could also say: 'Stay away from states'... in fact thats what i do. I use GSAP and Javascript to hide/show groups or parts of groups and thus create my own statemachine.
In the end this is a bug and Articulate should fix it !