Differences

This shows you the differences between two versions of the page.

--- sdk:scenery_tsc_file [2020/05/10 19:32] – jh
+++ sdk:scenery_tsc [2020/05/10 20:12] (current) – [Scenery Definition File (TSC)] jh
@@ Line 1: / Line 1: @@
-===== TSC File =====
+===== Scenery Definition File (TSC) =====
 The TSC file is a [[simulator:text_files|text file]] that can be edited with a regular text editor. The file can contain coordinates for an airport, a custom scenery object, runways, helipads and a lot more.
 Theses TSC files are placed in subdirectories of "places" folder in the scenery directory. For the creation of new scenery we have to set up a new TSC file and save it in our intermediate scenery folder.
+> **We recomment reading through the [[sdk:scenery|Scenery introduction tutorial]]** first\\ which provices a bit more background.
 Let's break down the content of the TSC file.
@@ Line 9: / Line 11: @@
 ==== How to optain the coordinates ====
-Please visit the [[sdk:geographic_coordinates|Geographic Coordinates]] tutorial to see how you can find out the coordinates that you need for your scenery projects.
+Please visit the [[sdk:scenery_coordinates|Geographic Coordinates]] tutorial to see how you can find out the coordinates that you need for your scenery projects.
@@ Line 39: / Line 41: @@
 You can defined multiple blocks of the same type if needed.
+Please also read the documentation of the [[sdk:scenery|different object classes]].
 <code>
         <[list_tmsimulator_scenery_object][objects][]
+            <[tmsimulator_scenery_object][element][0]
                 <[string8][type][ground]>
                 <[string8][geometry][keyw_key_west_intl_rwy]>
@@ Line 58: / Line 63: @@
 | autoheight_override | Can force the object above ground |
+==== Animated Objects ====
-**Runways**
+Animated objects require an animation to be set before exporting. The exporter then creates a .tma file that contains the keyframe animation data. Both the geometry (.tmb file name) as well as the animation file (.tma file name) are then added to the respective lines in the objects_animated elements.
+<code>
+        <[list_tmsimulator_scenery_object_animated][objects_animated][]
+            <[tmsimulator_scenery_object_animated][element][0]
+                <[string8][geometry][animations_guy_talking]>
+                <[string8][animation][animations_guy_talking]>
+                <[vector3_float64][position][11.350648 47.257897 0]>
+                <[float64][rot_in_degree][0]>
+                <[float64][duration][0]>
+                <[float64][time_scale][1]>
+                <[bool][autoheight][true]>
+            >
+        >
+</code>
+^Parameter  ^ Description                                               ^
+| geometry  | File name of the geometry |
+| animation | File name of the animation |
+| position  | Lon/lat coordinates and altitude in meters of the geometry origin (without animations applied) |
+| rot_in_degree | Rotation of the object around the up direction (without animations applied) |
+| duration | Duration of the animation sequence, zero for auto |
+| time_scale | Timelapse factor 1 = real time, 2 = twice the speed, 0.5 = half the speed |
+| autoheight | places object onto the terrain when loaded. When false then the altitude has to be set to meters above mean sea level |
+==== Runways ====
 Each runway is defined in the tsc as a set of coordinates (lon/lat).
@@ Line 97: / Line 128: @@
 | appltsys1 / ...2   | Approach light system installed for the first and second approach end        |
 | papi1 / ...2       | This side of the of the precision approach path indicators (PAPI)     |
-| reil1 / ...2       | Runway end identifier lights (REIL)     |
+| papi1_glide_slope     | Glide slope angle of the PAPI lights in degrees |
+| papi1_custom_position | Manual offset of the PAPI lights in meters |
+| papi1_spacing         | Distance between individual PAPI lights in meters |
+| reil1 / ...2          | Runway end identifier lights (REIL)     |
 === Approach Lighting System (ALS) ===
@@ Line 148: / Line 182: @@
 | reil_omni | reil  in all directions  |
+==== Helipads ====
-==== Parking Positions ====
+Helipads are defined in the tsc file as well:
-Towards the end of the file you can define individual parking positions.
+Example:
+<code>
+        <[list_tmsimulator_helipad][helipads][]
+            <[tmsimulator_helipad][element][0]
+                <[string8][name][H1]>
+                <[string8][type_name][building]>
+                <[vector2_float64][position][-81.7599657782887 24.5549091932849]>
+                <[float64][radius][8]>
+                <[float64][heading][89.13]>
+                <[float64][height][0]>
+            >
+        >
+</code>
 ^Parameter  ^ Description                                               ^
-| position  | Lon/lat Coordinates of the parking position |
+| name      | Name of the helipad |
+| type_name | Name of the helipad type (e.g. building) |
+| position  | Lon/lat coordinates of the helipad |
+| radius    | Maximum rotor radius in meters |
 | heading   | Direction of the parking position in degrees from true North |
-| name      | Name of the parking position (e.g. West or East apron, etc.)|
+| height    | Height above ground in meters |
+==== Parking Positions ====
+Towards the end of the file you can define individual parking positions.
+Example:
 <code>
         <[list_tmsimulator_parking_position][parking_positions][]
@@ Line 172: / Line 228: @@
         >
 </code>
+^Parameter  ^ Description                                               ^
+| position  | Lon/lat coordinates of the parking position |
+| heading   | Direction of the parking position in degrees from true North |
+| name      | Name of the parking position (e.g. West or East apron, etc.)|