TMT Troubleshooting Guide (all versions) - Revision history

Shawn Allen: /* ADOs Can't Travel On Sections of the Road Network wordsmith*/

2023-02-17T21:52:05Z

‎ADOs Can't Travel On Sections of the Road Network wordsmith

Shawn Allen: /* ADOs Can't Travel On Sections of the Road Network wordsmith*/

2023-02-17T21:50:44Z

‎ADOs Can't Travel On Sections of the Road Network wordsmith

Shawn Allen: /* ADOs Can't Travel On Sections of the Road Network add elevation map image*/

2023-02-17T21:48:38Z

‎ADOs Can't Travel On Sections of the Road Network add elevation map image

Shawn Allen: /* Objects Not Controllable Add tileSizes info here*/

2022-02-21T22:04:59Z

‎Objects Not Controllable Add tileSizes info here

Shawn Allen: /* ADOs Can't Travel On Sections of the Road Network link to existing page for TMT forced tiles*/

2021-12-03T15:35:58Z

‎ADOs Can't Travel On Sections of the Road Network link to existing page for TMT forced tiles

Shawn Allen: /* Output Visuals failure - edit to add ADO travel issues*/

2021-12-03T14:57:24Z

‎Output Visuals failure - edit to add ADO travel issues

Shawn Allen: /* Object Controllability Pipeline */

2021-08-24T20:05:36Z

‎Object Controllability Pipeline

Steve Cable: Steve Cable moved page TMT Troubleshooing Guide (all versions) to TMT Troubleshooting Guide (all versions): Typo

2021-08-24T16:44:42Z

Steve Cable moved page TMT Troubleshooing Guide (all versions) to TMT Troubleshooting Guide (all versions): Typo

Shawn Allen: /* Object Controllability: Stop Sign in ISAT add link to xref sectio nin isat*/

2021-08-24T16:35:32Z

‎Object Controllability: Stop Sign in ISAT add link to xref sectio nin isat

Shawn Allen: /* Object Controllability Pipeline replace image failed, so do it here*/

2021-08-24T16:26:26Z

‎Object Controllability Pipeline replace image failed, so do it here

@@ Line 11: / Line 11: @@
 # The other cause for ADO failure is the use of tiles containing elevation maps.  These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area.  In cases where the proper orientation is followed, ADOs can navigate without any problem.  However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on.
-These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane).  They disappear soon after.  This problem will also be evident in ISAT during rehearsal.
+These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane).  They disappear soon after.  This problem will also be evident in ISAT because ADOs will disappear during rehearsal when they encounter this situation.
 You can confirm the situation by reviewing the TMT project and reviewing the tile category for the intersection location in question.  Elevation maps at present are limited to intersection tiles only.

@@ Line 9: / Line 9: @@
 # [https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=ISAT_Troubleshooting_Guide#I_see_cars_in_the_simulation_disappear Road map contains a discontinuity or break.]
-# The other cause for ADO failure is the use of tiles containing elevation maps.  These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area.  In cases where the proper orientation is followed, ADOs can navigate without any problem.  However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on.  These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane).  They disappear soon after.  This problem will also be evident in ISAT during rehearsal.  You can confirm the situation by reviewing the TMT project and reviewing the tile category for the intersection location in question.  Elevation maps at present are limited to intersection tiles only.  You can also mouse over the suspect area in ISAT, and watch the status bar as the cursor moves.  Note how ISAT reports the cursor is over a road when the cursor is over a road, or within an intersection when the cursor is over an intersection.  If ISAT reports "off road" when the cursor is within an intersection, this is the reason.
+# The other cause for ADO failure is the use of tiles containing elevation maps.  These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area.  In cases where the proper orientation is followed, ADOs can navigate without any problem.  However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on.
 [[File:elev_maps_20200211B.jpg|400px]]

@@ Line 11: / Line 11: @@
 # The other cause for ADO failure is the use of tiles containing elevation maps.  These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area.  In cases where the proper orientation is followed, ADOs can navigate without any problem.  However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on.  These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane).  They disappear soon after.  This problem will also be evident in ISAT during rehearsal.  You can confirm the situation by reviewing the TMT project and reviewing the tile category for the intersection location in question.  Elevation maps at present are limited to intersection tiles only.  You can also mouse over the suspect area in ISAT, and watch the status bar as the cursor moves.  Note how ISAT reports the cursor is over a road when the cursor is over a road, or within an intersection when the cursor is over an intersection.  If ISAT reports "off road" when the cursor is within an intersection, this is the reason.
