ISAT Troubleshooting Guide - Revision history

Shawn Allen: /* Elevation Map Tiles add elevation map image, part 2 edit*/

2023-02-17T21:43:43Z

‎Elevation Map Tiles add elevation map image, part 2 edit

Shawn Allen: /* Add explanation about intersection elevation maps, part1 */

2023-02-17T21:39:37Z

‎Add explanation about intersection elevation maps, part1

Shawn Allen: /* Scenario Settings page formatting*/

2022-03-31T17:19:04Z

‎Scenario Settings page formatting

Shawn Allen: /* Scenario Settings add isat graphic*/

2022-03-31T17:18:37Z

‎Scenario Settings add isat graphic

Shawn Allen: /* Scenario Settings add scenario setting stop simulation on collision notes*/

2022-03-31T17:17:54Z

‎Scenario Settings add scenario setting stop simulation on collision notes

Shawn Allen: /* My trigger doesn't work completely add invalid audio ID bug*/

2022-03-31T17:08:55Z

‎My trigger doesn't work completely add invalid audio ID bug

Shawn Allen: /* I see cars in the simulation disappear add link to TMT page*/

2021-12-03T15:37:31Z

‎I see cars in the simulation disappear add link to TMT page

Shawn Allen: /* I see cars in the simulation disappear */

2021-12-03T15:00:21Z

‎I see cars in the simulation disappear

Shawn Allen: /* My trigger doesn't work new section*/

2021-11-04T16:49:08Z

‎My trigger doesn't work new section

Shawn Allen: /* Speed Limit, Other Signs or Objects Have Reset */

2021-08-25T21:06:59Z

‎Speed Limit, Other Signs or Objects Have Reset

← Older revision		Revision as of 21:43, 17 February 2023
Line 247:		Line 247:

	This is an issue because during LRI creation, the elevation data is not rotated to match the orientation of a rotated tile. When there is a mismatch, the elevation mismatch will disrupt vehicle dynamics when driven on and cause the simulation to fail as a result.		This is an issue because during LRI creation, the elevation data is not rotated to match the orientation of a rotated tile. When there is a mismatch, the elevation mismatch will disrupt vehicle dynamics when driven on and cause the simulation to fail as a result.
		+
		+	[[File:elev_maps_20200211B.jpg\|400px]]

	====Tile Orientation====		====Tile Orientation====

