Howto:Install aircraft: Difference between revisions

Jump to navigation Jump to search

Howto:Install aircraft (view source)

Revision as of 16:34, 18 April 2016

181 bytes added ,  18 April 2016
Removed wrong assumption, Folder name does not have to match $aircraft-set.xml name. Added proper explanation.
(updated with Git info for renaming the folder so FG will work as expected)
(Removed wrong assumption, Folder name does not have to match $aircraft-set.xml name. Added proper explanation.)
Line 31: Line 31:


== When installing an aircraft fails ==
== When installing an aircraft fails ==
=== Rename Aircraft Folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.
If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.
Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.
For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.
=== XML files with wrong encoding ===  
=== XML files with wrong encoding ===  
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.
Line 39: Line 53:
  $ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
  $ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'


=== Rename Aircraft Folder ===
If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the [http://forum.flightgear.org/viewforum.php?f=11 forum].
If you start FlightGear with the aircraft you installed it is invisible or if FlightGear will not start with your newly installed aircraft, but will start with other aircraft you might need to rename the aircraft folder.
 
If there is a readme file have a look there for instructions, otherwise try change to more obvious names like renaming for example "A320-master" to "A320" or "boeing-707" to "707".  If that does not work ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the [http://forum.flightgear.org/viewforum.php?f=11 forum].
 
==== Installing From Git Repo ====
If you have downloaded a *.zip file of an aircraft from github or other online repository you must rename the extracted folder name and remove the -[branch] tag. The folder name must correspond to the [/b]<aircraft>[/b]-set.xml file contained inside of the extracted folder. This is something that git automatically does when you download a zip file. The better way would be to learn and use git
 
$ git clone http://repo.address/here.git


== Choosing aircraft ==
== Choosing aircraft ==
I4dnf
422

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/97222"

Navigation menu