-Note that not all elevation map tiles are present for all orientations.
+[[File:elev_maps_20200211B.jpg|400px]]
 == Output Visuals failure ==

← Older revision		Revision as of 22:04, 21 February 2022
Line 165:		Line 165:

	There may be additional features present in the tile that could be controlled such as road surface, pavement markings, billboards and other features.		There may be additional features present in the tile that could be controlled such as road surface, pavement markings, billboards and other features.
		+
		+	One possible issue can be identified by reviewing the world.lri file as ASCII text and identifying the object/s you wish to control. All controllable objects are located near the end of the LRI file in the OBJECTS section. Each object should have a unique, non -1 ID assigned to it. Objects that have an ID of -1 are not controllable in the BLI.
		+
		+	In some cases the tile may be missing from TMT\Tiles\CommonLRIData\tileSizes.txt. In that case add the tile to the bottom of the file following the conventions for the other entries listed:
		+	tile_name.flt x_size y_size
		+
		+	Note: size is in Tile Units, or 660f increments. This information can be found at the top of the tile.pet file, located in the tile folder under each category.

	=== Object Controllability Pipeline ===		=== Object Controllability Pipeline ===

@@ Line 8: / Line 8: @@
 There are two common causes for this issue which must be corrected using TMT in order for traffic to operate as intended on a road network.
-# If two tiles are forced together, the roads may not combine as they would normally.  The most common reasons for this would be if the adjacent tile contains a different lane configuration, profile or elevation.  The result is a break at the tile boundary where one road ends and a different road begins, creating a discontinuity in the road.  ADOs cannot navigate across this region, and will disappear from the simulation at this point.  ISAT will show this case during rehearsal across the forced region.  You can also mouse over the region and watch the status bar for the road name, then slide the cursor over to the next section and see if the road name changes.  If it does, you have a break in the roadmap that ADOs cannot travel across.  To resolve, re-design your road network and use compatible tiles.
+# [https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=ISAT_Troubleshooting_Guide#I_see_cars_in_the_simulation_disappear Road map contains a discontinuity or break.]
 # The other cause for ADO failure is the use of tiles containing elevation maps.  These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area.  In cases where the proper orientation is followed, ADOs can navigate without any problem.  However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on.  These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane).  They disappear soon after.  This problem will also be evident in ISAT during rehearsal.  You can confirm the situation by reviewing the TMT project and reviewing the tile category for the intersection location in question.  Elevation maps at present are limited to intersection tiles only.  You can also mouse over the suspect area in ISAT, and watch the status bar as the cursor moves.  Note how ISAT reports the cursor is over a road when the cursor is over a road, or within an intersection when the cursor is over an intersection.  If ISAT reports "off road" when the cursor is within an intersection, this is the reason.
 Note that not all elevation map tiles are present for all orientations.
 == Output Visuals failure ==

← Older revision		Revision as of 14:57, 3 December 2021
Line 2:		Line 2:

	Please note: any steps that call for making changes to files should proceed carefully to prevent problems. In general, backing up a file is preferred to removal.		Please note: any steps that call for making changes to files should proceed carefully to prevent problems. In general, backing up a file is preferred to removal.
		+
		+
		+	== ADOs Can't Travel On Sections of the Road Network==
		+
		+	There are two common causes for this issue which must be corrected using TMT in order for traffic to operate as intended on a road network.
		+
		+	# If two tiles are forced together, the roads may not combine as they would normally. The most common reasons for this would be if the adjacent tile contains a different lane configuration, profile or elevation. The result is a break at the tile boundary where one road ends and a different road begins, creating a discontinuity in the road. ADOs cannot navigate across this region, and will disappear from the simulation at this point. ISAT will show this case during rehearsal across the forced region. You can also mouse over the region and watch the status bar for the road name, then slide the cursor over to the next section and see if the road name changes. If it does, you have a break in the roadmap that ADOs cannot travel across. To resolve, re-design your road network and use compatible tiles.
		+	# The other cause for ADO failure is the use of tiles containing elevation maps. These tiles follow an orientation code that must be strictly followed due to the nature of the meta-data that defines surfaces within the intersection area. In cases where the proper orientation is followed, ADOs can navigate without any problem. However, use of an elevation map tile with the incorrect orientation will introduce an off-road area that ADOs cannot travel on. These places can be identified by ADOs attempting to fly (taking off the surface of the road like an airplane). They disappear soon after. This problem will also be evident in ISAT during rehearsal. You can confirm the situation by reviewing the TMT project and reviewing the tile category for the intersection location in question. Elevation maps at present are limited to intersection tiles only. You can also mouse over the suspect area in ISAT, and watch the status bar as the cursor moves. Note how ISAT reports the cursor is over a road when the cursor is over a road, or within an intersection when the cursor is over an intersection. If ISAT reports "off road" when the cursor is within an intersection, this is the reason.
		+
		+	Note that not all elevation map tiles are present for all orientations.
		+