← Older revision		Revision as of 21:39, 17 February 2023
Line 240:		Line 240:

	[https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=TMT_Troubleshooting_Guide_(all_versions)#ADOs_Can.27t_Travel_On_Sections_of_the_Road_Network The other main cause for ADOs to disappear is related to the use of intersection tiles containing elevation maps.]		[https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=TMT_Troubleshooting_Guide_(all_versions)#ADOs_Can.27t_Travel_On_Sections_of_the_Road_Network The other main cause for ADOs to disappear is related to the use of intersection tiles containing elevation maps.]
		+
		+	===Elevation Map Tiles===
		+
		+	Tiles that contain elevation maps are located in the TMT tile category '''elev_maps'''.
		+	The elevation maps are a way to describe the 3D surface of the area within an intersection by assigning a surface material code (SMC) to an elevation. For the most part these are flat intersections, but the elevation map is required to describe curbs and islands. This geometry is organized in a spatial context that does not work if the tile is rotated from its original orientation.
		+
		+	This is an issue because during LRI creation, the elevation data is not rotated to match the orientation of a rotated tile. When there is a mismatch, the elevation mismatch will disrupt vehicle dynamics when driven on and cause the simulation to fail as a result.
		+
		+	====Tile Orientation====
		+	An elevation map tile will contain an orientation key in the form of a letter following the tile name as shown in the table below.
		+
		+	{\| class="wikitable"
		+	\|+ Caption: elevation map table
		+	\|-
		+	! Tile Code
		+	! Tile Orientation
		+	\|-
		+	\| None
		+	\| A
		+	\| B
		+	\| C
		+	\|-
		+	\| 0 degrees
		+	\| 90 degrees
		+	\| 180 degrees
		+	\| 270 degrees
		+	\|}

	== Collision Management ==		== Collision Management ==

← Older revision		Revision as of 17:19, 31 March 2022
Line 289:		Line 289:

	'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.		'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.
		+

	[[File:isat_collision_simulation_setting.jpg\|400px]]		[[File:isat_collision_simulation_setting.jpg\|400px]]

← Older revision		Revision as of 17:18, 31 March 2022
Line 289:		Line 289:

	'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.		'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.
		+
		+	[[File:isat_collision_simulation_setting.jpg\|400px]]

	'''Note:''' The scenario option to stop simulation on collision does not currently work in miniSim version 2.3. If this functionality is required, you can emulate the effect with an expression trigger that monitors for a collision. Note there is only one type of collision possible for any object (ADO, DDO, static object).		'''Note:''' The scenario option to stop simulation on collision does not currently work in miniSim version 2.3. If this functionality is required, you can emulate the effect with an expression trigger that monitors for a collision. Note there is only one type of collision possible for any object (ADO, DDO, static object).

← Older revision		Revision as of 17:17, 31 March 2022
Line 289:		Line 289:

	'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.		'''Note:''' this setting is unique per scenario. Disabling the collision effects does not affect collisions during simulation.
		+
		+	'''Note:''' The scenario option to stop simulation on collision does not currently work in miniSim version 2.3. If this functionality is required, you can emulate the effect with an expression trigger that monitors for a collision. Note there is only one type of collision possible for any object (ADO, DDO, static object).

	=== Scenario Object Library (SOL2) ===		=== Scenario Object Library (SOL2) ===

← Older revision		Revision as of 17:08, 31 March 2022
Line 191:		Line 191:

	This can happen if an ADO that is key to an event is removed from simulation, either because the ADO went unstable or otherwise was deleted. You will need to work backward from the point that ADO disappeared and try to identify the cause for the deletion.		This can happen if an ADO that is key to an event is removed from simulation, either because the ADO went unstable or otherwise was deleted. You will need to work backward from the point that ADO disappeared and try to identify the cause for the deletion.
		+
		+	Another way a trigger may not execute all actions is if an invalid audio ID is sent to the Audio Engine subsystem. If you know your trigger contains actions after a Write to Cell >> SCC_Audio_Trigger and they do not execute, review the Audio Engine log to see if there was an invalid ID used. In that case, either correct the scenario to use an existing ID, or add the necessary file and insert the ID into the Instructions.txt file. It will be necessary to stop miniSim and exit before attempting to drive the corrected instructions.txt file. If the ID was wrong and corrected in scenario, you do not have to exit miniSim and can just drive the edited scenario.

	=== I see cars in the simulation disappear===		=== I see cars in the simulation disappear===

@@ Line 237: / Line 237: @@
 In most cases the XD will be able to navigate, but ADOs will disappear when they try to cross the tile edge where road A meets road B.
-The other main cause for ADOs to disappear is related to the use of intersection tiles containing elevation maps.
+[https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=TMT_Troubleshooting_Guide_(all_versions)#ADOs_Can.27t_Travel_On_Sections_of_the_Road_Network The other main cause for ADOs to disappear is related to the use of intersection tiles containing elevation maps.]
 == Collision Management ==

@@ Line 199: / Line 199: @@
 # the ADO is being removed by a scenario action (this only happens when the delete is explicitly specified in an action '''Remove Element''' or is of a  category or name specified in a delete action, i.e. '''Ado''' or '''Type: Vehicle'''.)
 # the ADO has a creation radius and has travelled outside the visible radius specified
-# the roadmap contains  an anomaly that the ADO cannot resolve
+# the roadmap contains  an anomaly that the ADO cannot resolve.
 The most common roadmap anomaly is when the road network is created in TMT and two tiles are forced together.  Although this is an allowed operation, it does not guarantee the resulting road network will be drivable by simulated traffic.
@@ Line 236: / Line 236: @@
 In most cases the XD will be able to navigate, but ADOs will disappear when they try to cross the tile edge where road A meets road B.
 == Collision Management ==

← Older revision		Revision as of 16:49, 4 November 2021
Line 152:		Line 152:

	'''Expression "ReadCell('CFS_Auto_Transmission_Mode', 1) = ( 0 - 2 )"'''		'''Expression "ReadCell('CFS_Auto_Transmission_Mode', 1) = ( 0 - 2 )"'''
		+
		+	=== My trigger doesn't work ===
		+
		+	The most typical reason a trigger fails is if it is missing the predicate, or the predicate is wrong. If your trigger has a valid predicate, then it is time to add some form of debugging to the action stack so that you can see if the trigger works during rehearsal in ISAT.
		+
		+	Debugging can be a create action (to create a dummy object, such as an ADO, that will become visible) or a write to cell action (this can be a real or make-believe cell, such as TEST).
		+
		+	During rehearsal, the create action should create the object specified or the cell will be reported in the ISAT debug window.
		+
		+	If neither of these things happen then consider the trigger type.
		+
		+	For Time to Arrival (TTA) triggers, placing the target point at the start of the trigger roadpad will result not in immediate execution - for that you should be using a roadpad trigger (RPT) - but a failure of the trigger.
		+
		+	Likewise if you are using an expression trigger and the expression cannot be parsed by behaviors, that trigger will also fail (you should see an error message indicating this).
		+
		+	Roadpad triggers can have roadpads that are invalid (wrong location) or missing - this will prevent the trigger from working as expected.
		+
		+	If the trigger has a creation radius that is not valid, it can prevent the trigger from working as expected.

	=== My trigger doesn't work completely ===		=== My trigger doesn't work completely ===

@@ Line 89: / Line 89: @@
 These troubleshooting elements can be removed from the scenario once the issues have been resolved.
-=== Speed Limit, Other Signs or Objects Have Reset ===
+=== Speed Limit, Other Signs or Objects Have Reset on miniSim ===
 ISAT has a known bug that can reset scenario objects to their defaults.  This can be particularly frustrating for complex scenarios.  While it may be possible to recover object settings from a backup file created by ISAT (scenario.bak) located in the same folder as the scenario.scn file, a better approach is to reduce the potential for problems by using [https://www.nads-sc.uiowa.edu/minisim/wiki/index.php?title=ISAT_User_Guide_Table_of_Contents#External_Reference| external reference scenarios.]