Howto:Edit a livery: Difference between revisions

Jump to navigation Jump to search
Being bold: Deleting all text, and copying text from my draft at User:Johan G/Howto: Edit a livery.
m (Only add "other" languages, so no English on this page ;))
(Being bold: Deleting all text, and copying text from my draft at User:Johan G/Howto: Edit a livery.)
Line 1: Line 1:
In this [[:Category:Howto|howto]] I will explain how to change the existing livery of a [[aircraft|plane]] in [[FlightGear]]. The examples that are given are based on a KLM Royal Dutch Airlines livery for the [[Boeing 707]].
This HOWTO is intended to be a help guiding the potential livery artist as well as the more experienced one needing a refresher.


'''Note: this method is not the best way any more. New planes will use the method described in the [[Livery over MP]] article.'''
== 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]].]]
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.


=== Basic ===
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.
# Find all original texture files that are used by the plane. Most of the planes have stored their textures in the <tt>.../Models</tt> directory. The fileformat we use is .rgb. This format can't be opened by some common software like paint. So to open it in paint (or any other graphical editor without .rgb support) we first need to convert the image to another format. We will use [http://www.gimp.org Gimp], a free editor.
# Open the .rgb texture file of the aircraft in Gimp and save it as .png.
# Now we can open the texture in every editor. A simple image editor to use is Paint, which can be found on all Windows computers.
# After you've edited the texture you save it. Now we open the saved file in Gimp and save it again, but now as .rgb.
# Replace the texture(s) to the aircraft's <tt>.../Models/</tt> directory.
# Launch FlightGear and select your aircraft. If you did everything as described you should now see the plane with your livery!


=== A little further ===
== General work flow ==
You now know how to edit a livery. But we want to have multiple planes that we could choose in FlightGear, so we won't need to change the texture files everytime we want to "play" with another skin. That's why we need to make some extra files.
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.


# Copy the 707-set.xml file from your plane and rename it to 707-KLM.xml.
When creating the livery, the work flow is basically in this order:
# Open the 707-KLM-set.xml file with a text editor like Notepad (you'd better use a real .xml editor) and change the following things:
* Check the FlightGear Livery Database, to avoid duplicate work,
#* <tt><description>Boeing 707</description></tt> to <tt><description>Boeing 707 KLM</description></tt>
* find reference images,
#* <tt><model><path>Aircraft/707/Models/707.xml</path></model></tt> to <tt><model><path>Aircraft/707/Models/707-KLM.xml</path></model></tt>
* get a paintkit if available,
# Copy the 707.xml file from your plane's 707/Models directory and rename it to 707-KLM.xml.
* make the livery, and
# Save the new .rgb texture in a directory like <tt>Models/Textures/KLM/</tt>.
* share the livery
# Open the 707-KLM.xml file with a text editor and add the following line, just below the <model> tags: <tt><texture-path>Textures/KLM/</texture-path></tt>
Now you're done and you could launch FlightGear. If you did everything as described you will see your plane now below the original plane in the [[FlightGear Launch Control|FlightGear Wizard]].


== Sharing your liveries ==
== Finding reference images ==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefor, other users should be able to download them.
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.


We have some FlightGear hosts, where you can upload your liveries to:
Make sure you have a lot of good reference images of the aircraft livery you want to make.
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.


== A Note to Those who wish to make a Livery ==
== Editing the livery image ==
If you are planning to make a Livery, and your Livery is likely to be edited by other Users, Then consider making a Paintkit in addition to your Livery.
[[File:Vector vs Raster Graphics.png|150px|thumb|right|The difference between vector and raster graphics. One pixel line width circle and square together with a gradient.]]
A paintkit is where you create a blank Livery which shows only constructional elements like bolts, rivets, windows, doors, panels and things like those. This is done so any other users looking to create their own Livery can Make a realistic looking Livery with these construction Elements without having to redraw them or trying to avoid painting over them, and makes the process of creating a Livery a more fun and less stressful Task.
[[File:Livery layers in Inkscape (Slovenian PC-9M).png|150px|thumb|right|Inkscape layer dialogue. The four top top layers are the paintkit, while the rest of the layers are the livery.]]
[[File:Finished Slovenian PC-9M livery (3DViewer screenshot).png|150px|thumb|right|3DViewer screen shot of a finished livery draped over the model.]]
[[File:Finished Slovenian PC-9M livery (in-game screenshot).png|150px|thumb|right|FlightGear 2.0.0 in-game screen shot with the finished livery.]]
To be on the safe side copy the aircraft folder to some other place while you work on the livery.


Here is an example of a Paintkit for the Bombardier CRJ-700 from Flight Sim 10:
=== Vector or raster ===
[http://fsx-repaints.com/downloads/7pk.jpg]
There are in general two ways to edit the livery: Using a raster image editor such as GIMP or Photoshop or using a vector editor such as Inkscape or Illustrator.  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 and scale 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.


== Related content ==
=== Using layers ===
* [[Livery over MP]] you need to use this method if you want to get your liveries included in [[FlightGear CVS]].
When editing the livery, have the template in one layer, adding the elements of your livery in other layers.  If you would be using a raster editor it is a good idea to use a two or four times higher resolution in case you would want a higher resolution livery later on. Another good idea if you are using a raster editor is to have individual elements as separate layers to be able to move them around if necessary.


[[Category:Aircraft enhancement|Edit a livery]]
=== Saving the files ===
[[Category:Howto|Edit a livery]]
''Start'' the work by saving the 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 mean more detail shown, but also a slower running FlightGear.


[[de:Howto: Edit a livery]]
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 need a livery in a larger 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 ===
While you are working on the livery it is a good idea to load it into a 3D viewer, turning the model around and comparing it to your reference images at regular intervals.
 
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 '''3DViewer''', a neat, small and fast viewer, or
* use the 3D modeller '''Blender''', which has quite a steep learning curve.
 
My recommendation is 3DViewer, since it is small and fast.
 
=== 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.
 
Details on the XML work needed here.
 
== 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.
 
=== 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.
 
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.
 
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 share your livery you have to upload it to a file host and link to it with the <tt>[url]</tt> tags like this <tt>[url=&lt;URL to file&gt;]&lt;Description of file&gt;[/url]</tt>.
 
=== 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):
 
# '''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 ===
Both real and fictional liveries can be uploaded to Unitedfreeworld.com using [http://www.unitedfreeworld.com/contribute/ a web form].
 
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 ==
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.
 
== See also ==
* [[Livery over MP]]
 
== External links ==
* [http://liveries.flightgear.org/index.php FlightGear Livery Database]
* [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 ===
* [http://www.google.se/imghp Google image search] The obvius
* [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.jetphotos.net/ JetPhotos.Net]
* [http://www.planepictures.net/ PlanePictures]
* And many, many more.
 
=== 3D Viewers ===
* [http://karelse.home.xs4all.nl/3DViewer/ 3DViewer] Small, neat and fast.

Navigation menu