sdk:scenery_tsc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sdk:scenery_tsc_file [2020/05/10 19:26] – jh | sdk:scenery_tsc [2020/05/10 20:12] (current) – [Scenery Definition File (TSC)] jh | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== TSC File ===== | + | ===== Scenery Definition |
The TSC file is a [[simulator: | The TSC file is a [[simulator: | ||
Theses TSC files are placed in subdirectories of " | Theses TSC files are placed in subdirectories of " | ||
+ | |||
+ | > **We recomment reading through the [[sdk: | ||
Let's break down the content of the TSC file. | Let's break down the content of the TSC file. | ||
Line 9: | Line 11: | ||
==== How to optain the coordinates ==== | ==== 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 26: | Line 28: | ||
| icao | This is the unique airport ICAO code (leave empty if it's not an airport or if the airport doesn' | | icao | This is the unique airport ICAO code (leave empty if it's not an airport or if the airport doesn' | ||
| country | | country | ||
- | | coordinate_system | Coordinates in this file are defined in this coordinate system. Typically " | + | | coordinate_system | Coordinates in this file are defined in this coordinate system. Typically " |
| position | | position | ||
| height | | height | ||
Line 37: | Line 39: | ||
Individual geometries of the 3D model are used for specific functions such as (generic) objects, ground and decals. These functions are assigned as individual blocks within the tsc file. | Individual geometries of the 3D model are used for specific functions such as (generic) objects, ground and decals. These functions are assigned as individual blocks within the tsc file. | ||
+ | |||
+ | You can defined multiple blocks of the same type if needed. | ||
+ | |||
+ | Please also read the documentation of the [[sdk: | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | > | ||
+ | > | ||
+ | </ | ||
^Parameter | ^Parameter | ||
- | | type | Type of geometry that is being defined (object, ground, decal) | | + | | type | Type of geometry that is being defined (object, ground, decal, object_transparent_atc) | |
| geometry | | geometry | ||
- | | position | + | | position |
+ | | orientation | Rotates the object above the up axis, angle in degrees | ||
+ | | autoheight_override | Can force the object above ground | | ||
+ | |||
+ | ==== Animated Objects ==== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | > | ||
+ | > | ||
+ | </ | ||
+ | |||
+ | ^Parameter | ||
+ | | geometry | ||
+ | | animation | File name of the animation | | ||
+ | | position | ||
+ | | 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** | + | ==== Runways |
Each runway is defined in the tsc as a set of coordinates (lon/lat). | Each runway is defined in the tsc as a set of coordinates (lon/lat). | ||
Line 81: | Line 128: | ||
| appltsys1 / ...2 | Approach light system installed for the first and second approach end | | | 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) | | papi1 / ...2 | This side of the of the precision approach path indicators (PAPI) | ||
- | | reil1 / ...2 | + | | papi1_glide_slope |
+ | | papi1_custom_position | Manual offset of the PAPI lights in meters | | ||
+ | | papi1_spacing | ||
+ | | reil1 / ...2 | Runway end identifier lights (REIL) | ||
=== Approach Lighting System (ALS) === | === Approach Lighting System (ALS) === | ||
Line 132: | Line 182: | ||
| reil_omni | reil in all directions | | 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: |
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | > | ||
+ | > | ||
+ | </ | ||
^Parameter | ^Parameter | ||
- | | position | + | | name | Name of the helipad | |
+ | | type_name | Name of the helipad type (e.g. building) | | ||
+ | | position | ||
+ | | radius | ||
| heading | | heading | ||
- | | name | + | | height |
+ | |||
+ | ==== Parking Positions ==== | ||
+ | |||
+ | Towards the end of the file you can define individual parking positions. | ||
+ | |||
+ | Example: | ||
< | < | ||
< | < | ||
Line 156: | Line 228: | ||
> | > | ||
</ | </ | ||
+ | |||
+ | ^Parameter | ||
+ | | position | ||
+ | | heading | ||
+ | | name | Name of the parking position (e.g. West or East apron, etc.)| | ||
sdk/scenery_tsc.txt · Last modified: 2020/05/10 20:12 by jh