Measure: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
* Placing [[Levee]]s | * Placing [[Levee]]s | ||
* Execute Server [[event]]s | * Execute Server [[event]]s | ||
These actions are configured as components of the measure. There are restrictions on which of these spatial components may overlap, in order to keep the measure consistent. For example, two [[Building]]s that are on the same [[ | These actions are configured as components of the measure. There are restrictions on which of these spatial components may overlap, in order to keep the measure consistent. For example, two [[Building]]s that are on the same [[layer]] cannot overlap. | ||
A measure can be owned by a specific [[Stakeholder]]. You can change its name, description, image, cost and constructions details. | A measure can be owned by a specific [[Stakeholder]]. You can change its name, description, image, cost and constructions details. | ||
Revision as of 12:36, 5 October 2022
In the Tygron Platform, measures are predefined actions that can be performed by stakeholders. In contrast to other actions, such as the placement of constructions, a participant in a project session does not define any properties for the measure. Instead, they can only opt to plan or cancel the measure as it has been defined in the editor. However, measures can be set up to perform multiple actions at the same time, enabling users to plan a whole design at once.
A measure can be used to:
- Placing Buildings
- Execute terrain adjustments using measure spatials
- Upgrade existing Buildings that overlap the defined upgrade selection.
- Placing Levees
- Execute Server events
These actions are configured as components of the measure. There are restrictions on which of these spatial components may overlap, in order to keep the measure consistent. For example, two Buildings that are on the same layer cannot overlap.
A measure can be owned by a specific Stakeholder. You can change its name, description, image, cost and constructions details.
A measure is an action, which means it can be added to an action menu. Also, measures can be activated indirectly using events. Thirdly, they can be activated directly in the editor by click on the Activate Measure link:
When to use measures
A measure can be used to offer predefined plans to stakeholders. When a plan exists, applicable to the case implemented in the project, that plan can be implemented as a measure. Such a plan can consist of the spatial components of the plan, as well specific costs, and other eventual consequences of implementing that plan.
A measure doesn't need to have a spatial components. Instead, it can also be used to represent a policy change or campaign, which may have consequences for indicators, or may trigger events.
Measures can also be activated via events. This means that a measure does not necessarily need to be enacted by a stakeholder, but can also be activated at the start of a scenario, by reaching a certain point in a cinematic, or even by planning or canceling another measure. If any of these occurrences should have a spatial consequence or an effect on an indicator, a measure can also be used to define these consequences.
(In Dutch)
Creating and editing measures
Measures have a large number of properties. Depending on the complexity of the measure you intend to create, a variety of panels may need to be used to properly configure all properties of a measure.
- How to add and remove measures
- How to edit general measure properties
- How to edit measure cost details
- How to edit measure events
Advanced usage of measures
Because measures can have a large variety of effects, and can be activated via events, measures can be extremely powerful. Correctly using measures can allow an editing user to create very intricate or specific effects in a project. This does tend to make a project more complex, but can have benefits both for the maintainability of a project, as well as for the sense of realism for the session participants.
Not showing spatial effects
Normally, when a user select a measure in their action menu, the spatial effects of that measure are shown. This means locations on the map where the measure has its effect are highlighted, and the user's camera is moved to that location. However, this may not always be necessary or desirable. To prevent this, it is possible to implement the measure as two measures. A first measure, with the proper costs and description, which the stakeholder will see in the action menu. A second measure is not directly visible to the stakeholder, but has the actual spatial effect. The first measure can then, upon activation, trigger the activation of the second measure.
Reusing spatial effects
Using the above principle, it is also possible to reuse spatial effects. If multiple measures would have the same spatial effect, it is possible to have an additional measure in which the actual spatial effect is defined. All measures which should have that spatial effect can trigger the additional measure. This has the benefit of being easier to maintain if the spatial effect needs to change. Any change to the plan would only require a change to a single measure, instead of all measures which have the same effect.
Creating a spatially dynamic world
Because a measure can also be set to automatically activate on a given date, it is also possible to use measures to cause things to happen in the 3D world on predefined dates. This means that, as time progresses, buildings in and around the construction area can appear and disappear. Effects on indicators can also be added or removed at various points in time.
See also
(In Dutch)
Future Design