Scenario: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
Line 7: Line 7:
A project in the Tygron Engine can be set up as a Timeline based project. A session of such a project will progress along a time line, with the intention to see the impact of actions and measures on the indicators over time.
A project in the Tygron Engine can be set up as a Timeline based project. A session of such a project will progress along a time line, with the intention to see the impact of actions and measures on the indicators over time.


For different reasons it is possible to divide this timeline 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 gradually make the project interaction more complex, to jump in time to a more distant future scenario, to provide pause moments in a session, etc.
For different reasons it is possible to divide this timeline in two or more levels. Reasons to do so can be (but are not limited to)to:
* :provide the session participants a learning curve  
:''Create a first level as tutorial where a stakeholder can only perform a limited number of actions and measures, even in a secluded area in the 3D world, in order to get acquainted with the interaction with the project in the Tygron Engine, without affecting the outcome of the session as a whole.''
* :gradually make the project interaction more complex
:''Add more complex actions, measures and indicators to let session participants gradually experience the complexity of the spatial planning issue at hand. This can be combined with the above mentioned reason of course.''
* :jump in time to a more distant future scenario  
:''Each level can start with an event that reflects future scenarios, such as floodings that only occur once every fifty and every one hundred years, or the sea level rise over time for instance.''
* :provide pause moments in a session
:''Sessions often take place during business hours, taking up a whole morning, afternoon or even the whole day. By implemnitng levels the natural sesion flow can be directed to incorporate pause moments for reflection and refreshments.''


By default, a project in the Tygron Engine always consists of at least one level.
By default, a project in the Tygron Engine always consists of at least one level.

Revision as of 12:19, 21 August 2015

Please note: This page is currently being updated.

Template:Learned

What are Levels?

A Level is a relative position or rank on a scale.

How do Levels relate to the Tygron Engine

A project in the Tygron Engine can be set up as a Timeline based project. A session of such a project will progress along a time line, with the intention to see the impact of actions and measures on the indicators over time.

For different reasons it is possible to divide this timeline in two or more levels. Reasons to do so can be (but are not limited to)to:

  • :provide the session participants a learning curve
Create a first level as tutorial where a stakeholder can only perform a limited number of actions and measures, even in a secluded area in the 3D world, in order to get acquainted with the interaction with the project in the Tygron Engine, without affecting the outcome of the session as a whole.
  • :gradually make the project interaction more complex
Add more complex actions, measures and indicators to let session participants gradually experience the complexity of the spatial planning issue at hand. This can be combined with the above mentioned reason of course.
  • :jump in time to a more distant future scenario
Each level can start with an event that reflects future scenarios, such as floodings that only occur once every fifty and every one hundred years, or the sea level rise over time for instance.
  • :provide pause moments in a session
Sessions often take place during business hours, taking up a whole morning, afternoon or even the whole day. By implemnitng levels the natural sesion flow can be directed 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

Template:Editor ribbon

Adding a Level

Duplicating a Level

Removing a Level from a project

Changing the properties of a level

Template:Editor ribbon

Level

Name

Description

Event Bundles

Server Events fired when chosen

Measures

Stakeholders

Provided Budget

Start with Cinematic

Active Action Menus

Playable Zones