Entities can be organized as groups or hierarchical gathering called Units or Aggregates.
The benefit of such teaming is the ability to aggregate all members behind a unique master entity. This simplifies the representation on the map without cutting down the accuracy (aggregated entities can be simulated individually but without display on the map)
To create a Unit, one entity must be defined as the Master and others as Members.
|
|
A member can also be a Master of a sub-unit.
|
On the terrain map, units are displayed with connecting brown lines (when a Master is selected) or a green line to the Master (when a Member is selected):
Units are also represented in a hierarchical way on the Environment tree list:
On the terrain map, when an entity is selected, it can be made a master unit by selecting the Make Master option:
To add members to this new unit, just select desired entities one at a time and make them Join the Unit:
For a member, to leave a unit, just use the option Leave Unit:
For a unit, to release all its members and become a single entity, just use the Release All option:
At runtime, a Master will be able to raise events only to its members. Conversely, a Unit Member will be able to raise an event only to its Master.
Communication
channels can also used inside a Unit for exchanging data amongst members (report, synchronization, etc.)
From the GUI or using the API, it is possible for any entity, to join or leave a Unit.
Vt_Entity class Unit API:
|
int makeUnit(UnitState =U_Disaggregated); ///< Make an entity a master unit.
int freeUnit(); ///< Release all members from the unit. Master becomes normal entity.
int joinUnit(Vt_Entity*); ///< Join the given master unit
int leaveUnit(); ///< leave the current unit if any.
int isUnit(); ///< Is entity a master?
int isMember(); ///< Is entity a unit member?
|
