Presagis .flt (OPENFLIGHT) Writer Parameters

If specified, a master file will be created at the end of the writing process. The master file will contain references to the OpenFlight files that have been written out for each feature type during the translation.

The OpenFlight format version by default is 16.1 and can optionally be changed to 15.7 or 15.8.

The folder to write texture files referenced by the OpenFlight .flt files. The texture output folder is generally a subfolder of the output dataset but can be any path relative to the output dataset.

All textures image files for the dataset being produced will be written to this folder. Textured appearances that are shared between feature types of the same dataset will produce OpenFlight materials in different flt files that share the same texture image file. Texture file names are based on the fme appearance name. Existing old files of the same name from another run or another dataset will be overwritten with new files of the same name.

Specifies the preferred format for associated texture files. This preference will be used as long as the specified format supports the properties of the texture raster; if not, it will be overridden.

In the default Auto mode, the writer chooses the best representation based on the incoming texture raster.

If the preferred format is ignored, a message is added to the log file. Possible reasons that the preference will be ignored include a lack of raster palette support, alpha channel support, or color depth support in the selected format.

This parameter determines which texture coordinates will be used when a geometry surface with the same texture on the back and front sides is written. This is because the format supports only one texture.

• Use Front Presentation: Front texture coordinates are written, and back coordinates are ignored.
• Use Back Presentation: Back texture coordinates are written, and front coordinates are ignored.
• Split Surface: Both texture coordinates are output; however, this is done by splitting the surface and outputting two different geodes with the same vertex pool. Use caution when selecting this parameter because it produces very large files.

By default the OpenFlight writer processes all geometry into triangles and creates an flt polygon structure for each triangle. If you choose Yes, the writer will attempt to combine adjacent state sharing triangles into triangle strips and store them in flt mesh structures. This optimization can significantly compress geometry to save space and reduce load time.

Note: If you choose Yes, make sure your OpenFlight consuming applications support the mesh structure as some viewers are known to ignore OpenFlight mesh records.

Note that not all formats offer all the options described below.

• Yes: Coordinates of all the points in the written features will be normalized to the interval [-0.5, 0.5] on the largest side of their XYZ-bounding cube. The other dimensions will be scaled proportionally.

Additionally, the transformation matrix required to scale the model back to world coordinates will be written to a companion .fwt file. This can be used to improve precision of the written coordinates. The companion .fwt file will have the same name as the primary data file and will be written in the same folder. For folder-based formats, the file global.fwt will be written instead.

• No: The original coordinates will be written as provided. Coordinates will not be projected; .fwt world and .prj files will not be generated.
• Create Projection File Only: A companion .prj file containing the coordinate system and having the same name as the primary data file will be written in the same folder. For folder-based formats, the file global.prj will be written instead. Coordinates will not be projected and a world file will not be generated.
• Transform Coordinates Only: Transforms the coordinates as in the Yes option, but companion .prj and .fwt world files will not be generated.