- Release Notes
- Get Started
- Project Planning
- Preview & Publishing
- Account Settings
Path is a visualized sequence of the scenes in the demo, which is displayed when you switch from Canvas View to Path View. Studio automatically builds a path as you add scenes, transitions, and gestures to your project.
The primary purpose for Path View is to show the overall transition flow between scenes rather than the details of scene contents.
Initially, Path View is most helpful when you build linear, on-rails projects. As your project and expertise with Studio grow, you may find that Path View is most effective when you build parts of a more sophisticated demo flow rather than the entire project.
For example, you may use this view to build a quick prototype of a branch to check its flow before you add any assets to scenes or to create a Logic-Only series. After you build a part separately, you can verify its transition logic in Path View and then connect it to the main demo flow.
Tip: Check this view regularly to ensure that all added scenes are connected correctly. See also Path View troubleshooting tips and a short video in the tutorial that demonstrates how to use Path View for troubleshooting.
Here’s what you can do:
- Zoom in and out to preview the entire path, using the controls in the top left corner (F).
- Click any scene and view its actions and other settings in the side panels.
The scene name (D) automatically updates to indicate the currently selected scene in Path View whose settings are displayed in the side panel.
- Right-click a scene and preview its video in the bottom right corner. Click anywhere in the view to close the preview.
- Click any transition arrow label (A) and modify its settings in the Transition menu that opens in Canvas View.
You can identify the following scenes in Path View:
- Scenes with video assets added to them, displayed as cards with the scene name at the top and a video image below. (To preview a video, right-click the scene.)
- Scenes with no video assets added, displayed only as labels with the scene name (E). These can Logic-Only scenes or regular scenes.
- Disconnected scenes, for example, without transitions (E), with undefined transitions (when you don’t specify a scene to transition to), or with transitions set to occur By Counter.
These orphaned scenes typically appear disconnected from the main flow on the right (C, E).
Gestures and other transitions are represented by arrows, with their types identified by labels on the arrows. Below are descriptions of different transitions types that you can see in Path View:
- Gesture transitions—require user interactions during the demo are displayed as arrows with smaller versions of the previous scenes with gesture areas highlighted in green (B). See also Gestures and Add Gestures.
- Direct, scene-to-scene transitions, also known as auto transitions, and any transitions with the default After Video event selected in the Transition Menu—displayed as arrows with the Video Ends label (A) indicating that the next scene starts after the video in the previous scene ends. See also Add Auto Transitions.
- Immediate transitions, for example, from logic-only scenes and any other scenes that move to the next scene without waiting for the video to end—displayed as arrows with the Every Time label indicating that the next scene starts immediately, with all actions and events in the logic scene executed at once. See also Immediate Transitions and Advanced Transitions.
- Trigger transitions set to occur when a certain trigger condition is met appear as arrows with the Trigger: <name> label. Conditional transitions typically include at least one alternate branch as shown below. See also Triggers.
- Counter transitions set to occur when a certain counter condition is met appear as arrows with the counter operator label selected in the Counter Conditionals section of the transition. Conditional transitions typically include at least one alternate branch. See also Counters.
- Transitions with different probability (as long as they have no trigger or counter conditionals) appear with the percentage displayed on the arrow. For details, see Randomized Transitions.
If randomized transitions have a trigger or counter conditional, the transition will appear with the trigger or counter conditional label as shown above.
Since Studio builds your project path automatically, you can’t do certain things in Path View. For example, you cannot do the following:
- Make any changes directly in Path View. To make any changes to a scene or gesture, switch to Canvas View. See also Check Path View.
- Preview layers, such as buttons, text, images.
- See certain event settings (At Time, On Exit, By Counter), actions, counter and trigger values.
- See probability percentages if there are conditionals added to the same transition.