Howto:Edit a livery: Difference between revisions

Jump to navigation Jump to search
Restore categories, remove livery db contribution rules (link to website instead), small cleanups.
(Wording etc.)
(Restore categories, remove livery db contribution rules (link to website instead), small cleanups.)
Line 1: Line 1:
This HOWTO is intended to be a help guiding the potential livery artist as well as the more experienced one needing a refresher.
This [[:Category:howto|howto]] is intended to be a help guiding the potential livery artist as well as the more experienced one needing a refresher.


== What is a livery? ==
== What is a livery? ==
[[File:PC-9M Slovenian Livery.png|150px|thumb|right|Slovenian livery for pjedvaj's second version of the [[Pilatus PC-9M]].]]
[[File:PC-9M Slovenian Livery.png|150px|thumb|right|Slovenian livery for pjedvaj's second version of the [[Pilatus PC-9M]].]]
A ''livery'' is the way an aircraft from as an example an airline or a fighter wing is painted, in some other flight simulators and games they are sometimes called ''textures'' instead, as they are wrapped around the 3D model representing the aircraft.
A ''livery'' is the way an [[aircraft]] from for example an airline or a fighter wing is painted. Some other flight simulators and games call this a '''paint (scheme)''' or '''repaint'''. A livery consists of one or more textures, wrapped around the 3D model representing the aircraft.


Most aircraft in FlightGear comes as a ZIP file which contains a few text, 3D model and image files organized in several directories. In that structure is one or more liveries and on or more text files, XML files, describing it's use. The liveries can usually be found in the <tt>..Models<tt>, <tt>..Liveries</tt>, <tt>..Models/Liveries</tt> or some other directory, depending on how the aircraft's original author organized the files and directories.
Most aircraft in FlightGear come as a ZIP file which contains a few text, 3D model and image files organized in several directories. In that structure is one or more liveries and on or more text files, XML files, describing it's use. The liveries can usually be found in the <tt>..Models<tt>, <tt>..Liveries</tt>, <tt>..Models/Liveries</tt> or some other directory, depending on how the aircraft's author organized the files and directories.


== General work flow ==
== General work flow ==
There are a few ways to make a new livery. First of all have a look at the [http://liveries.flightgear.org/index.php FlightGear Livery Database], to make sure you don't duplicate someones else's work. You can also download templates for liveries, called ''paintkits'', there for a few aircraft , but usually paintkits are included in ZIP file with the aircraft.
There are a few ways to make a new livery. First of all have a look at the [[FlightGear livery database]], to make sure you don't duplicate someones else's work. You can also download templates for liveries, called ''paintkits'', there for a few aircraft, but usually paintkits are included with the aircraft.


When creating the livery, the work flow is basically in this order:
When creating the livery, the work flow is basically in this order:
* Check the FlightGear Livery Database, to avoid duplicate work,
# Check the FlightGear Livery Database, to avoid duplicate work
* find reference images,
# Find reference images,
* get a paintkit if available,
# Get a paintkit, if available,
* make the livery, and
# Make the livery
* share the livery
# Share the livery


== Finding reference images ==
== Finding reference images ==
To do a good livery based on a real aircraft you simply have to have reference images to look at while making the livery. You will need images from both sides of the fuselage, images of the top and bottom, and a lot of close in images of details. Make sure you also have images from an angle as well. Having a three way drawing can be helpful, specially if you want to add rivet lines or if there was no paintkit available.
To do a good livery based on a real aircraft you simply have to have reference images to look at while making the livery. You will need images from both sides of the fuselage, images of the top and bottom, and a lot of close in images of details. Make sure you also have images from an angle. Having a three way drawing can be helpful, specially if you want to add rivet lines, or if there was no paintkit available.


Make sure you have a lot of good reference images of the aircraft livery you want to make.
Make sure you have a lot of good reference images of the aircraft livery you want to make. A list of websites containing such images can be found at the bottom of this article.


== Editing the livery image ==
== Editing the livery image ==
Line 30: Line 30:


=== Vector or raster ===
=== Vector or raster ===
There are in general two ways to edit the livery: Using a raster image editor such as GIMP or Photoshop or using a vector graphics editor such as Inkscape or Illustrator. GIMP and Inkscape are both free and open source software. If you don't have experience with a vector editor there's a bit of a learning curve, but after you have passed it a vector editor can be more rewarding, as you can more easily adjust, scale and rotate elements in the livery such as warning labels, stripes and cabin windows. Vector images also have the great advantage of having the possibility to later make a higher resolution livery in a snap.
There are in general two ways to edit the livery: Using a raster image editor such as GIMP or Photoshop or using a vector graphics editor such as Inkscape or Illustrator. GIMP and Inkscape are both free and open source software. If you don't have experience with a vector editor there's a bit of a learning curve, but after you have passed it a vector editor can be more rewarding, as you can more easily adjust, scale and rotate elements in the livery such as warning labels, stripes and cabin windows. Vector images also have the great advantage of having the possibility to later make a higher resolution livery in a snap.


=== Using layers ===
=== Using layers ===
Line 36: Line 36:


=== Saving the files ===
=== Saving the files ===
''Start'' the work by saving your livery while it is still empty. That way you will not get carried away, forgetting to save it just to be reminded in the harshest way, maybe having hours of work lost. The file should usually have a size of 1024 x 1024 pixels, but any square with n<sup>2</sup> pixels side, for example 256, 512 and 2048 pixels, will do. Larger image size will result in more detail being shown, but also a slower running FlightGear.
''Start'' the work by saving your livery while it is still empty. That way you will not get carried away, forgetting to save it just to be reminded in the harshest way, maybe having hours of work lost. The file should usually have a size of 1024*1024 pixels, but any rectangle with n<sup>2</sup> pixels side, for example 256, 512 and 2048 pixels, will do. Larger image size will result in more detail being shown, but also a slower running FlightGear.


If you are working with raster files, remember to use a two or four times larger size, while working on the livery, in case you later on need a livery in a larger size.  When you are done you can save a version in the right size.  Save the file in a larger size also when creating a raster image paintkit from scratch.
Note that all liveries for a certain aircraft must have the same aspect ratio. So when an existing livery is 1024*2048, your livery can be 512*1024, but not 512*512.


While working on the livery save the file in different versions while you are adding new features, so you don't end up messing your ''only'' file up by mistake. Copy the file, with the right size, to the aircraft's <tt>..Models</tt> directory or <tt>..Models/Liveries</tt> directory, depending on how the original author organized the aircraft's folders, and name it default.png.
If you are working with raster files, remember to use a two or four times larger size, while working on the livery, in case you later on need a livery in a larger size. When you are done you can save a version in the right size. Save the file in a larger size also when creating a raster image paintkit from scratch.
 
While working on the livery save the file in different versions while you are adding new features, so you don't end up messing your ''only'' file up by mistake. Copy the file, with the right size, to the aircraft's <tt>..Models</tt> directory or <tt>..Models/Liveries</tt> directory, depending on how the original author organized the aircraft's folders, and name it default.png.


=== Viewing the livery in 3D ===
=== Viewing the livery in 3D ===
Line 46: Line 48:


To be able to check the livery on a model there are three ways, you can either
To be able to check the livery on a model there are three ways, you can either
* use '''FGRun's''' built in viewer at the aircraft page to look at the model, which is rather slow, or
* use '''[[FGRun]]'s''' built in viewer at the aircraft page to look at the model, which is rather slow.
* use '''3DViewer''', a neat, small and fast viewer, or
* use '''3DViewer''', a neat, small and fast viewer.
* use the 3D modeller '''Blender''', which has quite a steep learning curve.
* use the 3D modeller '''[[Blender]]''', which has quite a steep learning curve.


My recommendation is 3DViewer, since it is small and fast.
My recommendation is 3DViewer, since it is small and fast.


=== Naming your livery ===
=== Naming your livery ===
Lastly, when done give the livery a proper name. For hints on airliners etc. have a look at the livery database. It is usually a good idea to have aircraft model and airline, possibly also years it was used in the file name.
Lastly, when done give the livery a proper name. For hints on airliners etc. have a look at the [http://liveries.flightgear.org/contribute.php livery database's contribute page]. It is usually a good idea to have aircraft model and airline, possibly also years it was used in the file name.


  Details on the XML work needed here.
  Details on the XML work needed here.


== Sharing your work ==
== Sharing your work ==
Please consider sharing your work on the forum, and in the case it is a real livery, and doesn't have parts of non-free images, also the livery database under the GPL license.
Please consider sharing your work on the forum, and in the case it is a real livery and doesn't have parts of non-free images, also the livery database under the GPL license.


=== Showing your livery at the FlightGear forum ===
=== Showing your livery at the FlightGear forum ===
In order to show your liveries at the forum you have to be registered and have uploaded your images of the livery to some external image host like Picasa, Flickr, imageshed or something similar.
In order to show your liveries at the forum you have to be registered and have uploaded your images of the livery to some external image host like Picasa, Flickr, imageshed or something similar.


On the forum there are sometimes a topic for the development of an aircraft as well as a sparate topic for liveries to the same aircraft. Use the forums search function to find any already existing topics. I you doesn't find one make a new one in the [http://www.flightgear.org/forums/viewforum.php?f=13 Development &gt; Aircraft &gt; Liveries] subforum with the name of the aircraft somewhere in the new topic's title.
On the forum there are sometimes a topic for the development of an aircraft as well as a sparate topic for liveries to the same aircraft. Use the forums search function to find any already existing topics. If you cannot find one, make a new one in the [http://www.flightgear.org/forums/viewforum.php?f=13 liveries development] subforum with the name of the aircraft somewhere in the topic's title.


To add the image to your post use your image host's share function or if you do not find it use <tt>[img]</tt> tags like this <tt>[img]&lt;URL to image&gt;[/img]</tt>.
To add the image to your post use your image host's share function or if you do not find it use <tt>[img]</tt> tags like this <tt>[img]&lt;URL to image&gt;[/img]</tt>.
Line 70: Line 72:


=== Uploading to the FlightGear Livery Database ===
=== Uploading to the FlightGear Livery Database ===
You can upload your liveries to the livery database using [http://liveries.flightgear.org/contribute.php a web form]. When uploading, please consider the following (quoted from the contribution page):
You can upload your liveries to the official livery database using [http://liveries.flightgear.org/contribute.php a web form]. Please read the rules and tips carefully before sending in your livery.
 
# '''Your files have to comply with the GNU GPL V2 license.'''
# The livery must exist, or have existed in the real world; on the respective aircraft.
# Zip '''only''' the files you've changed and/or added (eg. textures and livery xmls) and upload them using the button below. Keep in mind that:
## you use the correct ICAO code (can be found at [http://www.airfleets.net/home/ Airfleets.net]) for your livery. If the airline does not have an ICAO code, or the livery is based on a private one, the registration of the aircraft can be used instead.
## the .xml file must be in the form of ICAO.xml.
## the texture must be in .png format and named like ICAO.png.
## both files should be placed inside the Models/Liveries/ directory.
# Each livery will be checked before it is commited; you might receive an e-mail with requests for improvements or additional files.
# Include a JPG image of the livery (of the flying (!) aircraft) in a 350*250 (w*h) resolution.


=== Uploading to Unitedfreeworld.com ===
=== Uploading to Unitedfreeworld.com ===
Line 86: Line 78:


Unitedfreeworld uses a Creative Commons-Attribution-Non commercial-No derivates (CC-by-nc-nd) licence and recommends you to adhere to that, and that your livery contains no copyrighted material, in essence that it is your own work entirely.
Unitedfreeworld uses a Creative Commons-Attribution-Non commercial-No derivates (CC-by-nc-nd) licence and recommends you to adhere to that, and that your livery contains no copyrighted material, in essence that it is your own work entirely.
:"...we also encourage you to upload packages in accordance to terms and conditions of this site. Simply put, ensure your packages are works of your own, virus free, contains no copy right materials and most importantly, your willingness to share them for free and no commercial gains."


== A pledge to aircraft developers and livery artists ==
== A pledge to aircraft developers and livery artists ==
Some one else would likely want to have a try at liveries for the aircraft you are working on. When you are developing an aircraft or are making a new livery for an aircraft without a painkit, please consider making a paintkit for that aircraft. Also consider that the aircraft will more likely get higher quality liveries and more liveries if your paintkit are of high quality.  
Some one else would likely want to have a try at liveries for the aircraft you are working on. When you are developing an aircraft or are making a new livery for an aircraft without a painkit, please consider making a paintkit for that aircraft. Also consider that the aircraft will more likely get higher quality liveries and more liveries if your paintkit is of high quality.  


== See also ==
== Related content ==
* [[Livery over MP]]
* [[Livery over MP]], describes how to equip an aircraft with a livery system.


== External links ==
== External links ==
* [http://liveries.flightgear.org/index.php FlightGear Livery Database]
* [http://liveries.flightgear.org/index.php FlightGear Livery Database]
* [http://www.unitedfreeworld.com/ Unitedfreeworld.com]
* [http://www.unitedfreeworld.com/ Unitedfreeworld.com]
* [http://www.gnu.org/licenses/gpl-2.0.html GNU General Public License, version 2]


=== Web sites for reference images ===
=== Web sites for reference images ===
* [http://www.google.se/imghp Google image search] The obvius
A small selection. Many, many more are available these days.
* [http://www.google.se/imghp Google image search] The obvious
* [http://www.airliners.net/ Airliners.net] Well known
* [http://www.airliners.net/ Airliners.net] Well known
* [http://www.airplane-pictures.net/ Airplane-Pictures.net] Many ways to browse through the images
* [http://www.airplane-pictures.net/ Airplane-Pictures.net] Many ways to browse through the images
* [http://www.jetphotos.net/ JetPhotos.Net]
* [http://www.jetphotos.net/ JetPhotos.Net]
* [http://www.planepictures.net/ PlanePictures]
* [http://www.planepictures.net/ PlanePictures]
* And many, many more.


=== 3D Viewers ===
=== 3D Viewers ===
* [http://karelse.home.xs4all.nl/3DViewer/ 3DViewer] Small, neat and fast.
* [http://karelse.home.xs4all.nl/3DViewer/ 3DViewer] Small, neat and fast.
[[Category:Aircraft enhancement|Edit a livery]]
[[Category:Howto|Edit a livery]]
[[de:Howto: Edit a livery]]

Navigation menu