http://bundysoft.com/docs/ 2026-05-13T17:44:37+00:00 http://bundysoft.com/docs/ http://bundysoft.com/docs/lib/images/favicon.ico text/html 2017-08-31T05:17:11+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:amf&rev=1504156631&do=diff The L3DT attributes map file (AMF) stores the land type of each pixel in the height map. The 'amf.gz' extension indicates the AMF file has been compressed using the gzip algorithm. The data is preceded by a 10-byte header containing the following information: text/html 2017-08-31T05:28:44+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:cli&rev=1504157324&do=diff climate file XML-based climate file text/html 2017-08-31T06:27:44+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:cli.xml&rev=1504160864&do=diff The L3DT climate file (.cli.xml) is an XML-based file (using L3DT's XML format spec) that contains the settings and parameters of a climate, including appearance (material, etc) and distribution (alt. range, water-affinity parameters, etc). For more information on the climate system in L3DT, please refer to the climate algorithms page. text/html 2017-08-31T05:11:28+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:def&rev=1504156288&do=diff map definition fileXML-based definition file text/html 2011-01-13T03:51:06+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:def.xml&rev=1294890666&do=diff The L3DT map definition (.def.xml) is an XML-based file (using L3DT's XML format spec) that contains the settings used to generate a map, and lists the operations that were performed. These files are automatically saved and loaded along with the map project files, but can also be used to clone a map or generate a batch of maps (see batch generation in the user-guide). text/html 2017-08-31T06:15:19+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:dmf&rev=1504160119&do=diff The L3DT design map file (DMF) stores a number of design parameters for the heightfield, including altitude, erosion strength, sea-flooding flags, and so-forth. The data is preceded by a 11-byte header containing the following information: Field name Contents Length Offset Purpose ASCII marker “L3DT” 4 0 Tells L3DT and humans that this is an L3DT file. Note string is not null terminated. Binary marker USHORT 2 4 Tells L3DT what type of map file this is. Must be… text/html 2011-01-13T03:51:07+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:hf2&rev=1294890667&do=diff Overview HF2 is a compressed heightfield format designed to replace uncompressed terrain formats such as HFF, TER and BT. In addition to smaller file sizes thanks to difference and gzip encoding, the HF2 format also includes an section for storing additional metadata such as georeferencing coordinates, comments, and the like. Thus, HF2 was designed with extensibility in mind. text/html 2011-01-13T03:51:07+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:hff&rev=1294890667&do=diff Introduction The default file format for L3DT heightfields is HFF v1.0. This file format supports single precision floating-point data, 2-byte unsigned integer data and unsigned byte data. In the case of integer data, the vertical scaling and offset are used to stretch the byte range across the minimum and maximum altitudes in the heightfield, giving maximum fidelity. text/html 2017-08-31T06:40:33+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:ini.xml&rev=1504161633&do=diff The L3DT application settings files (.ini.xml) is an XML-based file (using L3DT's XML format spec) used to store and recall settings and preferences. These settings can, in general, be edited from the settings menu, so there shouldn't be a need to tinker with these files directly. text/html 2017-08-31T05:43:37+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:lmf&rev=1504158217&do=diff light map fileJPEGPNG text/html 2017-08-31T05:54:46+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:mat.xml&rev=1504158886&do=diff The L3DT material file (.mat.xml) is an XML-based file (using L3DT's XML format spec) that contains the texture and bump-map settings and parameters of a material. For more information on the climate/material system in L3DT, please refer to the climate algorithms page. text/html 2017-08-31T04:42:08+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:mgf&rev=1504154528&do=diff map group fileXML-based project file text/html 2017-08-31T05:18:58+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:mmf&rev=1504156738&do=diff The L3DT mosaic master file (*.mmf) is an ASCII file that describes the size and number of map files within a mosaic map. A typical MMF might look like this: L3DT Mosaic master file #MosaicName: Alpha1 #MosaicType: RGB #FileExt: bmp #nPxlsX: 4096 #nPxlsY: 2048 #nMapsX: 8 #nMapsY: 4 #SubMapSize: 512 #HorizScale: 1.00 #TileState: 0 OK #TileState: 1 OK #TileState: 2 OK #TileState: 3 OK #TileState: 4 OK #TileState: 5 OK #TileState: 6 OK #TileState: 7 OK #TileState: 8 OK #TileState: 9 OK #TileSta… text/html 2011-01-13T03:51:09+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:proj&rev=1294890669&do=diff The L3DT map project file (.proj) is an XML-based file (using L3DT's XML format spec) that lists the files in a map project (such as heightfield and texture filenames), and some pertinent settings (including map size, etc). These project files may be thought of as the main 'document' file used by L3DT. text/html 2013-08-22T00:20:24+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:raw&rev=1377130824&do=diff The raw binary data file (.RAW) is an unstandardised - but usually simple - file format that is used to exchange data between programs. RAW files usually contain no header, which makes them unsuitable as a general purpose format, and this L3DT supports RAW for import and export only (though mosaic maps are supported). text/html 2017-08-31T05:26:48+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:run&rev=1504157208&do=diff The L3DT batch file format (.run) is a simple text-based format used for the generation of multiple maps automatically (see user-guide). An example RUN file is provided below, which specifies the map definition files (.def.xml) to be used, the directories to which the maps will be saved, the map output filename (root name), and the number of copies to be made. text/html 2017-08-31T05:45:15+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:tnf&rev=1504158315&do=diff terrain normals fileJPEGPNG text/html 2017-08-31T05:21:13+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:wmf&rev=1504156873&do=diff The current file format for L3DT water maps is WMF v1.0. This file format is largely based on the HFF v1.0 format, but also supports multiple data layers (water level, water type, water ID#). The header structure is as follows: Header structure The water data in the WMF v1.0 file is preceded by a header containing the following information: text/html 2017-08-31T07:31:36+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:xml&rev=1504164696&do=diff L3DT uses the eXtensible Markup Language to store settings in text files, such as the project file (.proj), climate file (.cli.xml), and the application settings file (.ini.xml). Because I like writing code, I've made my own XML writer and parser. However, since I'm not a total masochist, I have not implemented the entire XML standard in L3DT's parser. Therefore, if you intent to write XML files for L3DT to read (for example, writing your own climate editor), you must conform to several requ… text/html 2017-08-31T07:25:39+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:zeo&rev=1504164339&do=diff Thge Zeolite plugin file (.zeo) is a 32-bit Windows Dynamic Linked Library, build with the Zeolite plugin API. ZEO files are exactly equivalent to DLL files, and the DLL extension may be used instead of ZEO. text/html 2017-08-31T06:59:51+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:zfilter&rev=1504162791&do=diff ZFILTER files are text files that define filters used by the ZeoGraph plugin. ZFILTER files are stored in the following directory: Win 7 / Vista C:\Users\[username]\L3DT\Resources\[version]\Filters\ Win XP / 2000 C:\Documents and Settings\[username]\L3DT\Resources\[version]\Filters\ File sections ZFILTER files consist of the following sections: text/html 2017-08-31T05:09:54+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:zgraph&rev=1504156194&do=diff ZGRAPH files are XML-based file (using L3DT's XML format spec) that are used to store graphs for the ZeoGraph plugin. These files should only be edited using the ZeoGraph interface, and shouldn't be tinkered with directly. ZGRAPH files are stored in the following directory: text/html 2017-08-31T07:09:00+00:00 http://bundysoft.com/docs/doku.php?id=l3dt:formats:specs:zs&rev=1504163340&do=diff The ZeoScript file (.zs) is a plain text file containing a script written in the ZeoScript language. Please refer to the ZeoScript plugin page for examples.