Search Knowledge Base by Keyword
Allows you to define if an interaction is dependant on any other interaction in the scene. This feature will allow you to build chain of events for creating an experience. Dependencies allow you to define how interactions are linked between them in order to have a whole step by step experience.
Whether it is to build an interactive story, game mechanics, tutorials or simulations, dependencies are a practical and simple feature.
If an interaction is dependent on another it means that as soon as the first interaction is validated, the other one can be activated or deactivated.
Warning: in the current version an interaction has to first be activated with a dependency (by another interaction) in order to be deactivated. (If you only have a Deactivate dependency you can create an empty IO with an empty interaction and use it for the Activate dependency).
If ‘Require All’ is checked, all the interactions in the list must be validated before the dependencies are validated.
Note that interactions have what we call a Timeframe, and an interaction can depend on different states of the timeframe of another interaction. The most used is the Triggered state (by default) which happens when all conditions of an interaction are met. You can however be dependent on an interaction that is only Active or after being triggered in After mode.
See Timeframe for details.