Difference between revisions of "TMT User Guide (versions 1.8 & greater)"
Shawn Allen (Talk | contribs) (→Obsolete and compatible tile models) |
Shawn Allen (Talk | contribs) (→Summary of changes in this version) |
||
Line 138: | Line 138: | ||
#urban_4ln_arterial_02 | #urban_4ln_arterial_02 | ||
#urban_4ln_straight_01 | #urban_4ln_straight_01 | ||
+ | |||
+ | =='''Introduction'''== | ||
+ | |||
+ | The Tile Mosaic Tool (TMT™) was created to build visual and virtual correlated databases, a process generally known as world or database generation. The TMT™ is used to arrange tile models into a configuration (world). Tile models typically contain roads, terrain and feature objects. The construction of these elements and additional models and textures require the use of 3rd party software for the creation of textured 3D models. At the present time, only OpenFlight™ models and RGB format image files are supported by the TMT™. Many commercially available (and many shareware or free) 3D programs can also be used for tile creation, but their output will need to be converted to OpenFlight™ format for use within the TMT™. For a partial list of applications, please see Appendix B. | ||
=Appendix A= | =Appendix A= |
Revision as of 14:51, 15 September 2016
This document is in progress 09.15.2016
Contents
Who should use this document
This document is for use with TMT version 1.8 or greater. Do NOT use this document if you are working with a TMT version less than 1.8.
Summary of changes in this version
This version of the Tile Mosaic Tool contains significant updates to the tile model library.
Obsolete models
The most significant change is that some tiles are now considered obsolete. Obsolete models are contained within the tile category 'Obsolete'.
It is strongly recommended that worlds using obsolete models be revised, as future versions of the Tile Mosaic Tool may not include those models.
If a world.mos file contains tile models that are missing from the library and it is saved, that .mos file will become corrupted.
There is currently no way to recover from this condition.
The Obsolete tile category is included with this version to permit replacing obsolete models with compatible tiles.
A list of compatible models is included in the Appendix of this document.
Transition tile category
Another change is that transition tiles are now grouped into a new Transition tile category. If you require a transition between different roadway types, the Transition category is the place you will find it.
New tile models
Another change in this version is the addition of tile models, listed below.
bike_lane This is a new tile category. Tiles within the bike_lane category contain bicycle lanes, which are narrow lanes defined as Vehicle Restricted lanes. This definition is intended to prevent typical ADOs from using this lane.
However, scenario authors should be able to author pedestrian and bicycle models that will use the bike lane. In some cases it may be necessary to author scenarios using the standard road lane and apply a lane offset to shift the scenario object over into the target lane.
bike_lane tile models
- 2ln_3Mi_01
- 2ln_3Mi_02
- 2ln_4way_3Mi_01
- 2ln_4way_3Mi_02
NOTE: Bike lanes are not necessarily included as a separate network adjacent to the road network. At this time they are an attribute of the road.
city tile models
- 4ln_city_1x1_02
- 4ln_city_1x1_crv90_02
- 6ln_4way_01
- 6ln_4way_02
- 6ln_city_straight_01
- 6ln_city_straight_02
comm tile models
- 2ln_4ln_3way_comm_02
- 2ln_4ln_3way_comm_03
- 4ln_4way_comm_01
- 4ln_comm_straight
- 4ln_comm_straight_04
- 4ln_comm_straight_05
- 4ln_res_3way_comm
- 4ln_res_hill_curve01
filler tile models
- gen_common_3x5
- urban_01
- urban_02
- urban_03
fwy tile models
- fway_2ln_04
- fway_2ln_10k10kS_01
- fway_4ln_2ln_DTL01
- fway_4ln_straight_13x17
railroad tile models
- railway_1xgrade_rural_01
- railway_1xgrade_rural_02
- railway_1x_straight
- railway_3xgrade_city_01
- railway_3xgrade_rural_01
- railway_3xgrade_rural_02
- railway_3x_straight
- railway_4ln_city_01
- railway_90
- railway_straight
res tile models
- 2ln_res_mult_school
- 2ln_res_rural_trans
- 2ln_straight_res
- 2ln_straight_res_2
- res_2ln_3way
- res_2ln_3way_02
- res_3way
- res_3way_02
- res_90
- res_straight
rural tile models
- 2ln_3way_rural_res01
- 4ln_1mi_02
suburb tile models
- suburb_2mi_01
- suburb_90_01
- suburb_Scurve_01
transition tile models
- 2ln_fwy_2ln_rural
- 2ln_fwy_3ln_fwy
- 2ln_fwy_3ln_fwy_02
- 2ln_fwy_4ln_fwy
- 2ln_fwy_4ln_urban
- 2ln_rural_2ln_gravel
- 2ln_rural_2ln_gravel_02
- 2ln_rural_2ln_res
- 2ln_rural_2ln_res_3way
- 2ln_rural_2ln_rural_10f_lane
- 2ln_rural_2ln_rural_no_shoulder
- 2ln_rural_3M_rural
- 2ln_rural_4ln_city
- 2ln_rural_4ln_rural
- 3ln_fwy_3ln_urban
- 4ln_BLVD_4ln_urban_e20
- 4ln_BL_urban_2ln_rural
- 4ln_city_4ln_BL_city
- 4ln_city_4ln_BL_city_ROT_C
- 4ln_rural_2ln_fwy
- 4ln_suburb_2ln_rural
- 4ln_suburb_2ln_rural_night
- 4ln_urban_6ln_urban_day
- 4ln_urban_6ln_urban_night
- 5ln_urban_4ln_urban
urban tile models
- 4ln_urban_4x8_01
- urban_2ln_4ln_s1400A
- urban_4ln_arterial_02
- urban_4ln_straight_01
Introduction
The Tile Mosaic Tool (TMT™) was created to build visual and virtual correlated databases, a process generally known as world or database generation. The TMT™ is used to arrange tile models into a configuration (world). Tile models typically contain roads, terrain and feature objects. The construction of these elements and additional models and textures require the use of 3rd party software for the creation of textured 3D models. At the present time, only OpenFlight™ models and RGB format image files are supported by the TMT™. Many commercially available (and many shareware or free) 3D programs can also be used for tile creation, but their output will need to be converted to OpenFlight™ format for use within the TMT™. For a partial list of applications, please see Appendix B.
Appendix A
Obsolete and compatible tile models
Do NOT use obsolete tile models - instead, locate the compatible tile model and use that instead. Obsolete models are included solely to avoid potentially corrupting existing world.mos files.
Obsolete Tile | use -> | Compatible Tile |
2ln_city_06 | is now: | 2ln_rural_4ln_city |
2ln_4ln_trans_01 | is now: | 2ln_rural_4ln_rural |
2ln_res_rural_trans | is now: | 2ln_rural_2ln_res |
urban_4ln_trans_01 | is now: | 5ln_urban_4ln_urban |
fway_3LN_2ln_Trans_01 | is now: | 2ln_fwy_3ln_fwy |
rural_2ln_gravel_trans_01 | is now: | 2ln_rural_2ln_gravel |
suburb_trans_rural_01_night | is now: | 4ln_suburb_2ln_rural_night |
suburb_trans_rural_01 | is now: | 4ln_suburb_2ln_rural |
4ln_city_1x1_BL_Trans01 | is now: | 4ln_city_4ln_BL_city |
fway_trans_4ln_01 | is now: | 2ln_fwy_4ln_urban |
fway_trans_rural_01 | is now: | 2ln_fwy_2ln_rural |
fway_trans_4ln_2ln_01 | is now: | 2ln_fwy_4ln_fwy |
fway_3LN_3LnUrban_trans01 | is now: | 3ln_fwy_3ln_urban |
4ln_BL_rural_trans01 | is now: | 4ln_BL_urban_2ln_rural |
4ln_rural_4ln_trans_01 | is now: | 4ln_rural_2ln_fwy |
BLVD_4ln_trans_01_20 | is now: | 4ln_BLVD_4ln_urban_e20 |
fway_3ln_2ln_trans_03 | is now: | 2ln_fwy_3ln_fwy |
rural_2ln_gravel_trans_02 | is now: | 2ln_rural_2ln_gravel_02 |
rural_trans03 | is now: | 2ln_rural_2ln_rural_no_shoulder |
rural_trans01_3Mto12f | is now: | 2ln_rural_3M_rural |
rural_trans02_10fto12f | is now: | 2ln_rural_2ln_rural_10f_lane |
urban_6ln_4ln_transition | is now: | 6ln_urban_4ln_urban_night |
urban_6ln_4ln_transition_day | is now: | 6ln_urban_4ln_urban_day |
2ln_3way_rural_res01 | is now: | 2ln_rural_2ln_res_3way |
4ln_city_1x1_BL_Trans01C | is now: | 4ln_city_4ln_BL_city_ROT_C |