230
edits
List of file formats: Difference between revisions
Jump to navigation
Jump to search
m
add *.ac description
m (mention that RLE is lossless) |
m (add *.ac description) |
||
| Line 1: | Line 1: | ||
= *.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: | |||
=== [http://www.blender3d.org/ Blender] === | |||
See File->Import/Export->AC3d (*.ac) | |||
=== [http://www.openscenegraph.org/ Open Scenegraph Library] === | |||
The <tt>osgviewer</tt> demo is very useful for quickly looking at models. | |||
=== [http://prettypoly.sourceforge.net/ ppe] === | |||
This is an unmaintained object editor that uses the same graphics library as FlightGear (plib). This has the advantage that objects look very much like in FlightGear (minus shader effects and shadows). Compiling ppe may be a challenge, though, and it's only useful for viewing, but hardly for editing objects. | |||
=== threedconvert === | |||
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 = | ||
| Line 7: | Line 25: | ||
All better graphics applications should be able to read and write the format, but often they load SGI images without problems, but only write them properly when the <tt>*.sgi</tt> extension is used. Here are some free applications that create SGI images, along with some usage notes: | All better graphics applications should be able to read and write the format, but often they load SGI images without problems, but only write them properly when the <tt>*.sgi</tt> extension is used. Here are some free applications that create SGI images, along with some usage notes: | ||
=== [http://www.gimp.org GIMP] === | === [http://www.gimp.org/ GIMP] === | ||
Either save the image with extension <tt>*.sgi</tt> and rename it afterwards, or choose in the file dialog "Select Filetype" -> "Silicon Graphics IRIS image". Save with "Aggressive RLE". (The remark about SGI not supporting that is wrong. This is compliant with the file specification from SGI itself.) | Either save the image with extension <tt>*.sgi</tt> and rename it afterwards, or choose in the file dialog "Select Filetype" -> "Silicon Graphics IRIS image". Save with "Aggressive RLE". (The remark about SGI not supporting that is wrong. This is compliant with the file specification from SGI itself.) | ||
=== krita/kolourpaint ([http://www.kde.org/ KDE]) === | |||
=== krita/kolourpaint ([http://www.kde.org KDE]) === | |||
KDE supports reading and writing of SGI images on the base library level, so ''all'' applications that can read/write images in general can also read/write SGI images. They are automatically saved in highest possible compression (more aggressive than GIMP :-) | KDE supports reading and writing of SGI images on the base library level, so ''all'' applications that can read/write images in general can also read/write SGI images. They are automatically saved in highest possible compression (more aggressive than GIMP :-) | ||
=== convert ([http://www.imagemagick.org/ ImageMagick]/[http://www.graphicsmagick.org/ GraphicsMagick]) === | |||
=== convert ([http://www.imagemagick.org ImageMagick]/[http://www.graphicsmagick.org GraphicsMagick]) === | |||
Like with GIMP, it's necessary to either call the target file <tt>*.sgi</tt> or to specify the file type explicitly via <tt>sgi:</tt> prefix: | Like with GIMP, it's necessary to either call the target file <tt>*.sgi</tt> or to specify the file type explicitly via <tt>sgi:</tt> prefix: | ||