Scenario: Difference between revisions
| Line 9: | Line 9: | ||
For different reasons it is possible to divide a project in two or more levels. Reasons to do so can be (but are not limited to): | For different reasons it is possible to divide a project in two or more levels. Reasons to do so can be (but are not limited to): | ||
* '''to provide the session participants a learning curve, to get used to interacting with the Tygron Engine''' | * '''to provide the session participants a learning curve, to get used to interacting with the Tygron Engine''' | ||
:''Create a first level as tutorial where a [[stakeholder]] can only perform a limited number of actions and measures | :''Create a first level as tutorial where a [[stakeholder]] can only perform a limited number of [[actions]] and [[measures]]. This can happen in a secluded area of the [[3D World]], to get acquainted with the interaction with the project in the Tygron Engine, without affecting the outcome of the session as a whole.'' | ||
* '''to gradually make the project interaction more complex, to match the issue in real life more closely''' | * '''to gradually make the project interaction more complex, to match the issue in real life more closely''' | ||
:''Add more complex actions, measures and indicators to let session participants gradually experience the complexity of the spatial planning issue(s) at hand | :''Add more complex actions, measures and [[indicators]] to let session participants gradually experience the complexity of the spatial planning issue(s) at hand.'' | ||
* '''to jump in time to a future scenario''' | * '''to jump in time to a future scenario''' | ||
:''Each level can start with an [[event bundle|event]] or measure that reflects future scenarios, such as [[Terrains#Flooding terrain|floodings]] that only occur once every fifty and every one hundred years, or the sea level rising over time.'' | :''Each level can start with an [[event bundle|event]] or measure that reflects future scenarios, such as [[Terrains#Flooding terrain|floodings]] that only occur once every fifty and every one hundred years, or the sea level rising over time.'' | ||
Revision as of 15:06, 21 August 2015
What are Levels?
There are many definitions for the word Level, of which the following is the most relevant for the Tygron Engine:
- A Level is a relative position or rank on a scale.
How do Levels relate to the Tygron Engine
For different reasons it is possible to divide a project in two or more levels. Reasons to do so can be (but are not limited to):
- to provide the session participants a learning curve, to get used to interacting with the Tygron Engine
- Create a first level as tutorial where a stakeholder can only perform a limited number of actions and measures. This can happen in a secluded area of the 3D World, to get acquainted with the interaction with the project in the Tygron Engine, without affecting the outcome of the session as a whole.
- to gradually make the project interaction more complex, to match the issue in real life more closely
- Add more complex actions, measures and indicators to let session participants gradually experience the complexity of the spatial planning issue(s) at hand.
- to jump in time to a future scenario
- Each level can start with an event or measure that reflects future scenarios, such as floodings that only occur once every fifty and every one hundred years, or the sea level rising over time.
- to provide pause moments during a session
- Sessions often take place during business hours, taking up a whole morning, afternoon or even the whole day. By implementing levels the session flow can be interrupted to incorporate pause moments for reflection and refreshments.
By default, a project in the Tygron Engine always consists of at least one level.
Adding, duplicating and removing Levels in a project
Adding a Level
A level can be added in two ways in the Tygron Engine; through a ribbon drop down option or by selecting the Add button on the bottom of the left panel, after selecting Levels in the ribbon bar.
- Select Storyline → Levels
- Select Add new Level from the drop down menu
- Or select Add on the bottom of the left panel
Duplicating a Level
When levels are used to add complexity or to provide a tutorial, it can be very convenient to be able to duplicate a previous level. This avoids having to create and assign all previous actions, measures and indicators again for each consecutive level. Instead, only the added complexity needs to be put in the duplicated level.
- Select Storyline → Levels
- Select the level to be duplicated on the left panel
- Select Duplicate on the bottom of the left panel
Removing a Level from a project
Sometimes an earlier implemented level becomes redundant, or an error has occurred that renders a level useless. In such cases it is possible to remove the level completely.
- Select Storyline → Levels
- Select the level to be removed on the left panel
- Select Remove on the bottom of the left panel
Changing the properties of a Level
Level
By selecting a level entry on the left panel, the following properties become available on the right panel:
Name
In the Name field a more suitable name can be entered, if desired. Examples of this are: "Tutorial", "Prologue", etc.
Description
The description field allows for describing the level in the Editor. This is convenient when the level has added complexity. The description will also appear on the Level panel of the Admin Interface, providing a short summary of the levels in the project.