Skip to main content
At the core, the Altoura Experience system is a state machine that can be configured using the Experience builder in the Altoura Portal. There are three primary concepts in the Altoura Experience System. Nodes, Events and Transitions. Nodes: Each node is a state that the Experience can be in at a given time. It is important to understand that a given Experience can only be in one node at a time. If you are creating step by step training, each step is a node. To transition from one state to another, the user has to take an action. For ex, in one step the user may have to place a part of an equipment in a certain location. In another, it could be to place a bolt to secure the part placed in the previous step. It is important to remember that each user action that the system detects needs to be in one node. For ex, if the user has to put down a part in a certain area and then secure it using two bolts, it will require 3 nodes to be created. The first one to put down the part in a location, the second to secure it with the first bolt and the third to secure it with the second bolt. In every case, the user can also press the next arrow on the text panel to move to the next step. Events: Events are triggers that can cause the Experience to move from one node to another. Currently the system supports a few events but will expand to a lot more in the coming months. For now the primary events that Creators can use are
  1. Collider based: This event is triggered when the user moves the training object within a collider. Both the training object and collider names can be input into Node properties within the Altoura management portal
  2. Rotation: This event is triggered when the user rotates the training object by a given amount on a given axis. Both the axis and the amount can be set in the Altoura management portal.
  3. Clicking the next button: This is the default action for every step and the user can always move to the next step by clicking the next arrow button on a panel.
Transitions: When an Experience moves from one node to another, it can be made to perform actions as part of that transition. The primary use of transitions is to setup the system for the next node. It is important to remember that these are used to keep the experience in sync in a multi user session. When a new user joins a multiuser session, the system follows the nodes that have been transitioned in that session and executes the transitions for each of those step. This ensures that the new user sees the system in the same state that the original user does. Using the above concepts, creators can create sophisticated Experiences on the Altoura platform.