simulator:text_files
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
simulator:text_files [2017/01/18 11:01] – [Editable Text Files] jh | simulator:text_files [2020/05/10 20:00] (current) – ↷ Links adapted because of a move operation jh | ||
---|---|---|---|
Line 6: | Line 6: | ||
* [[aircraft: | * [[aircraft: | ||
* [[aircraft: | * [[aircraft: | ||
- | * [[aircraft:tmr|TMR]] - aircraft repaint files | + | * [[sdk:scenery_tsc|TSC]] - scenery and object description files |
- | * [[scenery: | + | |
* [[simulator: | * [[simulator: | ||
* [[simulator: | * [[simulator: | ||
Line 15: | Line 14: | ||
For editing all Aerofly FS 2 text files the IPACS development team recommends using one of the following UNICODE capable text editors. | For editing all Aerofly FS 2 text files the IPACS development team recommends using one of the following UNICODE capable text editors. | ||
+ | * Visual Studio 2019 | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
* Windows Wordpad | * Windows Wordpad | ||
+ | |||
===== Language ===== | ===== Language ===== | ||
Throughout all files of the Aerofly FS 2 English is the language of choice. Descriptive names that are usually separated by white spaces in the common language or hyphens are usually written in CamelCase in the Aerofly FS 2 files. This means that the spaces and hyphens are left away and the following letter after the separation is turned into an upper case letter instead. | Throughout all files of the Aerofly FS 2 English is the language of choice. Descriptive names that are usually separated by white spaces in the common language or hyphens are usually written in CamelCase in the Aerofly FS 2 files. This means that the spaces and hyphens are left away and the following letter after the separation is turned into an upper case letter instead. | ||
+ | |||
+ | ===== Units and Coordinate Systems ===== | ||
+ | |||
+ | Aerofly FS 2 uses the international system of units (SI) exclusively. This means that all lengths and dimensions are meters, masses are in kilograms, forces are in Newtons, power values are in Watts, speeds are in meters per second. | ||
+ | Any rotation uses the positive mathematical direction (anti-clockwise), | ||
+ | Fractions are used instead of percentages (20% would be written as 0.2). | ||
+ | |||
+ | The coordinate system the entire aircraft is defined in the 3D model of the aircraft. The origin is usually placed close to the center of gravity but does not have to be. The forward flight direction defines the x-axis of the aircraft' | ||
+ | The y-axis points towards the left of the aircraft, the z-axis points straight up. One unit in the coordinate system represents a real world length of one meter. The 3D model may use a scale factor which is removed when the aircraft is exported. | ||
===== Character Set ===== | ===== Character Set ===== | ||
Line 28: | Line 38: | ||
* ''<'',''>'','' | * ''<'',''>'','' | ||
- | * white spaces for separation of lists | + | * white spaces for separation of lists, indentations and additional spacing |
* digits from '' | * digits from '' | ||
* English-alphabet from '' | * English-alphabet from '' | ||
Line 36: | Line 46: | ||
* \r\n as line endings (carriage return and line-feed) | * \r\n as line endings (carriage return and line-feed) | ||
- | Especially forbidden is the usage of tab indentation or separation. Instead four white spaces are used for indentation and multiple white spaces for separation. | + | Especially forbidden is the usage of **tab** indentation or separation. Instead four white spaces are used for indentation and multiple white spaces for separation. |
===== Syntax ===== | ===== Syntax ===== | ||
Line 45: | Line 55: | ||
A single opening pointy bracket ''<'' | A single opening pointy bracket ''<'' | ||
- | < | + | < |
The first parameter is a definition of the type for the following variable or content. This could be a '' | The first parameter is a definition of the type for the following variable or content. This could be a '' | ||
Line 55: | Line 65: | ||
Here is an example code of an typical nested parameter inside an object: | Here is an example code of an typical nested parameter inside an object: | ||
- | < | + | < |
- | < | + | < |
></ | ></ | ||
Line 63: | Line 73: | ||
Spaces and empty lines can be used throughout the entire file, for example to indent the parameters better: | Spaces and empty lines can be used throughout the entire file, for example to indent the parameters better: | ||
- | < | + | < |
- | < | + | |
< | < | ||
< | < | ||
Line 77: | Line 86: | ||
A comment is started by a double slash '' | A comment is started by a double slash '' | ||
- | > ''/ | + | > ''/ |
simulator/text_files.1484733715.txt.gz · Last modified: 2017/01/18 11:01 by jh