@@ Line 174: / Line 174: @@
 Object controllability is specified in the Scenario Object List file, sol2.txt or sol2_aux.xxx.txt by the use of multiple '''Option keywords'''. The following section is the sol2 definition for a Stop sign.  Note the Options are defined as Yield, Stop, Stop All Way and Off.
-;TrafSign Stop
+ TrafSign Stop
-;&nbsp;Width
+  Width
-;&nbsp;&nbsp;0.9
+.9
-;&nbsp;&end&
+  &end&
-;&nbsp;Height
+  Height
-;&nbsp;&nbsp;3.0
+.0
-;&nbsp;&end&
+  &end&
-;	Length
+  Length
-;		0.1
+.1
-;	&end&
+  &end&
-;	VisModelCigiId
+  VisModelCigiId
-;		803
-;	&end&
+  &end&
-;	ObjID
+  ObjID
-;		803
-;	&end&
+  &end&
-;	CanBeAdo
+  CanBeAdo
-;		0
-;	&end&
+  &end&
-;	CanBeDdo
+  CanBeDdo
-;		0
-;	&end&
+  &end&
-;	CanBeStatic
+  CanBeStatic
-;		1
-;	&end&
+  &end&
-;	IsatModelBitmap
+  IsatModelBitmap
-;		"stop.bmp"
+   "stop.bmp"
-;	&end&
+  &end&
-;	IsatModelHighLod
+  IsatModelHighLod
-;		""
+   ""
-;	&end&
+  &end&
-;	IsatModelLowLod
+  IsatModelLowLod
-;		""
+   ""
-;	&end&
+  &end&
-;	Option
+  Option
-;		0 "Yield" "yield.png" "" ""
+"Yield" "yield.png" "" ""
-;	&end&
+  &end&
-;	Option
+  Option
-;		1 "All-way Stop" "stopAll.png" "" ""
+"All-way Stop" "stopAll.png" "" ""
-;	&end&
+  &end&
-;	Option
+  Option
-;		2 "Stop" "stop.png" "" ""
+"Stop" "stop.png" "" ""
-;	&end&
+  &end&
-;	Option
+  Option
-;		3 "Off" "off.png" "" ""
+"Off" "off.png" "" ""
-;	&end&
+  &end&
-;	DefaultSoundID
+  DefaultSoundID
-;		0
-;	&end&
+  &end&
-;	CollisionSoundID
+  CollisionSoundID
-;		0
-;	&end&
+  &end&
-;&end&
+ &end&
 === Object Controllability: Stop Sign in ISAT ===

← Older revision	Revision as of 16:44, 24 August 2021
(No difference)

← Older revision		Revision as of 16:35, 24 August 2021
Line 244:		Line 244:

	In order to test the scenario it is necessary to drive the scenario on miniSim™.		In order to test the scenario it is necessary to drive the scenario on miniSim™.
		+
		+	'''Note: ISAT has a known bug that randomly resets scenario objects to their default setting. A workaround exists by using an [https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=ISAT_User_Guide_Table_of_Contents#External_Reference: external reference scenario file] to set signs and features, then referencing that file from your main scenario file. This method prevents ISAT from changing object settings.

@@ Line 164: / Line 164: @@
 Each downstream element is dependent on upstream elements.  Any failure in the pipeline will result in objects that are not controllable; i.e., those objects will display only their default settings during simulation irrespective of the scenario settings authored for it.
-[[File:2021-08-20_10h51_35.png|400px]]
+[[File:2021-08-24_11h23_38.png|400px]]
 Controllable objects are specified in the sol2.txt or sol2_aux.xxx.txt, and are referenced within a tile model using appropriate syntax.  This information is extracted from the tile model and stored within the tile.pet file, which contains all meta-data for the tile: