8,602
edits
List of file formats: Difference between revisions
Jump to navigation
Jump to search
m
Fix apt.dat link + Resize headings
Screwdriver (talk | contribs) m (Added link to apt.dat format on x-plane.org) |
m (Fix apt.dat link + Resize headings) |
||
| Line 1: | Line 1: | ||
= *.ac = | == *.ac == | ||
This is the native format for 3D graphics written by the [http://www.ac3d.org/ AC3D] application (payware with free trial version). These files contains meshes, UV-mappings, texture paths and material definitions. The format is FlightGear's preferred (i.e. best supported) format. It's ASCII text and easy to edit by hand or via scripts. Many applications are able to import and/or export this format: | This is the native format for 3D graphics written by the [http://www.ac3d.org/ AC3D] application (payware with free trial version). These files contains meshes, UV-mappings, texture paths and material definitions. The format is FlightGear's preferred (i.e. best supported) format. It's ASCII text and easy to edit by hand or via scripts. Many applications are able to import and/or export this format: | ||
| Line 15: | Line 14: | ||
This is a converter for all plib supported 3D formats and comes with FlightGear (see utils/Modeller/3dconvert.cxx). It can read and write <tt>*.ac</tt> files, but a written file may lack UV mapping or have other defects. | This is a converter for all plib supported 3D formats and comes with FlightGear (see utils/Modeller/3dconvert.cxx). It can read and write <tt>*.ac</tt> files, but a written file may lack UV mapping or have other defects. | ||
== *.rgb == | |||
= *.rgb = | |||
These files are texture files in [http://en.wikipedia.org/wiki/Silicon_Graphics SGI] Image Format. This format supports multiple layers, transparency, compression, indexed colors, 8 bits and 16 bits per plane. Files of this format use different extensions, often to indicate the image properties, but in fact it's always the same format. The "official" extensions is <tt>*.sgi</tt>. Images with one layer are usually black/white (<tt>*.bw</tt>) or a mere alpha layer (<tt>*.a</tt>), with two layers black/white with alpha, with three layers red/green/blue (<tt>*.rgb</tt>), and with four layers red/green/blue/alpha (<tt>*.rgba</tt>). This, however, is only a convention and not mandated by the SGI image specification. SGI images can be uncompressed or [http://en.wikipedia.org/wiki/Run-length_encoding RLE-compressed], which is a lossless compression method. | These files are texture files in [http://en.wikipedia.org/wiki/Silicon_Graphics SGI] Image Format. This format supports multiple layers, transparency, compression, indexed colors, 8 bits and 16 bits per plane. Files of this format use different extensions, often to indicate the image properties, but in fact it's always the same format. The "official" extensions is <tt>*.sgi</tt>. Images with one layer are usually black/white (<tt>*.bw</tt>) or a mere alpha layer (<tt>*.a</tt>), with two layers black/white with alpha, with three layers red/green/blue (<tt>*.rgb</tt>), and with four layers red/green/blue/alpha (<tt>*.rgba</tt>). This, however, is only a convention and not mandated by the SGI image specification. SGI images can be uncompressed or [http://en.wikipedia.org/wiki/Run-length_encoding RLE-compressed], which is a lossless compression method. | ||
| Line 54: | Line 50: | ||
done | done | ||
= *.stg = | == *.stg == | ||
This entry is copied from $FG_ROOT/Docs/README.scenery, which is part of FlightGear >0.9.10. | This entry is copied from $FG_ROOT/Docs/README.scenery, which is part of FlightGear >0.9.10. | ||
stg files ("static terragear") define the static elements of a scenery "tile", including the terrain elevation data, airport geometry, and all static objects placed on this tile. Four of the available key words are followed by a string and four numbers. The meaning of these numbers is always the same and described under OBJECT_SHARED. | stg files ("static terragear") define the static elements of a scenery "tile", including the terrain elevation data, airport geometry, and all static objects placed on this tile. Four of the available key words are followed by a string and four numbers. The meaning of these numbers is always the same and described under OBJECT_SHARED. | ||
=== OBJECT_BASE === | === OBJECT_BASE === | ||
| Line 109: | Line 102: | ||
=== OBJECT_SIGN === | === OBJECT_SIGN === | ||
{{main article|Signs}} | |||
defines taxiway or runway sign. The syntax is like that of OBJECT_SHARED entries, except that the path is replaced with a sign contents specification. This specification will probably be changed. Look at $FG_ROOT/Docs/README.scenery if you need to use this entry. | defines taxiway or runway sign. The syntax is like that of OBJECT_SHARED entries, except that the path is replaced with a sign contents specification. This specification will probably be changed. Look at $FG_ROOT/Docs/README.scenery if you need to use this entry. | ||
| Line 114: | Line 108: | ||
are experimental entries. Don't use them! | are experimental entries. Don't use them! | ||
== apt.dat == | |||
= apt.dat = | See [http://data.x-plane.com/file_specs/Apt810.htm X-Plane data file definitions - Airport data (apt.dat) 810 version] | ||
See [http:// | |||
[[Category:List]] | [[Category:List]] | ||
[[Category:Software]] | [[Category:Software]] | ||