|XML Element Name
||Support in UC-win/Road
||Several simulations can be played at the same time in UC-win/Road.
The Simulation element is displayed in the following screens of UC-win/Road.
-Setting Screen: It is displayed in the tree view of the simulation list.
The Name attribute of the simulation is displayed at the node representing a simulation.
- Play List Editor: The Name attribute of the simulation is displayed in each bar representing a simulation.
The Length attribute is used as is if present in the xml file and the simulation is
played until the end defined by the Length attribute. If the attribute
is not present in the xml file, UC-win/Road recalculates it from the latest
time found in all the elements of the simulation.
The Description attribute is not used in UC-win/Road.
Regarding the spatial coordinate system, for each simulation the relationship
between the X and Y axis of the simulation and the South->North and
West->East axis of UC-win/Road can be defined by the user.
Different sets of units can be used for each simulation opened in UC-win/Road.
UC-win/Road supports any type of unit but very small units such as Nanosecond
or Nanometer cannot be represented at the actual scale.
||Supported in UC-win/Road.
||Supported in UC-win/Road.
Virtually any number of elements is supported in UC-win/Road. Since every
element is loaded into the memory, the memory allowed for the process is
the only limitation on the number of elements that can be loaded.
The Loop attribute of the element is taken into account during playback.
The Name attribute of the element can be displayed on the Setting Screen in the
preview area and in the tree view.
For each simulation and every different value of the Type attribute, UC-win/Road allows the assignment of a model profile. A model profile is a list of 3D models and/or characters with proportions. When
an element is represented in UC-win/Road one model is selected randomly
from the profile associated to the type of this element. The proportions
set in the profile are applied during the random selection.
The Mesh3D attribute is used to open the mesh file corresponding to the element. UC-win/Road
can read rm (UC-win/Road's native format), 3ds or pk3 (character) files.
The path provided in the Mesh3D attribute can be the full or the relative
path to the xml file. The file must be on the local hard drive
of the machine or in a share folder on the network.
Moving elements are supported in UC-win/Road.
Moving elements are only visible while the movement of the traffic and
movement of the environment are enabled. Resetting the traffic will temporary
delete all the elements from the scene.
Moving elements can be represented by a 3D model or a 3D character.
The position of such elements are constantly updated according to the data
of the simulation during playback.
Fixed elements are supported in UC-win/Road.
For new elements not already present in the scene, UC-win/Road imports fixed
elements and places them in the scene. Fixed elements can be represented
by a 3D model or a 3D character.
UC-win/Road allows the association of a fixed element to an existing model in
the scene. An association can link only one fixed element of the simulation
to one model placed in the scene.
The position and direction of an existing model associated with a fixed element
will not be updated by the position information present in the xml file.
The position and direction of a model automatically placed in the scene
to represent a fixed element are the first values found in the states of
Fixed elements should be used to control objects that are parts of the
environment and always present in the scene. Only the animation of subparts
of such objects should be controlled and the position should not change
during the simulation. For example, a fixed element can be used to control
traffic signals, barriers at crossing, toll gates etc.
||Not supported in UC-win/Road.
The Time attribute is used to determine the state to use during playback.
The Value attribute is used to change the colour of the traffic lights. UC-win/Road
uses the following mapping rule:
||State of each light.
||Green ON, others OFF
||Yellow ON, others OFF
||Red ON, others OFF
||Left Green Arrow ON, others OFF
||Left Yellow Arrow ON, others OFF
||Left Red Arrow ON, others OFF
||Straight Green Arrow ON, others OFF
||Straight Yellow Arrow ON, others OFF
||Straight Red Arrow ON, others OFF
||Right Green Arrow ON, others OFF
||Right Yellow Arrow ON, others OFF
||Right Red Arrow ON, others OFF
|Any combination of the above separated by a comma character to light up several
colors at the same time.
||Lights ON or OFF according to the combination.
||All lights OFF
If no Value is specified in the xml file, UC-win/Road does not change the
current light setting.
The Animation attribute is used to change the animation of a character model.
The available animations are listed below:.
(The data of the animation itself is modeled in the character file imported
Used to place and update the position of the object.
If no Z value is present in the XML file, UC-win/Road uses 0 as the default
UC-win/Road allows placing all objects at the ground level (taking
the roads in account) and overriding the Z value present in the xml file.
Used to orientate the object in the scene.
If no value is present in the XML file, UC-win/Road uses 0 as the default value.
The reference for the Yaw angle is the Y axis.
The Active attribute is applied by UC-win/Road but the Interpolation attribute is not currently supported. Only linear interpolation is possible.
Not supported in UC-win/Road.