Imagine you have a "screen saver" scene that will become visible when users stop interacting with the experience. Running videos will not be counted as interactivity, therefore the screen saver scene might pop up right in the middle of a running video. To prevent this, you can use Conditional Triggers.
Scenario 1
You can now add a condition to your trigger based on the status of a given asset. In the following example, the timer trigger which fires the screen saver is conditioned by the time status of a given Video asset:
- WHEN "Scene" - Has been inactive - IF - Current time of Video - Equals 0 - THEN - Go to - Screen Saver
NOTE: you will have to stop the video once its finished playing, if the video continues to play, your screen saver will never fire.
Scenario 2
- Add a Global Variable Interface Asset to your project
- Add triggers that will set the Global Variable's state to true/false when the video starts/stops playback.
- On the Inactivity Timer, set a conditional trigger that checks if the Global Variable is true/false
- IF False, perform the navigation to the ScreenSaver scene.
To see the theory in action, you can download a sample experience
Comments
0 comments
Article is closed for comments.