FlightGear wiki - User contributions [en]

Talk:Input device

2021-05-18T09:21:10Z

J8d4c3:

1.9.1 for Windows doesn't seem to include js_demo.exe at all. Does anyone know where I might find it?

== Saitek x52 pro don't work under Ubuntu 9.10 ==

Hello to everyone,
I have an X52 pro flight control system.

I can't use it under ubuntu. I don't know why. 
I have followed the FG getstartguide.pdf to check the device. 

The commands that I've used to check: 

'''1)''' andrea@andrea-IBM:~$ lsusb 
Bus 004 Device 004: ID 06a3:0762 Saitek PLC 

'''2)''' andrea@andrea-IBM:~$ dmesg | grep Joystick 
[ 875.178360] generic-usb 0003:06A3:0762.0002: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 983.266631] generic-usb 0003:06A3:0762.0003: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 4743.317355] generic-usb 0003:06A3:0762.0004: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 

'''3) Confirming that the driver recognizes your joystick''' andrea@andrea-IBM:~$ js_demo 
Joystick test program. 

Joystick 0 not detected 
Joystick 1 not detected 
Joystick 2 not detected 
Joystick 3 not detected 
Joystick 4 not detected 
Joystick 5 not detected 
Joystick 6 not detected 
Joystick 7 not detected 
 

----
Can anyone help me?
--[[User:Andreasantopietro|Andreasantopietro]] 22:42, 6 August 2010 (UTC)

:: Andreas, please ask support at our forum: {{forum url}} We will be able to help you there. This wiki is only meant for documentation.
:: [[User:Gijs|Gijs]] 07:38, 7 August 2010 (UTC)

== Different configurations for the same stick depending on OS (Linux vs. Windows) ==

I'm using js_demo on Linux (here: Ubuntu Lucid x64 with joystick "SpeedLink Black Widow")
On Linux it's detected as "Mega World USB Game Controller", on Windows js_demo detects a "SL-6640 Black Widow Flightstick".
I define cooliehat left/right and up/down for view direction and view elevation. On Linux the numbering of the cooliehat axis differs from what is detected on Windows. This I can respect by using the number-tag in my XML. Additional view elevation is opposite in both OSs. Linux move up = axis 5 -> -1, move down = axis 5 -> +1; Windows move up = axis 7 -> +1, move down = axis 7 -> -1. How can I respect these differences in my config.xml?
Cheers 
--[[User:D-SKY1|D-SKY1]] 10:54, 7 August 2010 (UTC)

== Some suggestions for improvement ==

Under Built-in Joystick Support:
* Bullet 2: Seeing as they might be adding another "joystick" or they might be starting off with a yoke, rudder and throttle-quadrant, they need to look at ALL the Joystick #n entries.
* Bullet 3: After editing xml file, re-run FG (or from v2.8, Debug Reload Input) to see if it is now using that file (instead of default).

All over the article: Start > Control Panel > Game Controller doesn't work in later versions of Windows.

Also, I am prepared to write details about how to achieve specific things, showing how (and when) to use <binding></binding>, <script></script>, <mod-ctrl></mod-ctrl>; how to handle Unix and Windows assigning different button and axis numbers, and all that stuff.

[[User:Macnab|Macnab]] 05:39, 10 October 2012 (EDT)

: Hi,
: looks okay to me. Please make your edits as you please. We can always revert/finetune them whenever there is a need for that, so don't feel shy ;-)
: [[User:Gijs|Gijs]] 10:38, 10 October 2012 (EDT)

== Getting different mouse modes when using another control ==

Found this great old tip by mfranz on the {{forum link|p=98106|text=forum}}:
{{cquote|I want to disable the mouse-as-yoke control so that right clicking changes only between pointer and view control.|schwert}}
<pre><nowiki>$ fgfs --prop:input/mice/mouse/mode/button[2]/binding/value=2</nowiki></pre>
I just don't know where to put it.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:16, 31 October 2012 (EDT)

: Nowhere. The upcoming release has a built-in function to change the mouse behaviour ;-)
: [[User:Gijs|Gijs]] 18:12, 21 May 2013 (UTC)

== Multiple devices on Windows ==

Is this tip really necessary anymore? Did it get fixed for Windows? If so, then I don't think it should really be recommended. Also is it version specific, e.g. win XP? [[User:Philosopher|—Philosopher]] 18:07, 21 May 2013 (UTC)

: No idea if it's still valid. But, it's not a "recommendation" for everyone. The article clearly reads "(..) there may be cases, where the same driver name is reported twice. In this case (..)" It could use some rewording though, to make it more clear that this is in general not required.
: [[User:Gijs|Gijs]] 18:12, 21 May 2013 (UTC)

== Name: "Joystick" or "Input Device" ==

I'm wondering if we should move this back to "Joystick" as, contrary to Gijs' message [http://wiki.flightgear.org/index.php?title=Input_device&diff=51832&oldid=51831], it seems like it only covers what it calls "joysticks". I mean, yes it does have a section "Joystick or yoke?", but after that "joystick" is used to denote both types of device, while "input device" could refer to mice, keyboards, and other things (like 3DConnexion products). So I would suggest that we move it back to "joystick", because even though that term doesn't technically include yokes, it sorta does imply it at least ;-). (As evidenced by the fact that [[Yoke]] already redirects to [[Joystick]].) Just my 2¢. [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 14:16, 4 April 2014 (UTC)

:What about "Joysticks and other controls" or "Joysticks and other input devices"?
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:00, 21 April 2014 (UTC)

== Saitek ST290 Pro Joystick with Windows 10 ==
The following information are notes I made to document the symptoms I am having. 
Valid for FlightGear version 2020.3.8 and earlier using default config file with Windows 10 64 bit. 
Years ago, the joystick worked correctly. But I can't remember with what FlightGear version. 
I also created a fix when the problem first started. But I can't remember what I did and I apparently didn't create a notes file saying what I did. 
Problem is there using the default drivers from Windows 10 64 bit and with Saitek's drivers. 
To get a nice graphical image to verify the joystick works, install driver and software from saitek.com: 
# Open Windows Settings / Devices / Devices and Printer. Right-click on the joystick. Select "Game Controller Settings". Click on Properties.
# That opens a dialog box showing an image of the joystick and its controls.
# Can use it to verify that the joystick works.
For me: the dialog box shows that everything works properly. 
However, FlightGear's Joystick Configuration window shows: 
..... = control's input value changes proportionally to control's position. 
Axis 0 Aileron = -1.0 at full left aileron ...... 1.0 at rest, 1.0 at full right aileron. Bad = Should be 0.0 at rest. Also, no change from at rest to full right aileron. 
Axis 1 Elevator = -1.0 at full nose down ..... 0 at rest ..... 1.0 at full nose up. This works correctly. 
Axis 2 Throttle = 0 at no throttle, -1.0 for anything other than no throttle. Values at bottom of window shows .5 and 1.0. Bad = Input values do not change proportional to control position. 
Axis 3 rudder = -1.0 at full left rudder, 1.0 at rest, 1.0 at full right rudder. Bad = Should be 0.0 at rest. Also, no change from at rest to full right rudder. 
Axis 6 & 7 are assigned to the hat button and work correctly.

Talk:Input device

2021-05-18T09:17:44Z

J8d4c3: Saitek ST290 PRO Joystick Problem

1.9.1 for Windows doesn't seem to include js_demo.exe at all. Does anyone know where I might find it?

== Saitek x52 pro don't work under Ubuntu 9.10 ==

Hello to everyone,
I have an X52 pro flight control system.

I can't use it under ubuntu. I don't know why. 
I have followed the FG getstartguide.pdf to check the device. 

The commands that I've used to check: 

'''1)''' andrea@andrea-IBM:~$ lsusb 
Bus 004 Device 004: ID 06a3:0762 Saitek PLC 

'''2)''' andrea@andrea-IBM:~$ dmesg | grep Joystick 
[ 875.178360] generic-usb 0003:06A3:0762.0002: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 983.266631] generic-usb 0003:06A3:0762.0003: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 4743.317355] generic-usb 0003:06A3:0762.0004: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 

'''3) Confirming that the driver recognizes your joystick''' andrea@andrea-IBM:~$ js_demo 
Joystick test program. 

Joystick 0 not detected 
Joystick 1 not detected 
Joystick 2 not detected 
Joystick 3 not detected 
Joystick 4 not detected 
Joystick 5 not detected 
Joystick 6 not detected 
Joystick 7 not detected 
 

----
Can anyone help me?
--[[User:Andreasantopietro|Andreasantopietro]] 22:42, 6 August 2010 (UTC)

:: Andreas, please ask support at our forum: {{forum url}} We will be able to help you there. This wiki is only meant for documentation.
:: [[User:Gijs|Gijs]] 07:38, 7 August 2010 (UTC)

== Different configurations for the same stick depending on OS (Linux vs. Windows) ==

I'm using js_demo on Linux (here: Ubuntu Lucid x64 with joystick "SpeedLink Black Widow")
On Linux it's detected as "Mega World USB Game Controller", on Windows js_demo detects a "SL-6640 Black Widow Flightstick".
I define cooliehat left/right and up/down for view direction and view elevation. On Linux the numbering of the cooliehat axis differs from what is detected on Windows. This I can respect by using the number-tag in my XML. Additional view elevation is opposite in both OSs. Linux move up = axis 5 -> -1, move down = axis 5 -> +1; Windows move up = axis 7 -> +1, move down = axis 7 -> -1. How can I respect these differences in my config.xml?
Cheers 
--[[User:D-SKY1|D-SKY1]] 10:54, 7 August 2010 (UTC)

== Some suggestions for improvement ==

Under Built-in Joystick Support:
* Bullet 2: Seeing as they might be adding another "joystick" or they might be starting off with a yoke, rudder and throttle-quadrant, they need to look at ALL the Joystick #n entries.
* Bullet 3: After editing xml file, re-run FG (or from v2.8, Debug Reload Input) to see if it is now using that file (instead of default).

All over the article: Start > Control Panel > Game Controller doesn't work in later versions of Windows.

Also, I am prepared to write details about how to achieve specific things, showing how (and when) to use <binding></binding>, <script></script>, <mod-ctrl></mod-ctrl>; how to handle Unix and Windows assigning different button and axis numbers, and all that stuff.

[[User:Macnab|Macnab]] 05:39, 10 October 2012 (EDT)

: Hi,
: looks okay to me. Please make your edits as you please. We can always revert/finetune them whenever there is a need for that, so don't feel shy ;-)
: [[User:Gijs|Gijs]] 10:38, 10 October 2012 (EDT)

== Getting different mouse modes when using another control ==

Found this great old tip by mfranz on the {{forum link|p=98106|text=forum}}:
{{cquote|I want to disable the mouse-as-yoke control so that right clicking changes only between pointer and view control.|schwert}}
<pre><nowiki>$ fgfs --prop:input/mice/mouse/mode/button[2]/binding/value=2</nowiki></pre>
I just don't know where to put it.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:16, 31 October 2012 (EDT)

: Nowhere. The upcoming release has a built-in function to change the mouse behaviour ;-)
: [[User:Gijs|Gijs]] 18:12, 21 May 2013 (UTC)

== Multiple devices on Windows ==

Is this tip really necessary anymore? Did it get fixed for Windows? If so, then I don't think it should really be recommended. Also is it version specific, e.g. win XP? [[User:Philosopher|—Philosopher]] 18:07, 21 May 2013 (UTC)

: No idea if it's still valid. But, it's not a "recommendation" for everyone. The article clearly reads "(..) there may be cases, where the same driver name is reported twice. In this case (..)" It could use some rewording though, to make it more clear that this is in general not required.
: [[User:Gijs|Gijs]] 18:12, 21 May 2013 (UTC)

== Name: "Joystick" or "Input Device" ==

I'm wondering if we should move this back to "Joystick" as, contrary to Gijs' message [http://wiki.flightgear.org/index.php?title=Input_device&diff=51832&oldid=51831], it seems like it only covers what it calls "joysticks". I mean, yes it does have a section "Joystick or yoke?", but after that "joystick" is used to denote both types of device, while "input device" could refer to mice, keyboards, and other things (like 3DConnexion products). So I would suggest that we move it back to "joystick", because even though that term doesn't technically include yokes, it sorta does imply it at least ;-). (As evidenced by the fact that [[Yoke]] already redirects to [[Joystick]].) Just my 2¢. [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 14:16, 4 April 2014 (UTC)

:What about "Joysticks and other controls" or "Joysticks and other input devices"?
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 10:00, 21 April 2014 (UTC)

== Saitek ST290 Pro Joystick with Windows 10 ==
The following information are notes I made to document the symptoms I am having. 
Valid for FlightGear version 2020.3.8 and earlier using default config file with Windows 10 64 bit. 
Years ago, the joystick worked correctly. But I can't remember with what FlightGear version. 
I also created a fix when the problem first started. But I can't remember what I did and I apparently didn't create a notes file saying what I did. 
Problem is there using the default drivers from Windows 10 64 bit and with Saitek's drivers. 
To get a nice graphical image to verify the joystick works, install driver and software from saitek.com: 
# Open Windows Settings / Devices / Devices and Printer. Right-click on the joystick. Select "Game Controller Settings". Click on Properties.
# That opens a dialog box showing an image of the joystick and its controls.
# Can use it to verify that the joystick works.
For me: the dialog box shows that everything works properly. 
However, FlightGear's Joystick Configuration window shows: 
..... = control's input value changes proportionally to control's position. 
Axis 0 Aileron = -1.0 at full left aileron ...... 1.0 at rest, 1.0 at full right aileron. Bad = No change from at rest to full right aileron. 
Axis 1 Elevator = -1.0 at full nose down ..... 0 at rest ..... 1.0 at full nose up. This works correctly. 
Axis 2 Throttle = 0 at no throttle, -1.0 for anything other than no throttle. Values at bottom of window shows .5 and 1.0. Bad = Input values do not change proportional to control position. 
Axis 3 rudder = -1.0 at full left rudder, 1.0 at rest, 1.0 at full right rudder. Bad = No change from at rest to full right rudder. 
Axis 6 & 7 are assigned to the hat button and work correctly.

TerraMaster

2019-01-30T15:50:08Z

J8d4c3: Updated latest release date and version

{{note|All users of TerraMaster need to update to v1.2 or later. Previous versions used to download the scenery from Google Code, which has become archived (read-only) as of January 2016. See also [https://github.com/open744/terramaster/issues/9 TerraMaster issue #9].}}

{{Infobox Software
|title = TerraMaster
|logo =
|image = TerraMaster r32 - Global view.png
|developedby = reeed, portree kid
|initialrelease = July 18, 2011
|latestrelease = January 30, 2019 (v2.03)
|writtenin = Java (1.8)
|os =
|platform = Cross-platform
|developmentstatus =
|type = Scenery manager
|license = [[GNU GPL]] v2
|website = https://portree-kid.github.io/terramaster/
}}

'''TerraMaster''' is a graphical [[scenery]] manager that gives you a quick overview of your scenery and makes it easier to maintain that scenery. TerraMaster is a cross platform stand alone application written in Java that synchronises [[TerraSync]] scenery tiles you select with the FlightGear Scenery Database. You can delete scenery tiles if the TerraSync scenery directory takes too much space, and you can also search for airports.

== Overview ==
=== Map ===
When TerraMaster starts it will show a map of the Earth. The map can be zoomed and one or more 1x1 degree tiles can be selected before they are synced or deleted. All the airports within a tile can be shown, and airports can be searched for and be shown.

=== Icons ===
The top row contains a status field, two groups of icon buttons, a search field and a sync progress bar. The icons will be grayed out when they can not be used. For more detailed directions, see the section [[#Using|Using]] below. From left to right:
* ''Status field''. Shows the name of the tile that was last selected.

* ''Sync icon''. Syncs the tiles currently selected.
* ''Clock icon''. Syncs old tiles.
* ''Flight icon''. Opens a dialog to help selecting a route.
* ''Trash can icon''. Deletes the currently selected tiles.
* ''Eye icon''. Shows all airports in the first selected tile of the currently selected tiles.
* ''Stop button''. Currently does not work.

* ''Empty paper''. Hides all shown airports.
* ''Globe icon''. Zooms out to the global view.
* ''Gear icon''. Opens a dialogue to select the location of the TerraSync scenery directory.

* ''Search field''. Used to search for airports.

* ''Sync progress bar''. Only visible during syncing.

=== Tile border colours ===
The tiles are colour coded to represent the state of the tiles:

* '''Green''' tiles have both terrain and objects.
* '''Amber/Yellow''' tiles has terrain but no objects. (And are possibly unsyncable - see "Bug", below.)
* '''Red''' tiles are currently selected for synchronisation.
* '''Blue''' tiles are currently being synchronised.

The blue tiles that are being synced will change colour to green or amber/yellow as they are synced. Tiles that get no border after they have been synced don't contain terrain or objects and are usually located in open seas.

== Using ==
[[File:TerraMaster r32 - Mouse hint.png|thumb|Tile information pop-up when holding the mouse pointer over a tile.]]
[[File:TerraMaster r32 - Airports in selected tile.png|thumb|Showing all airports in a selected tile using the "eye" button.]]
[[File:TerraMaster r32 - Searching for an airport.png|thumb|Searching for an airport.]]

=== Zooming and panning ===
TerraMaster with the global view. Left-clicking will zoom you in on an area.

'''Zoom''' using the scroll wheel.

'''Pan''' around by dragging the map while pressing the right mouse button.

Get '''back to global view''' by clicking the "globe" icon.

=== Showing tile information ===
To get some information about a downloaded tile, hold the mouse pointer over it.

A pop-up box will show the name of that tile, if there are terrain and objects in it and what airports it contains. This only works if a tile has been synced, either with Terrasync or TerraMaster.

=== Syncing tiles ===
To '''select just one tile''' left-click it. The scenery for download is available in 1x1 degree tiles.

To '''select more tiles''' press the Ctrl key while left-clicking or left-dragging over the wanted tiles. If you accidentally selected a tile to many, '''deselect tiles''' using it Ctrl+left-click. You can also deselect several tiles using Ctrl+left-click and dragging.

'''Start the update and/or download''' clicking the "sync" icon. The tiles will be downloaded starting from the first tile you selected and proceed in order of distance from it. If you are downloading tiles for a long flight you should then begin by selecting a tile close to the departure airport.

=== Syncing old tiles ===

'''Start the update and/or download''' clicking the 2nd "sync" icon. All previously downloaded tiles that are older than the age given in the settings, will be downloaded.

=== Deleting tiles ===
You can delete files from the TerraSync scenery by selecting the tiles you want to delete and click the "trash can" icon.

=== Showing all airports in a tile ===
To show all airports in a tile, select it and click on the "eye" icon. To hide the airports again, click the "empty paper" icon.

=== Searching for an airport ===
You can search for airports using the search field and pressing enter. The airports location an ICAO code will be shown in white on the map. If you don't see it, zoom out. ICAO airport codes works best, but sometimes the airport's name also work. To hide the airports again, click the "empty paper" icon.

Be warned that the search function is rather slow as it uses a web query to mpmap.flightgear.org and that it also doesn't tell if there was no airports found.

== Video tutorial ==
Here is a short video tutorial:
{{#ev:youtube|YxWV4wk_dHw}}

== Tips ==
* '''Before [[multiplayer]] events''' it might be an idea to sync the related tiles, even more so if you know that someone has crated new buildings etc. and got them into the [[FlightGear Scenery Database|scenery database]].
* If you have very little hard drive space left you can delete tiles you rarely or never fly within.
* Starting TerraMaster in a console window will let you see the sync process, which can be useful if the sync stalls for unknown reasons.
* If you already have a synchronisation running and want to add more tiles to be synced, just mark more tiles as above with Ctrl + leftclick and drag to mark more tiles and press the sync button again.

== Installing ==
Before installing, make sure you have Java 6 or higher, as it is needed.

# Download the newest version of TerraMaster from the [https://github.com/Portree-Kid/terramaster/releases releases page].
# Create a shortcut or script that runs <code>java -jar terramaster.jar</code>.
# When running TerraMaster the first time, click the "gear" icon and select the folder where your TerraSync scenery is located. On some machines you might have to manually edit the property file to have it pointing to the TerraSync directory.
# Done!

== Models ==
<strike>Don't forget that the contents of <tt>''TerraSync/Models''</tt> will have to be copied to <tt>''[[$FG_ROOT]]/Models''</tt> for them to be visible.</strike>

{{note|Since at least FG v3.4, it is no longer necessary to move or copy the <tt>''TerraSync/Models''</tt> folder. FlightGear will find and use the models in the <tt>''TerraSync/Models''</tt> directory with no problems.}}

== Related content ==
* [[FlightGear Admin Wizard]]

== External link ==
* {{forumref|title=TerraMaster: a new scenery manager|f=5|t=12050}}

[[Category:Scenery software]]
[[Category:Java]]

User:J8d4c3

2019-01-29T22:59:27Z

J8d4c3:

These are notes for myself for when or if I reacquire an interest in FlightGear reminding me what problems I was having with this program. 
 
I am abandoning this project. KMYR doesn't have any STAR or SID procedures. FG's navigation dialogs makes a good flightplan so I really see no use for creating procedures. 
A method of creating STARs and SIDs seems to require one of: a standalone app or a tab on FG's start page. Both of which I have neither the interest to invest a lot of time creating or the C/C++/Nasal programming skills required to do it. 
Not finding any free SID/STAR files for airports, I have decided to learn how to create my own. 
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ? 
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws. 
[[User:J8d4c3/Level-D_767_XML_File_Format]]
 

http://wiki.flightgear.org/Osm2city.py 
http://wiki.flightgear.org/Howto:Adding_procedures_to_the_route_manager

Steps to create and add permanent objects to FlightGear's scenery: 
Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it. 
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear? 
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah! 
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet. 
 

Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

Scenery Designer

2019-01-29T22:01:47Z

J8d4c3: Defunct Project?

#redirect[[FlightGear Scenery Designer]]
Defunct Project?

Scenery Designer

2019-01-29T22:00:51Z

J8d4c3: Undo revision 117230 by J8d4c3 (talk)

#redirect[[FlightGear Scenery Designer]]

Scenery Designer

2019-01-29T21:59:10Z

J8d4c3: Defunct Project?

Defunct project? 

#redirect[[FlightGear Scenery Designer]]

Modeling - Getting Started

2019-01-29T21:55:18Z

J8d4c3: Page links to possible defunct project

== Notice for Volunteers ==
{{main article|Volunteer#Scenery Model Creators}}
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

== Getting Started ==

Generally one can start with a blueprint using their favorite imaging software like Gimp, Photoshop, or Paint shop pro then separate various views (front, back, etc...) into greyscale jpg files. Then import them as a background for easy modelling in your favorite 3D modelling software program.

=== 3D Software ===
To begin, you will need to create models in a 3d modeling appliction. Three popular ones are AC3D, Blender and SketchUp. FlightGear can display models in several formats, any format supported by [[PLIB]] is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.

If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.

==== [[AC3D]] ====
Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to [http://www.ac3d.org AC3D] itself, or use [http://www.blender.org Blender] and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.

* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]

==== [[Blender]] ====
[http://www.blender.org Blender] is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.

* [http://wiki.blender.org Blender Manual]
* [http://blenderartists.org/forum/ Excellent forum for discussing Blender issues]

==== SketchUp ====
{{Main article|Modeling - SketchUp}}

SketchUp (http://sketchup.google.com) is the easiest to use of these three programs. But the results are very nice and professional. I recommend SketchUp for users who are not really good at difficult computer programs.

==== [[Wings 3D]] ====
{{Main article|Modeling - Wings 3D}}

Wings 3D (http://www.wings3d.com/) is another 3D modeling program, and is free open source software.

=== Placing Objects on Scenery ===
There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]].

[[File:Placing objects with UFO html 439816e9.jpg|thumb|270px|The model adjustment dialog of the [[UFO]]]]
The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file.

[[Talk:Modeling_-_Getting_Started|Obsolete project?]] Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.

=== Finding, Creating, or Using Textures ===
Models in Flightgear use textures with PNG format.

Most image editors support editing PNG files, like [[THE GIMP]], Corel Paintshop Pro, Adobe Photoshop, etc.

The old SGI rgb format (.rgb extension) is no longer supported. (see http://scenemodels.flightgear.org/)

Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this license. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.

=== Generation of textured light objects in Blender ===

{| style="margin-top:0.1em; margin-bottom:0.1em; margin-left:2em; padding:2px; font-size:95%; text-align:left; background: transparent;"
|-
| [[File:1rightarrow.png|15px]] ''See http://members.aon.at/mfranz/flightgear/blender-textured-lights.html for the main article about this subject.''
|}

== Problems and Solutions ==
* [[3D Model Rotates Around Nose]]
* [[Howto: Configure views in FlightGear]]
* [[Howto: Decrease the number of faces|Decrease the number of faces]]

== Improving models for best FlightGear performance ==
{{Merge|Modelling guidelines}}
[[File:Motor.jpg|thumb|270px|Using Multiple Models with varied detailing]]
[[File:Singlesided_blender.jpg|thumb|270px|To set faces to Singlesided (Blender), deselect the Doublesided button]]
=== Mesh ===
* In a single model, use a single mesh so far as possible. Note that this doesn't mean that every node must be linked to its object with an edge (e.g. a line of trees can be easily a single object.) Only have the separate objects if you need them for an animation or parts that use a transparent texture (any object using more then one texture is anyway spitted by the rendering engine.)
* Delete unseen faces such as faces inside the model, but remember that the [[Project Rembrandt|Rembrandt renderer]] needs closed meshes to cast shadows correctly, so you'll often want to keep the ones below.
* Remove "line faces", which are faces whose points are in the same line.
* Don't forget to remove double vertices (i.e. vertices sharing the same coordinates)
* See [[Howto:Decrease the number of faces]].

=== Single sided / double sided ===
* Set all the faces of the model to SingleSided. DoubleSided faces are very expensive to render properly. If a face needs to be displayed from every view angle use two faces with opposite normals rather than a Doublesided one (the overhead from the extra geometry is far lower than the overhead of doublesided faces)

=== Textures and Materials ===
{{FGCquote
|Modern graphics cards can handle very large textures and huge numbers of vertices with minimal frame rate impact. A typical scene in FlightGear (with clouds, buildings rivers, roads...) has millions of vertices which simply dwarfs a 17K aircraft making the aircraft model an insignificant factor. The general rule is use enough vertices and large enough textures to make things look right and no more. More recent aircraft efforts tend to have much higher vertex counts, much larger textures and a lot more detail then older work because of how capable modern hardware is. It is not unusual to see newer aircraft exceeding 100K vertices. For example the P-51D that will be released with 3.2 has an external model that is slightly over 100K vertices and this had a minimal frame rate impact on my (newer high end) hardware compared to the old 10K external model. 
 
If you can't see the difference between using a 512x512 instrument texture compared to a 256x256 texture then use the smaller texture. But if you can see the difference then use the larger texture. On modern hardware the difference in frame rate will be very small but it may impact those with older/slower/obsolete hardware in a noticeable way. All of the instruments in the P-51D are 512x512 for larger gauges or 256x256 for smaller gauges and at least to me they have a sharp appearance even when zoomed in fairly close. Many older aircraft use 128x128 textures for instruments but to me at least on the larger instruments on a very high resolution monitor these textures are a little bit fuzzy in appearance. The other thing I do is I create the textures at much higher resolution and then scale it to final size. This allows the scaling algorithm in the graphics package to apply anti aliasing during the scaling process which I think helps make the smaller textures look good since it reduces the appearance of jaggies.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=216211#p216211
|title=<nowiki>Re: key + animation</nowiki>
|author=<nowiki>hvengel</nowiki>
|date=<nowiki>Fri Aug 08</nowiki>
}}
}}
* Use Materials on Objects instead of textures where possible, but...
* ...avoid mixing textured and untextured geometry in the same model. Build the coloring into the texture map instead. This is to prevent that the object gets split, and anyway, the [[File Formats#*.ac files|AC format]] supports only one texture per object.
* Textures must be a power of two, or they will be resized at loading, and cause issues to some users.
* Avoid using big textures: 512x512 is mostly enough for most models.
* Use a single texture. However, if your model absolutely needs alpha texture and another part of the model is opaque, you should use two textures: one with alpha and the other without.
* Don't use alpha in texture when it is not needed: transparency is not easy to deal with, and often causes artifacts.

=== Effects ===
* Shader effects (like lightmaps, normalmaps...) and Rembrandt lights are not affordable by everyone's machine, so try to provide alternatives. However, remember also that FlightGear provides options to adjust such effects.

=== Level of Detail (LOD) ===
{{note|Note that range animations often used for LOD are very expensive (any time you move, every range animation must be evaluated), and give a real advantage only if they remove a very large amount of details (like 1000-2000 triangles), so it's not useful in many cases of for example scenery objects or cockpit details.}}
{{tip|Instead of using range animations for each little detail you could group many details together and do the range animation for them all, for example having one range animation for an entire cockpit instead of several dozens.}}
* If a model has to be detailed to a ''very high'' degree, use multiple objects with different levels of detailing, and switch between them based on LOD with a [[Howto:Animate models#Range|range animation]], or split the detailed parts to make them a couple more objects that add details incrementally.
* An alternative, less expensive way to support LOD is applying a [[Howto:Animate models#Select|select animation]], that can hide an object based on some property, for example hiding a cars side mirrors if "detailed" level is at less than 1500m (which is the default), indicating that the user has a less powerful machine. It is less flexible, but allows everyone to enjoy your models.

=== Other ===
* With modern graphics cards, the amount of objects can have a higher impact on performance than the amount of triangles/vertices.
* Textures, transparency, .xml included sub-models: The things that kill frame rate in FlightGear. Try to avoid them.
* Also avoid smooth shading when possible, but don't be afraid to use it for curved surfaces where it really has an impact on model quality.

== Resources ==
* [[Aircraft Information Resources‎]]
* [[Modeling Resources]]

{{3d}}

[[Category:Modeling]]

Talk:Modeling - Getting Started

2019-01-29T21:49:40Z

J8d4c3: Questioning about possible obsolete project.

It isn't obvious from the links: Where would I find information on how aircraft dynamics are modeled in Fligtgear? This must somehow be represented in each aircraft's representation. [[User:BenFrantzDale|BenFrantzDale]] 16:52, 25 June 2007 (EDT)

== <range> animation based LOD ==

I think it would be better if this method (in fact the whole <range> animation) would be not as "visible" as it is now. The drawbacks from using it far outweigh any potential benefit.

It would be better if it was mentioned only in passing in the animation types description, and left at that, without any other suggestion for its usage.

That, and now we have the improved <usage>interior</usage> support that solves the problem in a much more elegant way.

[[User:I4dnf|I4dnf]] ([[User talk:I4dnf|talk]]) 13:00, 5 October 2014 (UTC) 

Is http://wiki.flightgear.org/FlightGear_Scenery_Designer still useful?--[[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 16:49, 29 January 2019 (EST)

FlightGear Scenery Designer

2019-01-29T21:44:04Z

J8d4c3: Deleted link to deleted wiki page.

[[File:fgsd-wiki-title.jpg]]

FlightGear Scenery Designer ( aka fgsd ) is a tool to design and create custom-made scenery tiles suitable to FlightGear. It performs a similar function to [[TerraGear]], but in a different way. TerraGear is intended for batch processing of large numbers of files, and thus is used to produce the global scenery distributed with [[FlightGear]] and via [[TerraSync]]; fgsd is intended more for small-scale fine-tuning of a few tiles through a graphical interface. 
 
<big>'''Project Status'''</big> 
As of March 2011, it does not appear that fgsd is being actively developed.
Links on this page and on pages associated with this project may be bad. 

== Documentation ==

Documentation for fgsd is thin and hard to find. Besides this wiki page, you may want find the following helpful:

* [[Howto: Make an airport]]
* The [http://fgsd.sourceforge.net/doc.html documentation page] of the [http://fgsd.sourceforge.net/ fgsd Sourceforge] website. This includes a four-part video tutorial/demonstration (no sound) illustrating many steps in using fgsd, and instructions on placing static objects.
* The FlightGear Forum, in the scenery section. This seems to be the most current information, but information can be hard to find.

If you find more helpful bits of information, please add it here to make it easier to find.

== History and Philosophy ==

''How fgsd works and what are the ideas that drive its design''

The initial purpose of fgsd was to edit existing scenery because of the lack, at that time, of a decent free elevation model outside the USA. Releases up to 0.3.1 had capabilities to hand-edit part of the terrain. But it appeared to be cumbersome to edit triangles one at a time, and very frustrating as the work done on one tile was obsoleted every time a new global scenery was released. Moreover, editing the result of the [[TerraGear]] process proved to be non-trivial because of hidden gotchas on the topological quality of the tiles.
Finally, NASA and others released the SRTM digital elevation model that offers a more refined elevation dataset for most of the world, lessening the need to edit elevations manually.

From release 0.4.0 ( to be released ) ( and its pre-releases 0.3.9x - Win32 binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] - Other systems, use CVS ), fgsd no longer offers the ability to edit already made scenery tiles. Instead, it works interactively, using the same workflow as [[TerraGear]]. This workflow can be summarized as follow :

* load raw elevations
* simplify elevation model
* prepare land cover contour
* project land cover contour on terrain
* prepare airport layout
* project airport layout on terrain
* export terrain to fgfs scenery tiles

additionally, 3D object models can be placed here and there to add verticality to this somewhat horizontal world.

One side benefit of this approach is that modified land cover contours can be exported to a format that TerraGear can use. A centralized database of contours is setup for that ( see http://www.custom-scenery.org ). This way collaborative changes to the global scenery can be consolidated and the next round of global scenery generation will include submitted individual changes.
Of course, import from the landcover database is possible in fgsd.

Airports are loaded from the airport database file located in the FlightGear base package. It is not possible to edit an airport, but a new definition of an individual airport can be loaded from a file in X-Plane format. This kind of file are typically produced by the Taxidraw airport editor.

== What you need to run fgsd ==

PLEASE ADD TO THIS LIST OTHER PLACES WHERE THESE THINGS CAN BE FOUND.

* fgsd itself.
** Source code from [http://sourceforge.net/projects/fgsd/files/ SourceForge]
** Windows binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here]
* Elevation data from the SRTM ([http://www2.jpl.nasa.gov/srtm/ Shuttle Radio Topography Mission]), in .hgt file format, at either SRTM-3 or SRTM-1 resolution. Please note that if you want your work to eventually be incorporated back into FlightGear, you have to be careful to use elevation data sets that are compatible with the GNU Public License, such as the original SRTM data issued by NASA.
** [http://dds.cr.usgs.gov/srtm/ http://dds.cr.usgs.gov/srtm/]
* Surface landuse data from the [http://mapserver.flightgear.org/ FlightGear Mapserver]
* Aerial photographs that are keyed to latitude and longitude

== Main window ==

=== Menu ===

==== File ====

:''' New '''
:: Clears the current work area ready for a new project.
:'''Open'''
::'''Project'''
::: Opens an existing project file.
::'''Tile'''
::: Opens an existing tile. This is mainly used to place static objects. Editing a tile is not supported anymore.
:: '''File'''
::: Opens an existing file. It can be an elevation file or a fragment file. Elevation files contain raw elevation data and provide the basis for a project.
:; Recent Files
:: Opens recently opened files. These may be tiles or elevation files.
:; Recent Projects
:: FGSD saves work in *.FGSD files. These files contain references to map fragments as well as any land cover that might have been added. Various other pieces of information regarding the environment used to create that work are also saved.
:; Save Project
:: Saves the current environment. If the project has already been given a name, that names is used to save the work, otherwise you will be prompted to provide a new name
:; Save Project As
:: Saves the current environment under name that is prompted for.
:; Export
:: Exports the project to tile format. The results of the export process may be used in FGFS to view the progress of a project.
:; Quit
:: Exits FGSD

==== Edit ====

: '''Undo'''
:: Undo last action
:; Redo
:: Redo last undone action

==== Scenery ====

: '''Simplify Terrain'''
:; Strip Raw Elevations
:; Embed Curves
:; Embed Airports

==== Tools ====

: '''Object Library'''
:: Displays the Object library window
:; Map Fragments
:: Displays the Map fragment window
:; Import Curves
:; Select Airports
:; Chop HGT Files
:; Options
:: Displays the Options window

=== Toolbars ===

==== Main toolbar ====
[[File:fgsd-wiki-maintb.png]]

==== Curves toolbar ====
[[File:fgsd-wiki-curvetb.png]]

==== Scenery toolbar ====
[[File:fgsd-wiki-scenerytb.png]]

==== Static objects toolbar ====
[[File:fgsd-wiki-statobjtb.png]]

==== Airports toolbar ====
[[File:fgsd-wiki-apttb.png]]

=== Main area ===

=== Status bar ===

== Options window ==

''How to set general options and preferences''

This window has 4 tabs :
* General
* Flightgear
* LandcoverDB
* View

All parameters are saved in an [[XML]] file named ~/.fgsdrc

All path are in Unix convention : directories and names are separated by '/' ( slash ) character. Under Windows, the path may begin with :

=== General ===

:;Output path
:: this path will be used at export time. It can be overriden in the export window.
:;Project history length
:: number of project file names proposed in the File > Recent projects menu
:; File history length
:: number of file names proposed in the File > Recent files menu
:; Display position in decimal
:: choose the format of the longitude and latitude displayed in the status bar

=== FlightGear ===

:;FlightGear data path
::the path to the FG_ROOT directory. This path is used to find the Airports/apt.dat.gz database, the materials.xml material database, and the Textures/ directory.
:;FlightGear scenery path
:: collection of path to scenery folders. These paths contain 'Terrain' and optionally 'Objects' subfolders. They are separated by ';' ( semi colon ) under Window, and by ':' ( colon ) under Unix.

=== LandcoverDB ===

:; Shapefile directory
:: a path to a local directory containing shapefiles representing landcover contours
:; Database hostname
:: a hostname to a Post-GIS server
:; Layers
:: list all .shp files discovered in the Shapefile directory and their assigned FlightGear area type. The 'Use' checkbox shows if the layer is used.

=== View ===

:; Show constrained edges
:: if checked, tile boundaries and material boundaries are drawn in red
:;Show vertices
:: if checked, terrain vertices are drawn with a blue square
:;Show infinite edges
:: ( used mainly for debug ) infinite edges are edges that connect the terrain hull vertices to an infinite vertex. They are shown in white.

== Map fragment window ==

''How to import images and georeference them''

his window is used to georeference images before import in the main window. fgsd uses a 3 points method to correct rotation and non uniform scaling as well as positionning. A fragment have a contour that is initially set to the image extents. Only the image within the contour is displayed in the main window ( to discard ugly legend, for instance ).

[[File:fgsd-wiki-mapwin.jpg|Image of Alcatraz, courtesy of the USGS]]

The referencing information, as well as the contour and the image reference, are stored in an XML file.

=== Menu ===
The File menu has the items below :

:;New
::erase the content of the window to start over.
:; Open
:: '''Fragment'''
::: open an XML file containing the reference to the image, the contour and the referencing information
:: '''Image'''
::: open a JPEG file and set a default contour
:; Fetch terraserver-usa.com
:: load an aerial image from terraserver-usa.com, add a contour and georeference the image. terraserver-usa.com provides images from the USGS. These images are free to use.
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Save as
:: save the map fragment with a new name
:; Close
:: close the window. If the content is properly georeferenced, a popup is displayed to ask if the fragment should be included in the main window.

=== Toolbar ===
Icons, from left to right, are :

:; New
:: erase the content of the window to start over.
:; Open Fragment
:: open an XML file containing the reference to the image, the contour and the referencing information
:; Open Image
:: open a JPEG file and set a default contour
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Marker mode
:: Put the program in marker insertion mode. Every click in the image add a new marker at the mouse position and open a dialog box to position details
:; Contour mode
:: Put the program in Contour mode. The magenta contour is then editable. Contour nodes can be moved with the mouse, added or removed
:; Rotate image 90 degrees counter-clockwise
:; Rotate image 90 degrees clockwise
:: Orient the image to correct disoriented scan
:; Zoom slider
:: Zoom in or zoom out by moving the slider cursor. Zooming in increase the positioning precision.

=== Marker mode ===

When the marker button is activated, every click in the image pops up the dialog box below :

[[File:fgsd-wiki-marker.jpg]]

Its purpose is to enter real world position of the click. This can be done in several ways, depending on the data available on the map/image being georeferenced. First one have to choose a coordinate system between :

* WGS-84
* Lambert I
* Lambert II
* Lambert II extended
* Lambert III
* Lambert IV
* OSGB 36
* Universal Transverse Mercator

The first one allows to enter position directly in degrees for longitude and latitude. The others need eastings and northings in meters.

=== Contour mode ===

This mode is used to move contour nodes, add new nodes or remove existing one.

Moving is done by dragging the node.
To add a new node, first select an edge that should become cyan, and the CTRL-click where new point should be added.
To remove an existing node, right-click on the node and select 'Remove point' in the context menu that pops up.

The contour should stay a non-intersecting loop, so the program controls that moves or modifications in the number of nodes are legal.

=== terraserver-usa.com images download window ===

This dialog box is displayed when the 'Fetch terraserver-usa.com' is choosen from the file menu, or the 'Fetch terraserver-usa.com from here' popup menu option is choosen in the context menu of the main window. In the latter case, the location is the one under the mouse when choosing the option. Otherwise, this is the last location entered. The first location proposed is the one of KSFO, the San Francisco airport.

[[File:fgsd-wiki-terraserver.jpg]]

It allows one to connect to the server to get the aerial image centered at the location entered in the first line. The radius is the minimum distance between the center and an edge of the image, and can be a bit more due to the fact that image elements are 200x200 pixel square. Initially, the vertical 'radius' ( right field ) is set with the same value that is entered in the horizontal one. It is possible to change it to retrieve a non squared image.

There are 3 types of images available and several resolutions. An estimate of the size and the weight of the download is given before starting it.

During download, a progress bar is shown in the window status bar with a button to cancel the acquisition.

When acquisition is completed, markers are positioned at the image corners, and a contour is set around the image. It is then possible to save both image and fragment to files, and import them in the main project.

== Object library window ==

'''How to organize 3D object models'''

The Object library window is used to organize, display and select 3D object models.

[[File:fgsd-wiki-objlib.jpg]]

The window has a tree of models and folders at its left. The right part displays in 3D the model selected in the tree. The top hosts a toolbar to manage the tree.

In the toolbar, the entry field at the left is used whenever a name is required by the subsequent button action. It must be pre-filled before one click on the button.

The '''Af''' button adds a new folder as a child of the current folder (initially, only Root exists ). The name is found in the entry field at the time of the click.

The '''Rf''' button renames the current folder. Again, the new name is the content of the field at the time of the click.

The '''Cut''' button removes the folder subtree or the model. It is left in a paste buffer and is not immediately destroyed.

The ''Pst''' button pastes the content of the paste buffer as a child of the current folder.

The '''Am'' button adds a new model in the current folder. A file selection window is displayed and the user must select a model file supported by PLIB.

The '''Rm''' button is used to rename the model. The path remain unchanged

The '''At''' button is used to reference an additional file, for instance, a texture image file.

The '''Sm''' button stops or resumes model spinning in the 3D view.

The '''Select''' button is used when adding a static object in the scenery. It is grayed when the window is displayed from the menu.

The '''Quit''' is used to close the window. When a selection is prompted, this button cancel the selection.

It is possible to drag the mouse to change the camera position in the 3D view. Dragging with left mouse button rotates the model around its axis. Dragging the middle button rotates the camera around the model. Dragging vertically the right button change the distance between the camera and the model ( zoom ).

The object library is stored in an XML file named ~/.fgsdobjlib

== Airport selection dialog ==

'''How to load airports and specify additional parameters'''

The airport selection dialog lists all the airport found in the database that can fit in the terrain loaded in the current project. If some of these are already loaded in the project, current parameters for them are displayed and reused. The dialog looks like :

[[File:fgsd-wiki-aptwin.jpg]]

The first column is the ICAO code.

The second is the name found in the apt.dat.gz file.

The third column ( titled 'Zero' ) tells if the labeling of runways with number less than ten takes a zero at the first place ( 09 vs 9 ).

The fourth column is the distance ( in meters ) between taxiways and runways and the airport boundary.

The fifth column is the path to an alternate description of the airport. The requested file must be in X-Plane format ( .dat file ). This is the kind of files can be created by TaxiDraw. The buttons pops a file selection dialog up.

== Export dialog ==

'''How to export the current project to files suitable for FlightGear'''

[[File:fgsd-wiki-export.jpg]]

[[Category:Scenery software]]

[[fr:créer des scènes dans FlightGear]]

FlightGear Scenery Designer

2019-01-29T21:43:06Z

J8d4c3: Ditto for World Custom Scenery Project

[[File:fgsd-wiki-title.jpg]]

FlightGear Scenery Designer ( aka fgsd ) is a tool to design and create custom-made scenery tiles suitable to FlightGear. It performs a similar function to [[TerraGear]], but in a different way. TerraGear is intended for batch processing of large numbers of files, and thus is used to produce the global scenery distributed with [[FlightGear]] and via [[TerraSync]]; fgsd is intended more for small-scale fine-tuning of a few tiles through a graphical interface. 
 
<big>'''Project Status'''</big> 
As of March 2011, it does not appear that fgsd is being actively developed.
Links on this page and on pages associated with this project may be bad. 
Same for this project: For another approach to the whole challenge of enhancing world scenery, see the [[World Custom Scenery Project]].

== Documentation ==

Documentation for fgsd is thin and hard to find. Besides this wiki page, you may want find the following helpful:

* [[Howto: Make an airport]]
* The [http://fgsd.sourceforge.net/doc.html documentation page] of the [http://fgsd.sourceforge.net/ fgsd Sourceforge] website. This includes a four-part video tutorial/demonstration (no sound) illustrating many steps in using fgsd, and instructions on placing static objects.
* The FlightGear Forum, in the scenery section. This seems to be the most current information, but information can be hard to find.

If you find more helpful bits of information, please add it here to make it easier to find.

== History and Philosophy ==

''How fgsd works and what are the ideas that drive its design''

The initial purpose of fgsd was to edit existing scenery because of the lack, at that time, of a decent free elevation model outside the USA. Releases up to 0.3.1 had capabilities to hand-edit part of the terrain. But it appeared to be cumbersome to edit triangles one at a time, and very frustrating as the work done on one tile was obsoleted every time a new global scenery was released. Moreover, editing the result of the [[TerraGear]] process proved to be non-trivial because of hidden gotchas on the topological quality of the tiles.
Finally, NASA and others released the SRTM digital elevation model that offers a more refined elevation dataset for most of the world, lessening the need to edit elevations manually.

From release 0.4.0 ( to be released ) ( and its pre-releases 0.3.9x - Win32 binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] - Other systems, use CVS ), fgsd no longer offers the ability to edit already made scenery tiles. Instead, it works interactively, using the same workflow as [[TerraGear]]. This workflow can be summarized as follow :

* load raw elevations
* simplify elevation model
* prepare land cover contour
* project land cover contour on terrain
* prepare airport layout
* project airport layout on terrain
* export terrain to fgfs scenery tiles

additionally, 3D object models can be placed here and there to add verticality to this somewhat horizontal world.

One side benefit of this approach is that modified land cover contours can be exported to a format that TerraGear can use. A centralized database of contours is setup for that ( see http://www.custom-scenery.org ). This way collaborative changes to the global scenery can be consolidated and the next round of global scenery generation will include submitted individual changes.
Of course, import from the landcover database is possible in fgsd.

Airports are loaded from the airport database file located in the FlightGear base package. It is not possible to edit an airport, but a new definition of an individual airport can be loaded from a file in X-Plane format. This kind of file are typically produced by the Taxidraw airport editor.

== What you need to run fgsd ==

PLEASE ADD TO THIS LIST OTHER PLACES WHERE THESE THINGS CAN BE FOUND.

* fgsd itself.
** Source code from [http://sourceforge.net/projects/fgsd/files/ SourceForge]
** Windows binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here]
* Elevation data from the SRTM ([http://www2.jpl.nasa.gov/srtm/ Shuttle Radio Topography Mission]), in .hgt file format, at either SRTM-3 or SRTM-1 resolution. Please note that if you want your work to eventually be incorporated back into FlightGear, you have to be careful to use elevation data sets that are compatible with the GNU Public License, such as the original SRTM data issued by NASA.
** [http://dds.cr.usgs.gov/srtm/ http://dds.cr.usgs.gov/srtm/]
* Surface landuse data from the [http://mapserver.flightgear.org/ FlightGear Mapserver]
* Aerial photographs that are keyed to latitude and longitude

== Main window ==

=== Menu ===

==== File ====

:''' New '''
:: Clears the current work area ready for a new project.
:'''Open'''
::'''Project'''
::: Opens an existing project file.
::'''Tile'''
::: Opens an existing tile. This is mainly used to place static objects. Editing a tile is not supported anymore.
:: '''File'''
::: Opens an existing file. It can be an elevation file or a fragment file. Elevation files contain raw elevation data and provide the basis for a project.
:; Recent Files
:: Opens recently opened files. These may be tiles or elevation files.
:; Recent Projects
:: FGSD saves work in *.FGSD files. These files contain references to map fragments as well as any land cover that might have been added. Various other pieces of information regarding the environment used to create that work are also saved.
:; Save Project
:: Saves the current environment. If the project has already been given a name, that names is used to save the work, otherwise you will be prompted to provide a new name
:; Save Project As
:: Saves the current environment under name that is prompted for.
:; Export
:: Exports the project to tile format. The results of the export process may be used in FGFS to view the progress of a project.
:; Quit
:: Exits FGSD

==== Edit ====

: '''Undo'''
:: Undo last action
:; Redo
:: Redo last undone action

==== Scenery ====

: '''Simplify Terrain'''
:; Strip Raw Elevations
:; Embed Curves
:; Embed Airports

==== Tools ====

: '''Object Library'''
:: Displays the Object library window
:; Map Fragments
:: Displays the Map fragment window
:; Import Curves
:; Select Airports
:; Chop HGT Files
:; Options
:: Displays the Options window

=== Toolbars ===

==== Main toolbar ====
[[File:fgsd-wiki-maintb.png]]

==== Curves toolbar ====
[[File:fgsd-wiki-curvetb.png]]

==== Scenery toolbar ====
[[File:fgsd-wiki-scenerytb.png]]

==== Static objects toolbar ====
[[File:fgsd-wiki-statobjtb.png]]

==== Airports toolbar ====
[[File:fgsd-wiki-apttb.png]]

=== Main area ===

=== Status bar ===

== Options window ==

''How to set general options and preferences''

This window has 4 tabs :
* General
* Flightgear
* LandcoverDB
* View

All parameters are saved in an [[XML]] file named ~/.fgsdrc

All path are in Unix convention : directories and names are separated by '/' ( slash ) character. Under Windows, the path may begin with :

=== General ===

:;Output path
:: this path will be used at export time. It can be overriden in the export window.
:;Project history length
:: number of project file names proposed in the File > Recent projects menu
:; File history length
:: number of file names proposed in the File > Recent files menu
:; Display position in decimal
:: choose the format of the longitude and latitude displayed in the status bar

=== FlightGear ===

:;FlightGear data path
::the path to the FG_ROOT directory. This path is used to find the Airports/apt.dat.gz database, the materials.xml material database, and the Textures/ directory.
:;FlightGear scenery path
:: collection of path to scenery folders. These paths contain 'Terrain' and optionally 'Objects' subfolders. They are separated by ';' ( semi colon ) under Window, and by ':' ( colon ) under Unix.

=== LandcoverDB ===

:; Shapefile directory
:: a path to a local directory containing shapefiles representing landcover contours
:; Database hostname
:: a hostname to a Post-GIS server
:; Layers
:: list all .shp files discovered in the Shapefile directory and their assigned FlightGear area type. The 'Use' checkbox shows if the layer is used.

=== View ===

:; Show constrained edges
:: if checked, tile boundaries and material boundaries are drawn in red
:;Show vertices
:: if checked, terrain vertices are drawn with a blue square
:;Show infinite edges
:: ( used mainly for debug ) infinite edges are edges that connect the terrain hull vertices to an infinite vertex. They are shown in white.

== Map fragment window ==

''How to import images and georeference them''

his window is used to georeference images before import in the main window. fgsd uses a 3 points method to correct rotation and non uniform scaling as well as positionning. A fragment have a contour that is initially set to the image extents. Only the image within the contour is displayed in the main window ( to discard ugly legend, for instance ).

[[File:fgsd-wiki-mapwin.jpg|Image of Alcatraz, courtesy of the USGS]]

The referencing information, as well as the contour and the image reference, are stored in an XML file.

=== Menu ===
The File menu has the items below :

:;New
::erase the content of the window to start over.
:; Open
:: '''Fragment'''
::: open an XML file containing the reference to the image, the contour and the referencing information
:: '''Image'''
::: open a JPEG file and set a default contour
:; Fetch terraserver-usa.com
:: load an aerial image from terraserver-usa.com, add a contour and georeference the image. terraserver-usa.com provides images from the USGS. These images are free to use.
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Save as
:: save the map fragment with a new name
:; Close
:: close the window. If the content is properly georeferenced, a popup is displayed to ask if the fragment should be included in the main window.

=== Toolbar ===
Icons, from left to right, are :

:; New
:: erase the content of the window to start over.
:; Open Fragment
:: open an XML file containing the reference to the image, the contour and the referencing information
:; Open Image
:: open a JPEG file and set a default contour
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Marker mode
:: Put the program in marker insertion mode. Every click in the image add a new marker at the mouse position and open a dialog box to position details
:; Contour mode
:: Put the program in Contour mode. The magenta contour is then editable. Contour nodes can be moved with the mouse, added or removed
:; Rotate image 90 degrees counter-clockwise
:; Rotate image 90 degrees clockwise
:: Orient the image to correct disoriented scan
:; Zoom slider
:: Zoom in or zoom out by moving the slider cursor. Zooming in increase the positioning precision.

=== Marker mode ===

When the marker button is activated, every click in the image pops up the dialog box below :

[[File:fgsd-wiki-marker.jpg]]

Its purpose is to enter real world position of the click. This can be done in several ways, depending on the data available on the map/image being georeferenced. First one have to choose a coordinate system between :

* WGS-84
* Lambert I
* Lambert II
* Lambert II extended
* Lambert III
* Lambert IV
* OSGB 36
* Universal Transverse Mercator

The first one allows to enter position directly in degrees for longitude and latitude. The others need eastings and northings in meters.

=== Contour mode ===

This mode is used to move contour nodes, add new nodes or remove existing one.

Moving is done by dragging the node.
To add a new node, first select an edge that should become cyan, and the CTRL-click where new point should be added.
To remove an existing node, right-click on the node and select 'Remove point' in the context menu that pops up.

The contour should stay a non-intersecting loop, so the program controls that moves or modifications in the number of nodes are legal.

=== terraserver-usa.com images download window ===

This dialog box is displayed when the 'Fetch terraserver-usa.com' is choosen from the file menu, or the 'Fetch terraserver-usa.com from here' popup menu option is choosen in the context menu of the main window. In the latter case, the location is the one under the mouse when choosing the option. Otherwise, this is the last location entered. The first location proposed is the one of KSFO, the San Francisco airport.

[[File:fgsd-wiki-terraserver.jpg]]

It allows one to connect to the server to get the aerial image centered at the location entered in the first line. The radius is the minimum distance between the center and an edge of the image, and can be a bit more due to the fact that image elements are 200x200 pixel square. Initially, the vertical 'radius' ( right field ) is set with the same value that is entered in the horizontal one. It is possible to change it to retrieve a non squared image.

There are 3 types of images available and several resolutions. An estimate of the size and the weight of the download is given before starting it.

During download, a progress bar is shown in the window status bar with a button to cancel the acquisition.

When acquisition is completed, markers are positioned at the image corners, and a contour is set around the image. It is then possible to save both image and fragment to files, and import them in the main project.

== Object library window ==

'''How to organize 3D object models'''

The Object library window is used to organize, display and select 3D object models.

[[File:fgsd-wiki-objlib.jpg]]

The window has a tree of models and folders at its left. The right part displays in 3D the model selected in the tree. The top hosts a toolbar to manage the tree.

In the toolbar, the entry field at the left is used whenever a name is required by the subsequent button action. It must be pre-filled before one click on the button.

The '''Af''' button adds a new folder as a child of the current folder (initially, only Root exists ). The name is found in the entry field at the time of the click.

The '''Rf''' button renames the current folder. Again, the new name is the content of the field at the time of the click.

The '''Cut''' button removes the folder subtree or the model. It is left in a paste buffer and is not immediately destroyed.

The ''Pst''' button pastes the content of the paste buffer as a child of the current folder.

The '''Am'' button adds a new model in the current folder. A file selection window is displayed and the user must select a model file supported by PLIB.

The '''Rm''' button is used to rename the model. The path remain unchanged

The '''At''' button is used to reference an additional file, for instance, a texture image file.

The '''Sm''' button stops or resumes model spinning in the 3D view.

The '''Select''' button is used when adding a static object in the scenery. It is grayed when the window is displayed from the menu.

The '''Quit''' is used to close the window. When a selection is prompted, this button cancel the selection.

It is possible to drag the mouse to change the camera position in the 3D view. Dragging with left mouse button rotates the model around its axis. Dragging the middle button rotates the camera around the model. Dragging vertically the right button change the distance between the camera and the model ( zoom ).

The object library is stored in an XML file named ~/.fgsdobjlib

== Airport selection dialog ==

'''How to load airports and specify additional parameters'''

The airport selection dialog lists all the airport found in the database that can fit in the terrain loaded in the current project. If some of these are already loaded in the project, current parameters for them are displayed and reused. The dialog looks like :

[[File:fgsd-wiki-aptwin.jpg]]

The first column is the ICAO code.

The second is the name found in the apt.dat.gz file.

The third column ( titled 'Zero' ) tells if the labeling of runways with number less than ten takes a zero at the first place ( 09 vs 9 ).

The fourth column is the distance ( in meters ) between taxiways and runways and the airport boundary.

The fifth column is the path to an alternate description of the airport. The requested file must be in X-Plane format ( .dat file ). This is the kind of files can be created by TaxiDraw. The buttons pops a file selection dialog up.

== Export dialog ==

'''How to export the current project to files suitable for FlightGear'''

[[File:fgsd-wiki-export.jpg]]

[[Category:Scenery software]]

[[fr:créer des scènes dans FlightGear]]

FlightGear Scenery Designer

2019-01-29T21:41:15Z

J8d4c3: Added text showing that this project may not be actively developed and no longer useful for its intended purpose.

[[File:fgsd-wiki-title.jpg]]

FlightGear Scenery Designer ( aka fgsd ) is a tool to design and create custom-made scenery tiles suitable to FlightGear. It performs a similar function to [[TerraGear]], but in a different way. TerraGear is intended for batch processing of large numbers of files, and thus is used to produce the global scenery distributed with [[FlightGear]] and via [[TerraSync]]; fgsd is intended more for small-scale fine-tuning of a few tiles through a graphical interface. 
 
<big>'''Project Status'''</big> 
As of March 2011, it does not appear that fgsd is being actively developed.
Links on this page and on pages associated with this project may be bad. 
For another approach to the whole challenge of enhancing world scenery, see the [[World Custom Scenery Project]].

== Documentation ==

Documentation for fgsd is thin and hard to find. Besides this wiki page, you may want find the following helpful:

* [[Howto: Make an airport]]
* The [http://fgsd.sourceforge.net/doc.html documentation page] of the [http://fgsd.sourceforge.net/ fgsd Sourceforge] website. This includes a four-part video tutorial/demonstration (no sound) illustrating many steps in using fgsd, and instructions on placing static objects.
* The FlightGear Forum, in the scenery section. This seems to be the most current information, but information can be hard to find.

If you find more helpful bits of information, please add it here to make it easier to find.

== History and Philosophy ==

''How fgsd works and what are the ideas that drive its design''

The initial purpose of fgsd was to edit existing scenery because of the lack, at that time, of a decent free elevation model outside the USA. Releases up to 0.3.1 had capabilities to hand-edit part of the terrain. But it appeared to be cumbersome to edit triangles one at a time, and very frustrating as the work done on one tile was obsoleted every time a new global scenery was released. Moreover, editing the result of the [[TerraGear]] process proved to be non-trivial because of hidden gotchas on the topological quality of the tiles.
Finally, NASA and others released the SRTM digital elevation model that offers a more refined elevation dataset for most of the world, lessening the need to edit elevations manually.

From release 0.4.0 ( to be released ) ( and its pre-releases 0.3.9x - Win32 binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here] - Other systems, use CVS ), fgsd no longer offers the ability to edit already made scenery tiles. Instead, it works interactively, using the same workflow as [[TerraGear]]. This workflow can be summarized as follow :

* load raw elevations
* simplify elevation model
* prepare land cover contour
* project land cover contour on terrain
* prepare airport layout
* project airport layout on terrain
* export terrain to fgfs scenery tiles

additionally, 3D object models can be placed here and there to add verticality to this somewhat horizontal world.

One side benefit of this approach is that modified land cover contours can be exported to a format that TerraGear can use. A centralized database of contours is setup for that ( see http://www.custom-scenery.org ). This way collaborative changes to the global scenery can be consolidated and the next round of global scenery generation will include submitted individual changes.
Of course, import from the landcover database is possible in fgsd.

Airports are loaded from the airport database file located in the FlightGear base package. It is not possible to edit an airport, but a new definition of an individual airport can be loaded from a file in X-Plane format. This kind of file are typically produced by the Taxidraw airport editor.

== What you need to run fgsd ==

PLEASE ADD TO THIS LIST OTHER PLACES WHERE THESE THINGS CAN BE FOUND.

* fgsd itself.
** Source code from [http://sourceforge.net/projects/fgsd/files/ SourceForge]
** Windows binaries available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 here]
* Elevation data from the SRTM ([http://www2.jpl.nasa.gov/srtm/ Shuttle Radio Topography Mission]), in .hgt file format, at either SRTM-3 or SRTM-1 resolution. Please note that if you want your work to eventually be incorporated back into FlightGear, you have to be careful to use elevation data sets that are compatible with the GNU Public License, such as the original SRTM data issued by NASA.
** [http://dds.cr.usgs.gov/srtm/ http://dds.cr.usgs.gov/srtm/]
* Surface landuse data from the [http://mapserver.flightgear.org/ FlightGear Mapserver]
* Aerial photographs that are keyed to latitude and longitude

== Main window ==

=== Menu ===

==== File ====

:''' New '''
:: Clears the current work area ready for a new project.
:'''Open'''
::'''Project'''
::: Opens an existing project file.
::'''Tile'''
::: Opens an existing tile. This is mainly used to place static objects. Editing a tile is not supported anymore.
:: '''File'''
::: Opens an existing file. It can be an elevation file or a fragment file. Elevation files contain raw elevation data and provide the basis for a project.
:; Recent Files
:: Opens recently opened files. These may be tiles or elevation files.
:; Recent Projects
:: FGSD saves work in *.FGSD files. These files contain references to map fragments as well as any land cover that might have been added. Various other pieces of information regarding the environment used to create that work are also saved.
:; Save Project
:: Saves the current environment. If the project has already been given a name, that names is used to save the work, otherwise you will be prompted to provide a new name
:; Save Project As
:: Saves the current environment under name that is prompted for.
:; Export
:: Exports the project to tile format. The results of the export process may be used in FGFS to view the progress of a project.
:; Quit
:: Exits FGSD

==== Edit ====

: '''Undo'''
:: Undo last action
:; Redo
:: Redo last undone action

==== Scenery ====

: '''Simplify Terrain'''
:; Strip Raw Elevations
:; Embed Curves
:; Embed Airports

==== Tools ====

: '''Object Library'''
:: Displays the Object library window
:; Map Fragments
:: Displays the Map fragment window
:; Import Curves
:; Select Airports
:; Chop HGT Files
:; Options
:: Displays the Options window

=== Toolbars ===

==== Main toolbar ====
[[File:fgsd-wiki-maintb.png]]

==== Curves toolbar ====
[[File:fgsd-wiki-curvetb.png]]

==== Scenery toolbar ====
[[File:fgsd-wiki-scenerytb.png]]

==== Static objects toolbar ====
[[File:fgsd-wiki-statobjtb.png]]

==== Airports toolbar ====
[[File:fgsd-wiki-apttb.png]]

=== Main area ===

=== Status bar ===

== Options window ==

''How to set general options and preferences''

This window has 4 tabs :
* General
* Flightgear
* LandcoverDB
* View

All parameters are saved in an [[XML]] file named ~/.fgsdrc

All path are in Unix convention : directories and names are separated by '/' ( slash ) character. Under Windows, the path may begin with :

=== General ===

:;Output path
:: this path will be used at export time. It can be overriden in the export window.
:;Project history length
:: number of project file names proposed in the File > Recent projects menu
:; File history length
:: number of file names proposed in the File > Recent files menu
:; Display position in decimal
:: choose the format of the longitude and latitude displayed in the status bar

=== FlightGear ===

:;FlightGear data path
::the path to the FG_ROOT directory. This path is used to find the Airports/apt.dat.gz database, the materials.xml material database, and the Textures/ directory.
:;FlightGear scenery path
:: collection of path to scenery folders. These paths contain 'Terrain' and optionally 'Objects' subfolders. They are separated by ';' ( semi colon ) under Window, and by ':' ( colon ) under Unix.

=== LandcoverDB ===

:; Shapefile directory
:: a path to a local directory containing shapefiles representing landcover contours
:; Database hostname
:: a hostname to a Post-GIS server
:; Layers
:: list all .shp files discovered in the Shapefile directory and their assigned FlightGear area type. The 'Use' checkbox shows if the layer is used.

=== View ===

:; Show constrained edges
:: if checked, tile boundaries and material boundaries are drawn in red
:;Show vertices
:: if checked, terrain vertices are drawn with a blue square
:;Show infinite edges
:: ( used mainly for debug ) infinite edges are edges that connect the terrain hull vertices to an infinite vertex. They are shown in white.

== Map fragment window ==

''How to import images and georeference them''

his window is used to georeference images before import in the main window. fgsd uses a 3 points method to correct rotation and non uniform scaling as well as positionning. A fragment have a contour that is initially set to the image extents. Only the image within the contour is displayed in the main window ( to discard ugly legend, for instance ).

[[File:fgsd-wiki-mapwin.jpg|Image of Alcatraz, courtesy of the USGS]]

The referencing information, as well as the contour and the image reference, are stored in an XML file.

=== Menu ===
The File menu has the items below :

:;New
::erase the content of the window to start over.
:; Open
:: '''Fragment'''
::: open an XML file containing the reference to the image, the contour and the referencing information
:: '''Image'''
::: open a JPEG file and set a default contour
:; Fetch terraserver-usa.com
:: load an aerial image from terraserver-usa.com, add a contour and georeference the image. terraserver-usa.com provides images from the USGS. These images are free to use.
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Save as
:: save the map fragment with a new name
:; Close
:: close the window. If the content is properly georeferenced, a popup is displayed to ask if the fragment should be included in the main window.

=== Toolbar ===
Icons, from left to right, are :

:; New
:: erase the content of the window to start over.
:; Open Fragment
:: open an XML file containing the reference to the image, the contour and the referencing information
:; Open Image
:: open a JPEG file and set a default contour
:; Save
:: save the map fragment with the name it already has. If it is a new fragment, a name is asked first.
:; Marker mode
:: Put the program in marker insertion mode. Every click in the image add a new marker at the mouse position and open a dialog box to position details
:; Contour mode
:: Put the program in Contour mode. The magenta contour is then editable. Contour nodes can be moved with the mouse, added or removed
:; Rotate image 90 degrees counter-clockwise
:; Rotate image 90 degrees clockwise
:: Orient the image to correct disoriented scan
:; Zoom slider
:: Zoom in or zoom out by moving the slider cursor. Zooming in increase the positioning precision.

=== Marker mode ===

When the marker button is activated, every click in the image pops up the dialog box below :

[[File:fgsd-wiki-marker.jpg]]

Its purpose is to enter real world position of the click. This can be done in several ways, depending on the data available on the map/image being georeferenced. First one have to choose a coordinate system between :

* WGS-84
* Lambert I
* Lambert II
* Lambert II extended
* Lambert III
* Lambert IV
* OSGB 36
* Universal Transverse Mercator

The first one allows to enter position directly in degrees for longitude and latitude. The others need eastings and northings in meters.

=== Contour mode ===

This mode is used to move contour nodes, add new nodes or remove existing one.

Moving is done by dragging the node.
To add a new node, first select an edge that should become cyan, and the CTRL-click where new point should be added.
To remove an existing node, right-click on the node and select 'Remove point' in the context menu that pops up.

The contour should stay a non-intersecting loop, so the program controls that moves or modifications in the number of nodes are legal.

=== terraserver-usa.com images download window ===

This dialog box is displayed when the 'Fetch terraserver-usa.com' is choosen from the file menu, or the 'Fetch terraserver-usa.com from here' popup menu option is choosen in the context menu of the main window. In the latter case, the location is the one under the mouse when choosing the option. Otherwise, this is the last location entered. The first location proposed is the one of KSFO, the San Francisco airport.

[[File:fgsd-wiki-terraserver.jpg]]

It allows one to connect to the server to get the aerial image centered at the location entered in the first line. The radius is the minimum distance between the center and an edge of the image, and can be a bit more due to the fact that image elements are 200x200 pixel square. Initially, the vertical 'radius' ( right field ) is set with the same value that is entered in the horizontal one. It is possible to change it to retrieve a non squared image.

There are 3 types of images available and several resolutions. An estimate of the size and the weight of the download is given before starting it.

During download, a progress bar is shown in the window status bar with a button to cancel the acquisition.

When acquisition is completed, markers are positioned at the image corners, and a contour is set around the image. It is then possible to save both image and fragment to files, and import them in the main project.

== Object library window ==

'''How to organize 3D object models'''

The Object library window is used to organize, display and select 3D object models.

[[File:fgsd-wiki-objlib.jpg]]

The window has a tree of models and folders at its left. The right part displays in 3D the model selected in the tree. The top hosts a toolbar to manage the tree.

In the toolbar, the entry field at the left is used whenever a name is required by the subsequent button action. It must be pre-filled before one click on the button.

The '''Af''' button adds a new folder as a child of the current folder (initially, only Root exists ). The name is found in the entry field at the time of the click.

The '''Rf''' button renames the current folder. Again, the new name is the content of the field at the time of the click.

The '''Cut''' button removes the folder subtree or the model. It is left in a paste buffer and is not immediately destroyed.

The ''Pst''' button pastes the content of the paste buffer as a child of the current folder.

The '''Am'' button adds a new model in the current folder. A file selection window is displayed and the user must select a model file supported by PLIB.

The '''Rm''' button is used to rename the model. The path remain unchanged

The '''At''' button is used to reference an additional file, for instance, a texture image file.

The '''Sm''' button stops or resumes model spinning in the 3D view.

The '''Select''' button is used when adding a static object in the scenery. It is grayed when the window is displayed from the menu.

The '''Quit''' is used to close the window. When a selection is prompted, this button cancel the selection.

It is possible to drag the mouse to change the camera position in the 3D view. Dragging with left mouse button rotates the model around its axis. Dragging the middle button rotates the camera around the model. Dragging vertically the right button change the distance between the camera and the model ( zoom ).

The object library is stored in an XML file named ~/.fgsdobjlib

== Airport selection dialog ==

'''How to load airports and specify additional parameters'''

The airport selection dialog lists all the airport found in the database that can fit in the terrain loaded in the current project. If some of these are already loaded in the project, current parameters for them are displayed and reused. The dialog looks like :

[[File:fgsd-wiki-aptwin.jpg]]

The first column is the ICAO code.

The second is the name found in the apt.dat.gz file.

The third column ( titled 'Zero' ) tells if the labeling of runways with number less than ten takes a zero at the first place ( 09 vs 9 ).

The fourth column is the distance ( in meters ) between taxiways and runways and the airport boundary.

The fifth column is the path to an alternate description of the airport. The requested file must be in X-Plane format ( .dat file ). This is the kind of files can be created by TaxiDraw. The buttons pops a file selection dialog up.

== Export dialog ==

'''How to export the current project to files suitable for FlightGear'''

[[File:fgsd-wiki-export.jpg]]

[[Category:Scenery software]]

[[fr:créer des scènes dans FlightGear]]

User:J8d4c3

2019-01-28T22:34:01Z

J8d4c3:

These are notes for myself for when or if I reacquire an interest in FlightGear reminding me what problems I was having with this program. 
 
I am abandoning this project. KMYR doesn't have any STAR or SID procedures. FG's navigation dialogs makes a good flightplan so I really see no use for creating procedures. 
A method of creating STARs and SIDs seems to require one of: a standalone app or a tab on FG's start page. Both of which I have neither the interest to invest a lot of time creating or the C/C++/Nasal programming skills required to do it. 
Not finding any free SID/STAR files for airports, I have decided to learn how to create my own. 
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ? 
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws. 
[[User:J8d4c3/Level-D_767_XML_File_Format]]
 

Steps to create and add permanent objects to FlightGear's scenery: 
Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it. 
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear? 
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah! 
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet. 
 

Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

User:J8d4c3

2019-01-28T22:28:47Z

J8d4c3:

These are notes for myself for when or if I reacquire an interest in FlightGear reminding me what problems I was having with this program. 
 
I am abandoning this project. At least until or if someone shows me that I am doing something wrong in using WED. 
Not finding any free SID/STAR files for airports, I have decided to learn how to create my own. 
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ? 
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws. 
[[User:J8d4c3/Level-D_767_XML_File_Format]]
 

Steps to create and add permanent objects to FlightGear's scenery: 
Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it. 
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear? 
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah! 
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet. 
 

Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

User:J8d4c3

2019-01-28T22:27:28Z

J8d4c3:

These are notes for myself for when or if I reacquire an interest in FlightGear reminding me what problems I was having with this program. 
 
I am abandoning this project. At least until or if someone shows me that I am doing something wrong in using WED. 
Not finding any free SID/STAR files for airports, I have decided to learn how to create my own. 
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ? 
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws. 
 
[[User:J8d4c3/Level-D_767_XML_File_Format]]
 

Steps to create and add permanent objects to FlightGear's scenery: 
Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it. 
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear? 
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah! 
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet. 
 

Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

User:J8d4c3

2019-01-28T22:23:46Z

J8d4c3:

Not finding any free SID/STAR files for airports, I have decided to learn how to create my own.
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ?
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws.

[[User:J8d4c3/Level-D_767_XML_File_Format]]

Steps to create and add permanent objects to FlightGear's scenery: 

Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it. 
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear? 
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah! 
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet. 
 
Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

User:J8d4c3

2019-01-28T22:23:12Z

J8d4c3:

Not finding any free SID/STAR files for airports, I have decided to learn how to create my own.
The information shown here is gleaned from examining files found on the Internet, files found in airport files of FlightGear, ?
Since I am not copying exact files nor have I agreed to anything prohibiting me from documenting this, I am not in any violation of copyright laws.

[[User:J8d4c3/Level-D_767_XML_File_Format]]

Steps to create and add permanent objects to FlightGear's scenery: 

Use TerraMaster to download the latest scenery for the selected area. Or start FlightGear and set aircraft's starting location to that area and allow TerraSync to do it.
WED sucks. When validating an airport, it gripes about not being able to find files for objects that seem to be sourced from X-Plane's files and are not in FlightGear's /data directory. Even if I had those files, what good would they do me for using with FlightGear?
Use QGIS for landscape scenery. Have fun figuring out how to use it with geophotos: different file types, different databases, etc. Ah!
Lots of links on lots of FlightGear wiki pages don't work. Obsolete and/or moved websites/webpages. IDK enough about a lot of this to make intelligent changes to the wiki pages yet.

Since FG has a problem with my joystick and I can't play without it, I'm gonna take another extended break from FlightGear. I've made some changes that I hope helps FG. Time to go do other things.

Talk:WorldEditor

2019-01-28T22:20:51Z

J8d4c3:

Starting WED for the first time notes:
Reference:
xptools/src/WEDCore/WED_PackageMgr.cpp lines 33-35
CUSTOM_PACKAGE_PATH="Custom Scenery"
GLOBAL_PACKAGE_PATH="Global Scenery"
DEFAULT_PACKAGE_PATH="Resources" DIR_STR="default scenery"
This section was written by a person who is a newbie to WED. An experienced WED user is requested to verify and edit this as required.[[User:J8d4c3|J8d4c3]] 17:02, 7 July 2013 (UTC)

How should the directory structure be for if X-Plane '''is''' installed ? [[User:J8d4c3|J8d4c3]] 17:23, 7 July 2013 (UTC)

The links to xsimreviews in the external links section is out of date. I am new to WED, so I don't have a good idea what to replace them with.
[[User:Ve2hkw|Ve2hkw]] ([[User talk:Ve2hkw|talk]]) 21:22, 7 May 2017 (EDT)

I don't know about a few years ago but the use of WED seems to be a now unusable hack to use it to design an airport. External links on this page are bad, and my main gripe: WED seems to require the use of library files whose formats (I think) are found in X-Plane's files, which I won't install. Is there a method to get WED to use FlightGear's files for adding objects? FlightGear's ufo seems to be a better solution. I've spent the past several days trying to figure out how to add detail around KMYR and make the changes global to everyone. I'm not having much luck :/ [[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 15:48, 28 January 2019 (EST)

Talk:FlightGear Scenery Database

2019-01-28T21:25:37Z

J8d4c3: Suggestion

I wish this map had a link on the scenery website. This page seems to be the only source of informing people of its existence. There is no contact link on scenery.flightgear.org so I can suggest this.[[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 16:25, 28 January 2019 (EST)

FlightGear Scenery Database

2019-01-28T21:21:40Z

J8d4c3: Deleted discussion of an obsolete functionality. Added a bit more information about what is seen on the screen and how to use the map.

The '''FlightGear Scenery Database''' collects all 3D objects that are placed in the [[FlightGear]] [[World Scenery]] releases.

== Contribute ==
* ''Contribution guidelines'' are available here: https://scenery.flightgear.org/contribute.php
* ''Semi''-automatic insert/delete/update webtools for shared and static objects/models can be found on the [https://scenery.flightgear.org/submission scenery submission page].

=== Interactive World Map to update & delete objects ===
https://scenery.flightgear.org/map/?z=3&lat=0.0&lon=0.0

Type an airport name in the dialog box or zoom in to your place of interest. If you zoom in enough, you will see any objects that have been placed in the area. Those objects will be shown as red or blue circles with arrows attached. To see information about an object, move the cursor over the object until the cursor changes to a pointed finger icon and click. A popup will appear containing information about the object.
Unique items are shown as blue circles. Shared items are shown as red circles.

== Related content ==
* [[FlightGear related projects]]

== External links ==
* [https://scenery.flightgear.org FlightGear Scenery Database]
* [{{sceneryweb url}} Website repository] (Sourceforge)

[[Category:Scenery]]
[[Category:Scenery enhancement]]

Talk:WorldEditor

2019-01-28T20:49:45Z

J8d4c3: Comment

Starting WED for the first time notes:
Reference:
xptools/src/WEDCore/WED_PackageMgr.cpp lines 33-35
CUSTOM_PACKAGE_PATH="Custom Scenery"
GLOBAL_PACKAGE_PATH="Global Scenery"
DEFAULT_PACKAGE_PATH="Resources" DIR_STR="default scenery"
This section was written by a person who is a newbie to WED. An experienced WED user is requested to verify and edit this as required.[[User:J8d4c3|J8d4c3]] 17:02, 7 July 2013 (UTC)

How should the directory structure be for if X-Plane '''is''' installed ? [[User:J8d4c3|J8d4c3]] 17:23, 7 July 2013 (UTC)

The links to xsimreviews in the external links section is out of date. I am new to WED, so I don't have a good idea what to replace them with.
[[User:Ve2hkw|Ve2hkw]] ([[User talk:Ve2hkw|talk]]) 21:22, 7 May 2017 (EDT)

I don't know about a few years ago but the use of WED seems to be a now unusable hack to use it to design an airport. External links on this page is bad, and my main gripe: WED seems to require the use of library files whose formats (I think) are found in X-Plane's files, which I won't install. Is there a method to get WED to use FlightGear's files for adding objects? FlightGear's ufo seems to be a better solution. I've spent the past several days trying to figure out how to add detail around KMYR and make the changes global to everyone. I'm not having much luck :/ [[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 15:48, 28 January 2019 (EST)

Talk:Route manager

2019-01-27T07:44:45Z

J8d4c3: I hate this wiki's automated edit anti-spam question!

== Issues reported on the forums ==
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8317 Route Manager]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8345 2.0 Route Manager]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8295 Route Manager Issue/Other questions]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8048 Route Manager and AP]
* [http://forum.flightgear.org/viewtopic.php?f=40&t=22414 Route button of Route Manager] – Get route to the ''clicked'' point in the list
 
Deleted the following link from "Useful Software". Reference https://en.wikipedia.org/wiki/RubyForge
*[http://rubyforge.org/projects/fgmap Flightgear Mapping] is useful. With just a few clicks you can add navaids displayed on the map and as well a route you have defined there via waypoints. Navaids can be inserted into the list at any point, not just at the end.[[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 02:41, 27 January 2019 (EST)

Talk:Route manager

2019-01-27T07:41:49Z

J8d4c3: Documented deleted link. This also saves the program's name in case someone finds another source for the program it pointed to.

== Issues reported on the forums ==
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8317 Route Manager]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8345 2.0 Route Manager]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8295 Route Manager Issue/Other questions]
* [http://forum.flightgear.org/viewtopic.php?f=25&t=8048 Route Manager and AP]
* [http://forum.flightgear.org/viewtopic.php?f=40&t=22414 Route button of Route Manager] – Get route to the ''clicked'' point in the list
 
Deleted the following link from "Useful Software"
*[http://rubyforge.org/projects/fgmap Flightgear Mapping] is useful. With just a few clicks you can add navaids displayed on the map and as well a route you have defined there via waypoints. Navaids can be inserted into the list at any point, not just at the end.[[User:J8d4c3|J8d4c3]] ([[User talk:J8d4c3|talk]]) 02:41, 27 January 2019 (EST)

Route manager

2019-01-27T07:37:24Z

J8d4c3: Deleted link to defunct website

{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}

A real '''route-manager''' page!

[[File:Routemanager.jpg|thumb|270px|The route manager dialog.]]

== Introduction ==
(in the following sections, familiarity with basic [[IFR]] concepts, [[Autopilot]] usage and [[radio navigation]] is assumed)

The route-manager models part of the functionality found in real-world [[GPS]] and FMS devices, but is usable in any aircraft. Some panel instruments may provide access to the route manager via their own UI, but the route-manager is always available through a generic dialog box. The route-manager is also how a flight plan is made available to FlightGear - in the future this will hopefully permit better [[ATC]] and multi-player interactions, since [[ATC]] logic or controllers will be able to observe the filed plan associated with a pilot.

It's important to realize that the route-manager (and [[GPS]]) are pieces that a panel instrument might present as a single real world device - the mapping between C++ modules, generic user interface and in-panel instruments is very fluid, by design. In general core features exist in whichever place seems the most natural, and it's up to instruments to aggregate the core modules as they require.

== Concepts ==
The route-manager maintains a flight-plan, consisting of departure, destination, alternate airport and cruise information, as well as a list of waypoints. All information is currently optional, which is highly unrealistic, but convenient.

Route manager waypoints are entered as a [[navaid]] ident, an explicit latitude/longitude pair, or as an offset (bearing and distance) from another navaid. Each waypoint may also have an [[altitude]] associated with it, for vertical navigation modes (VNAV). In the future, other data, especially speed restrictions, may also be associated with waypoints.

The route-manager maintains a ''current waypoint'', which is shown in route-manager dialog, the GPS dialog (in LEG mode), on the default HUD, and potentially in cockpit displays in the aircraft. Normally, the route-manager moves automatically to the next waypoint after passing the current point (this is known as 'sequencing'), but if necessary the active waypoint can be manually adjusted.

An important piece of terminology is a ''leg'', which is a section of route between two waypoints. Many real-world devices deal in legs primarily, since each leg corresponds to a desired track, a distance and possibly an altitude to climb / descend. In the FlightGear route manager, the ''active leg'' is from the previous waypoint to the current waypoint - i.e the current waypoint is where you're heading to at the moment.

== Defining a Route ==
The simplest way to define a route is to add waypoints one at a time by identifier. Since navaid identifiers are not unique, the route-manager uses your departure airport or the previously defined waypoint to locate the identifier search. In practice, navaids with conflicting names are located far enough apart that this works automatically in practice.

From Flightgear 2016.2.0 onwards, it is also possible to add a list of waypoints using the route manager dialog. These should be separated by spaces, e.g. "TLA DCS HON WCO BNN" and the result is the same as typing individually and pressing the add button for each.

Until departure and arrival procedures are supported, you can often define them yourself, by creating offset waypoints, as shown in the examples below.

Routes can be loaded and saved to and from a simple XML format, so you may prefer to create the routes in a text editor, and load them instead of entering them by hand. You can also use a 3rd party flight-planning tool to create the route, export the route in GPX format and load the file with the route manager (requires FlightGear >= 2.99 and the file must have the suffix ".gpx"). Contact the developer list if you are interested on working on support for further file formats.

In the future, auto-routing using airways or VOR-VOR routing will also be added.

Example waypoint definitions:

;KJFK
: airport identifier
;UW
: navaid identifier ([[NDB]], [[VOR]] or a fix/interaction)
;TLA/210/35
: offset from a [[navaid]] - in this example, the 210-degree magnetic radial from TLA VOR, 35 nautical miles out
;WOBAD@18000
: WOBAD fix, at eighteen thousand feet altitude
;SPL/050/12.3@2000
: 12.3 nautical miles from SPL VOR on the 050 magnetic radial, at two thousand feet
;-20,55
: virtual point at W020N55, eg. when flying North Atlantic Tracks

See also [[#Useful Software]]

=== SIDs and STARs ===
As of FlightGear 2.4.0, the route manager has basic [[SID]]/[[STAR]] support. The route files are not free; access for a single {{wikipedia|AIRAC}} cycle and subscriptions can be bought at [http://www.navigraph.com/ Navigraph].

# Download the Level-D formatted files from the [http://www.navigraph.com/FmsDataPricing.aspx Navigraph manual install page]; log in and pay for the access when prompted. '''Save the .exe file somewhere safe (in case you need to reinstall the route files in the future): Navigraph won't provide you with another copy when the next data update comes out.'''
# Run the executable file. When prompted, choose to extract the data files in a directory on your Desktop (or in another easily accessible place).
# Open that directory, you will find many XML files named <tt>ICAO.procedures.xml</tt> (where <tt>ICAO</tt> is the ICAO code of the airport the XML file refers to): move each of them to [[$FG_SCENERY]]/Airports/<tt>I</tt>/<tt>C</tt>/<tt>A</tt>/<tt>ICAO</tt>.procedures.xml (replace <tt>I</tt>, <tt>C</tt>, <tt>A</tt> and <tt>ICAO</tt> with the corresponding letters of the ICAO code). (Example: put <tt>EDDF.procedures.xml</tt> in [[$FG_SCENERY]]/Airports/E/D/D/EDDF.procedures.xml</tt>).

The third point can be automated to install many procedure files at once:

* If you have Ruby installed on your computer, you can use [http://files.goneabitbursar.com/fg/install-navdat.rb this renaming script].
* Another possibility, using [https://www.python.org/ Python] 3, is this [http://frougon.net/python_dumping_ground/short_scripts/extract-navdata.py extract-navdata.py script], which can install the files from a directory or directly from a tarball. Run <tt>extract-navdata.py --help</tt> or <tt>python3 extract-navdata.py --help</tt> for instructions. You may need to use <tt>py -3</tt> instead of <tt>python3</tt> on Windows, cf. [https://docs.python.org/3/using/windows.html Using Python on Windows].
* You could also use a small bash-script to do the work for you. Bash is a shell, native on Linux, also exists on Macs. Copy the following code into a new file, name it "convert.sh". Put it into the lowest directory, where all the xml-files are stored. (.../Level-D Simulations/navdata/)
:<syntaxhighlight lang="bash" enclose="div">#!/bin/bash

for file in *.xml
do
FILENAME=$( echo $file | sed s/.xml// )
DIR=$( echo "$FILENAME" | sed s/[A-Z0-9]\$// )
ONE=$( echo "$DIR" | sed s/[A-Z0-9]\$// | sed s/[A-Z0-9]\$// )
TWO=$( echo "$DIR" | sed s/[A-Z0-9]// | sed s/[A-Z0-9]\$// )
THREE=$( echo "$DIR" | sed s/[A-Z0-9]// | sed s/[A-Z0-9]// )
#echo "$file => $DIR => $ONE / $TWO / $THREE / $file"
mkdir -pv "../Airports/$ONE/$TWO/$THREE"
cp -v $file "../Airports/$ONE/$TWO/$THREE/$FILENAME.procedures.xml"
done
</syntaxhighlight>
:# Now it's time to fire up a terminal and navigate to the files: <code>cd /path/to/Level-D Simulations/navdata</code>
:# To make the script executable type: <code>chmod +x convert.sh</code>
:# Now you're ready to run the script! <code>./convert.sh</code>
:When the script is done, you will find a new folder on your hard-disk: "/path/to/LevelD/Airports" which contains the files in our "I/C/A/ICAO.procedures.xml fashion". You can now copy this Airports-folder into a new scenery-folder and add it to your scenery-list.

Next time you start FlightGear, you can load the routes through the route manager interface.

=== Flying Approaches ===
The route manager can also be used to fly from airport to airport without using navaids or waypoints. The following is a step-by-step tutorial on how to plan a flight from KSFO-KLAX without using navaids or waypoints.

In the route manager, you will see two rows at the top: departure and arrival. They are almost the same, except departure has SID and the arrival airport has STAR (see below, SID/STAR).

1. In the departure airport row, fill in the ICAO of the airport you are departing from (KSFO) as well as the runway you are taking off from. (10R) If you are not familiar with the airport, choose your departure runway carefully, as your taxi time will depend on the distance of this runway. The SID dropdown can remain as it is.

2. In the arrival airport row, fill in the ICAO of the airport you are arriving at (KLAX) as well as the runway you will be landing on. (06L) Again, if you are not familiar with this airport, choose your arrival runway carefully, as this may significantly extend flight time. Next, select "Default" in the approach dropdown box. STAR can remain as it is.

3. There should now be a list of waypoints below the information fields. The first waypoint (outside of the airport) is a ways from the departure airport (in this example, 283.9 NM). However, the waypoints following that continue the approach, so they are only a few nautical miles away from the previous. The list should be populated with at least 4 waypoints, excluding the airports. When this is true, proceed to the next step.

4. There is a row of buttons at the bottom of the route manager. Press the button that says "Activate". This will enable the route that you have created (in this case, KSFO-KLAX). However, we don't want to fly to the airport we're already at. We want to fly to the first waypoint, which should be APP-4. To do this, click on APP-4 and click the "Jump To" button at the bottom. APP-4 should now be highlighted in orange. This means that autopilot is ready to fly to that waypoint.

5. Once you get above 500ft, after takeoff, enable autopilot. Click LNAV for lateral navigation to that first waypoint. Your plane will make a slight turn (in this case) towards Los Angeles. Altitude works separately, so you will have to set your own altitude and vertical speed. (If pressing the LNAV button only produces this error: "Captain, we forgot to program or activate the route manager!", you forgot to click the activate button! Repeat step 4 and 5, then proceed to step 6. You should pause the simulation while doing this.)

6. Your planes will make all the turns for you to get on approach. Remember that you, the pilot, are responsible for altitude, which deserves a whole different tutorial in itself.

== Activating a Route ==
Activating a route performs certain checks, and creates start and end waypoints based on the selected departure and arrival info. For the moment, that consists of adding the departure runway as waypoint zero, but in the future (when departure procedures are supported) this will create the appropriate procedure waypoints.

This will also be the hook point for calculating cruise information, such as top-of-climb and top-of-descent points in the future.

Other devices (especially a GPS/FMS) may trigger other changes based on activating a route, such as sequencing the first leg of the route, resetting internal counters / timers, and so on.

== Flying a Route ==

When a route is activated, the GPS system enters 'leg' mode, and will automatically sequence waypoints as they are overflown. Note that all aircraft can use the default route-manager and GPS functions, even aircraft that would never (historically) has such systems. This is a convenience to casual users, testing, and so on.

In particular, the GPS drives some properties of the generic autopilot, so 'true heading hold' mode can be used to fly the route manager route (or any other GPS course).

The default [[HUD]] (activated by pressing 'h') shows information about the active waypoint and leg, in the top-left corner. Notably, it includes the identifier, time and distance to the current waypoint, the magnetic bearing to the waypoint, and the current ground track, and finally the deviation (in nautical miles) from the leg course.

In aircraft with realistic navigation systems, or customised autopilots, the default behaviours above may not work; hopefully the aircraft author has provided alternative methods, such as panel instruments, to control the interaction with that aircraft's autopilot and panel.

=== Lining up with Runways ===
The route-manager only provides guidance to a particular location - to arrive on a particular heading, such as lined up with a runway or [[ILS]] localizer, it is necessary to use multiple waypoints. Virtually all ILS approaches define multiple [[fixes]] that can be used for this purpose, usually including altitude restrictions. For example, for the [http://flightaware.com/resources/airport/KPHX/IAP/ILS+OR+LOC+RWY+08 KPHX 08 approach], waypoints ALLIS, SARTE, HIKID, ILIKE, JAMIL and WAZUP are defined, extending 20nm from the threshold. Typically you enter the initial approach fix (IAF), ALLIS in this example, and as many of the intermediate waypoints as necessary, depending on required descent profile. It is helpful to include the glidepath capture waypoint (WAZUP), to provide an easy altitude reference and cross-check that your ILS receiver is working.

== Properties ==
When a route is active, the route-manage provides various pieces of information based upon current aircraft position / speed, and the route progress. These values would be calculated by the navigation computer in a real system, but are handled by route-manage in FG for convenience. Values logged include the takeoff time, estimated time enroute (ETE), distance remaining enroute, and so on - browse the property tree to see what's available.

== Useful Software ==
To easily create entries for route manager the application;
*[http://sourceforge.net/projects/fgflightplanner/ Kelpie Flight Planner] appears to be a very thorough route planning tool that works on Windows, Linux and other operating systems.

== Related content ==
* For additional route managr system details, see [[Route manager internals]].
* [[Howto: Create a flightplan]]
* [[Radio beacons]]
* [[Radio navigation]]

[[Category:Autoflight| ]]
[[Category:FlightGear feature]]
[[Category:Menubar]]

[[es:Gestor de rutas]]
[[zh:Route_manager]]

User:J8d4c3/Level-D 767 XML File Format

2019-01-26T03:53:19Z

J8d4c3: Still editing

== Level-D 767 XML File Format ==

=== Information Sources: ===

https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/ 
Options:
# Download and extract the digital Terminal Procedure Publication files. A few zip files that each contain a large number of pdf files. Download the "E" file first. Follow instructions in the included README FILE.
# Use the [https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/search/ Terminal Procedures Search application] to find files for a specific airport 

Navaid coordinates https://www.faa.gov/air_traffic/flight_info/aeronav/aero_data/Loc_ID_Search/Fixes_Waypoints/ 
FlightGear seems to have a database of these that are shown on the map. Find it! 
nav.dat & fix.dat 
src/Airports/sidstar.cxx 
RouteManager 
src/Navaids 

 
==== Definitions ====
Star - A route of an inbound flightpath to an airport [https://en.wikipedia.org/wiki/Standard_terminal_arrival_route 1] 
Sid - A route of an outbound flightpath away from an airport [https://en.wikipedia.org/wiki/Standard_instrument_departure 2] 
Waypoint - Any of the star-shaped icons seen on a map. 
....The Waypoint's name is in bold print 
....Any Altitude restrictions, speed limit is/are listed under the waypoint's name 

=== Fields ===
(M) = Mandatory information 
(O) = Optional information 
 

(M)File name: <Four digit airport code>.procedures.xml 
 
(M)ProceduresDB 
(M)Airport - At least one 
(M)Star or Sid - At least one 
 

==== Star ====
(M)Star name, Runways 
(M)Star Waypoint, ID - At least one 
 

==== Star Waypoint ====
(M)Star Waypoint, ID 
(M)Name 
(M)Type Normal or Hold 
(M)Latitude 
(M)Longitude 
(O)Altitude 
(O)AltitudeRestriction above / below 
(O)Speed 

 

==== Normal ====
 

==== Hold ====
Hld_Rad_or_Inbd 
Hld_Rad_value 
Hld_Turn 
Hld_Time_or_Dist 
Hld_td_value 
 

<ProceduresDB>
<Airport ICAOcode="LSGG">
<Star Name="LUSAR 1N" Runways="05">
<Star_Waypoint ID="1">
<Name>LUSAR</Name>
<Type>Normal</Type>
<Latitude>46.668888</Latitude>
<Longitude>5.179444</Longitude>
<Altitude>20000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>DINIG</Name>
<Type>Hold</Type>
<Latitude>46.495278</Latitude>
<Longitude>5.890556</Longitude>
<Speed>230</Speed>
<Altitude>7000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
<Altitude>24000</Altitude>
<AltitudeRestriction>below</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>144</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>1.0</Hld_td_value>
</Star_Waypoint>

User:J8d4c3/Level-D 767 XML File Format

2019-01-26T00:22:09Z

J8d4c3: FILE.

== Level-D 767 XML File Format ==

=== Information Sources: ===

https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/ 
Options:
# Download and extract the digital Terminal Procedure Publication files. A few zip files that each contain a large number of pdf files. Download the "E" file first. Follow instructions in the included README FILE.
# Use the [https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/search/ Terminal Procedures Search application] to find files for a specific airport 

 
==== Definitions ====
Star - A route of an inbound flightpath to an airport [https://en.wikipedia.org/wiki/Standard_terminal_arrival_route 1] 
Sid - A route of an outbound flightpath away from an airport [https://en.wikipedia.org/wiki/Standard_instrument_departure 2] 
Waypoint - Any of the star-shaped icons seen on a map. 
....The Waypoint's name is in bold print 
....Any Altitude restrictions, speed limit is/are listed under the waypoint's name 

=== Fields ===
(M) = Mandatory information 
(O) = Optional information 
 

(M)File name: <Four digit airport code>.procedures.xml 
 
(M)ProceduresDB 
(M)Airport - At least one 
(M)Star or Sid - At least one 
 

==== Star ====
(M)Star name, Runways 
(M)Star Waypoint, ID - At least one 
 

==== Star Waypoint ====
(M)Star Waypoint, ID 
(M)Name 
(M)Type Normal or Hold 
(M)Latitude 
(M)Longitude 
(O)Altitude 
(O)AltitudeRestriction above / below 
(O)Speed 

 

==== Normal ====
 

==== Hold ====
Hld_Rad_or_Inbd 
Hld_Rad_value 
Hld_Turn 
Hld_Time_or_Dist 
Hld_td_value 
 

<ProceduresDB>
<Airport ICAOcode="LSGG">
<Star Name="LUSAR 1N" Runways="05">
<Star_Waypoint ID="1">
<Name>LUSAR</Name>
<Type>Normal</Type>
<Latitude>46.668888</Latitude>
<Longitude>5.179444</Longitude>
<Altitude>20000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>DINIG</Name>
<Type>Hold</Type>
<Latitude>46.495278</Latitude>
<Longitude>5.890556</Longitude>
<Speed>230</Speed>
<Altitude>7000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
<Altitude>24000</Altitude>
<AltitudeRestriction>below</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>144</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>1.0</Hld_td_value>
</Star_Waypoint>

User:J8d4c3/Level-D 767 XML File Format

2019-01-25T22:54:16Z

J8d4c3: Still editing

== Level-D 767 XML File Format ==

=== Information Sources: ===
https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/ 
Download and extract the digital Terminal Procedure Publication files. A few zip files that each contain a large number of pdf files. 
or use the [https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/search/ Terminal Procedures Search application] to find files for a specific airport 

 
==== Definitions ====
Star - A route of an inbound flightpath to an airport [https://en.wikipedia.org/wiki/Standard_terminal_arrival_route 1] 
Sid - A route of an outbound flightpath away from an airport [https://en.wikipedia.org/wiki/Standard_instrument_departure 2] 
Waypoint - Any of the star-shaped icons seen on a map. 
....The Waypoint's name is in bold print 
....Any Altitude restrictions, speed limit is/are listed under the waypoint's name 

=== Fields ===
(M) = Mandatory information 
(O) = Optional information 
 

(M)File name: <Four digit airport code>.procedures.xml 
 
(M)ProceduresDB 
(M)Airport - At least one 
(M)Star or Sid - At least one 
 

==== Star ====
(M)Star name, Runways 
(M)Star Waypoint, ID - At least one 
 

==== Star Waypoint ====
(M)Star Waypoint, ID 
(M)Name 
(M)Type Normal or Hold 
(M)Latitude 
(M)Longitude 
(O)Altitude 
(O)AltitudeRestriction above / below 
(O)Speed 

 

==== Normal ====
 

==== Hold ====
Hld_Rad_or_Inbd 
Hld_Rad_value 
Hld_Turn 
Hld_Time_or_Dist 
Hld_td_value 
 

<ProceduresDB>
<Airport ICAOcode="LSGG">
<Star Name="LUSAR 1N" Runways="05">
<Star_Waypoint ID="1">
<Name>LUSAR</Name>
<Type>Normal</Type>
<Latitude>46.668888</Latitude>
<Longitude>5.179444</Longitude>
<Altitude>20000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>DINIG</Name>
<Type>Hold</Type>
<Latitude>46.495278</Latitude>
<Longitude>5.890556</Longitude>
<Speed>230</Speed>
<Altitude>7000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
<Altitude>24000</Altitude>
<AltitudeRestriction>below</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>144</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>1.0</Hld_td_value>
</Star_Waypoint>

User talk:J8d4c3/Level-D 767 XML File Format

2019-01-25T21:19:41Z

J8d4c3:

User:J8d4c3/Level-D 767 XML File Format

2019-01-25T17:21:36Z

J8d4c3: Initial data entry

== Level-D 767 XML File Format ==

=== Information Sources: ===
https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/ 

=== Fields ===
(M) = Mandatory information 
(O) = Optional information 
 

(M)File name: <Four digit airport code>.procedures.xml 
 
(M)ProceduresDB 
(M)Airport - At least one 
(M)Star or Sid - At least one 
 

==== Star ====
(M)Star name, Runways 
(M)Star Waypoint, ID - At least one 
 

==== Star Waypoint ====
(M)Star Waypoint, ID 
(M)Name 
(M)Type Normal or Hold 
(M)Latitude 
(M)Longitude 
(O)Altitude 
(O)AltitudeRestriction above / below 
(O)Speed 

 

==== Normal ====
 

==== Hold ====
Hld_Rad_or_Inbd 
Hld_Rad_value 
Hld_Turn 
Hld_Time_or_Dist 
Hld_td_value 
 

<ProceduresDB>
<Airport ICAOcode="LSGG">
<Star Name="LUSAR 1N" Runways="05">
<Star_Waypoint ID="1">
<Name>LUSAR</Name>
<Type>Normal</Type>
<Latitude>46.668888</Latitude>
<Longitude>5.179444</Longitude>
<Altitude>20000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>DINIG</Name>
<Type>Hold</Type>
<Latitude>46.495278</Latitude>
<Longitude>5.890556</Longitude>
<Speed>230</Speed>
<Altitude>7000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
<Altitude>24000</Altitude>
<AltitudeRestriction>below</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>144</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>1.0</Hld_td_value>
</Star_Waypoint>

User:J8d4c3/Level-D 767 XML File Format

2019-01-25T16:39:46Z

J8d4c3:

File name: <Four digit airport code>.procedures.xml

ProceduresDB
Airport
Star or Sid

Star
Star name, Runways
Star Waypoint, ID

Star Waypoint
Star Waypoint, ID
Name
Type Normal or Hold

Normal
Type = Normal
Latitude
Longitude
Speed
Altitude
AltitudeRestriction above

Hold
Type = Hold
Hld_Rad_or_Inbd
Hld_Rad_value
Hld_Turn
Hld_Time_or_Dist
Hld_td_value

Latitude
L
<ProceduresDB>
<Airport ICAOcode="LSGG">
<Star Name="LUSAR 1N" Runways="05">
<Star_Waypoint ID="1">
<Name>LUSAR</Name>
<Type>Normal</Type>
<Latitude>46.668888</Latitude>
<Longitude>5.179444</Longitude>
<Altitude>20000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
</Star_Waypoint>
<Star_Waypoint ID="4">
<Name>DINIG</Name>
<Type>Hold</Type>
<Latitude>46.495278</Latitude>
<Longitude>5.890556</Longitude>
<Speed>230</Speed>
<Altitude>7000</Altitude>
<AltitudeRestriction>above</AltitudeRestriction>
<Altitude>24000</Altitude>
<AltitudeRestriction>below</AltitudeRestriction>
<Hld_Rad_or_Inbd>Inbd</Hld_Rad_or_Inbd>
<Hld_Rad_value>144</Hld_Rad_value>
<Hld_Turn>Left</Hld_Turn>
<Hld_Time_or_Dist>Time</Hld_Time_or_Dist>
<Hld_td_value>1.0</Hld_td_value>
</Star_Waypoint>

User talk:J8d4c3/Level-D 767 XML File Format

2019-01-25T16:13:19Z

J8d4c3: Initial file creation

User talk:J8d4c3/Level-D 767 XML File Format

2019-01-25T16:12:12Z

J8d4c3: Created page with "Not finding any free SID/STAR files for airports, I have decided to learn how to create my own. The information shown here is gleaned from examining files found on the Interne..."

User:J8d4c3

2019-01-25T16:11:56Z

J8d4c3:

User:J8d4c3/Level-D 767 XML File Format

2019-01-25T16:05:51Z

J8d4c3: Created page with "test"

test

User:J8d4c3

2019-01-25T16:05:40Z

J8d4c3:

Hey, I got a page. Now what do I do with it?
User:User name/Article name
[[User:J8d4c3/Level-D_767_XML_File_Format]]

User:J8d4c3

2013-07-07T17:26:10Z

J8d4c3: init

Hey, I got a page. Now what do I do with it?

Talk:WorldEditor

2013-07-07T17:23:25Z

J8d4c3:

WorldEditor

2013-07-07T17:20:16Z

J8d4c3: Rearranging text

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Starting WED for the first time ==
X-Plane itself does not need to be installed before using WED. However, WED will require that you choose the X-Plane folder before it will allow you to do anything. Create a working directory with the following structure before starting WED for the first time.
working directory <-- Pick a name
|--Custom Scenery
|--Global Scenery
|--Resources
|--default scenery
NOTICE: WED looks for this specific directory structure and specific directory names !

Click "Choose X-Plane folder". Select the <tt>working directory</tt> for the X-Plane folder.

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED tutorial part two] (Xsimreviews blog)
* [http://www.x-plane.com/support/manuals/wed/ Online version of the WorldEditor Manual] (webpage)

[[Category:Software]]
[[Category:Scenery enhancement]]

Talk:WorldEditor

2013-07-07T17:02:05Z

J8d4c3: Starting WED for the first time notes

WorldEditor

2013-07-07T16:39:45Z

J8d4c3: typo fix and added link to WED manual

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

== Starting WED for the first time ==
WED will require that you choose the X-Plane folder before it will do anything else. Create a working directory with the following structure before starting WED for the first time.
working directory
|--Custom Scenery
|--Global Scenery
|--Resources
|--default scenery
NOTICE: WED looks for this specific directory structure and directory names !
Reference:
xptools/src/WEDCore/WED_PackageMgr.cpp lines 33-35
CUSTOM_PACKAGE_PATH="Custom Scenery"
GLOBAL_PACKAGE_PATH="Global Scenery"
DEFAULT_PACKAGE_PATH="Resources" DIR_STR="default scenery"
This paragraph was written by a person who is a newbie to WED. An experienced WED user is requested to verify and edit this as required.

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED tutorial part two] (Xsimreviews blog)
* [http://www.x-plane.com/support/manuals/wed/ Online version of the WorldEditor Manual] (webpage)

[[Category:Software]]
[[Category:Scenery enhancement]]

WorldEditor

2013-07-07T16:28:50Z

J8d4c3: Starting WED for the first time - minor edit of what I typed earlier

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

== Starting WED for the first time ==
WED will require that you Choose the X-Plane folder before it will do anything else. Create a working directory with the following structure before starting WED for the first time.
working directory
|--Custom Scenery
|--Global Scenery
|--Resources
|--default scenery
NOTICE: WED looks for this specific directory structure and directory names !
Reference:
xptools/src/WEDCore/WED_PackageMgr.cpp lines 33-35
CUSTOM_PACKAGE_PATH="Custom Scenery"
GLOBAL_PACKAGE_PATH="Global Scenery"
DEFAULT_PACKAGE_PATH="Resources" DIR_STR="default scenery"
This paragraph was written by a person who is a newbie to WED. An experienced WED user is requested to verify and edit this as required.

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:
build/Linux/release_opt/WED

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED tutorial part two] (Xsimreviews blog)

[[Category:Software]]
[[Category:Scenery enhancement]]

WorldEditor

2013-07-07T16:15:38Z

J8d4c3: Requirements to start WED for the first time

{{Infobox Software
| title = WorldEditor
| image = WorldEditor_EHAM.png
| alt = [[Amsterdam Airport Schiphol|Amsterdam Schiphol]] in WED.
| developedby = Ben Supnik, Cristiano Maggi
| initialrelease = 2007
| latestrelease =
| os = GNU/Linux, Windows, MacOS X
| website = http://scenery.x-plane.com/tools.php
| license = [[GNU General Public License]]
}}
'''WorldEditor''' ('''WED''') is a CAD-like graphic editor that lets you create custom airport layouts. It is designed for X-Plane, and works with [[apt.dat]] version 850 and higher.

== Obtaining WorldEditor ==
=== Mac/Windows ===
Stable WED binaries for Windows and Mac can be downloaded from [http://scenery.x-plane.com/tools.php scenery.x-plane.com]. A development version is available through: [http://dev.x-plane.com/download/tools/ dev.x-plane.com].

In order to work with WED without installing X-Plane, one needs to create a special <tt>Custom Scenery</tt> directory, for example <tt>X-Plane/Custom Scenery</tt>. When launching WED for the first time, click the "Choose X-Plane folder" directory and select the folder that your <tt>Custom Scenery</tt> houses in (in our example: <tt>X-Plane</tt>).

=== Linux ===
Because there is no (stable) binary available for Linux based operating systems, the user has to compile it from source. Don't be afraid of that, since it brings most of its dependencies along, it is not hard. However, some things need to be provided by the user's system:
* binutils and binutils-devel
* [[git]]
* GNU coreutils
* GNU make
* libmpfr-devel
* mesa-libGL-devel and mesa-libGLU-devel
* qt4-devel

Downloading WED's source (about 170 MiB) is done via <tt>git</tt>:
git clone http://dev.x-plane.com/git/xptools.git xptools.git
cd xptools.git

Afterwards WED's dependencies have to be downloaded (about 260 MiB) and compiled. These steps have to be done only once, before compiling WED the first time:
git submodule update --init
cd libs
make -j2
cd ..

Compiling WED:
conf=release_opt make -j2 WED

You may now copy the file <tt>build/Linux/release_opt/WED</tt> to <tt>~/bin</tt> or another location within your $PATH environment variable:
cp build/Linux/release_opt/WED ~/bin

== Starting WED for the first time ==
WED will require that you Choose the X-Plane folder before it will do anything else. Create a working directory with the following structure before starting WED for the first time.
working directory
|--Custom Scenery
|--Global Scenery
|--Resources
|--default scenery
WED looks for this specific directory structure.
Reference:
xptools/src/WEDCore/WED_PackageMgr.cpp lines 33-35
CUSTOM_PACKAGE_PATH="Custom Scenery"
GLOBAL_PACKAGE_PATH="Global Scenery"
DEFAULT_PACKAGE_PATH="Resources" DIR_STR="default scenery"
This paragraph was written by a person who is a newbie to WED. I will edit it as I learn more. An experienced WED user is more than welcome to edit this.

As on [[#Mac/Windows|Mac/Windows]] WED needs a certain working directory <tt>some_name/Custom Scenery</tt>. Assuming your self made scenery stuff lives (/is going to be) in <tt>~/FGscenery-workbench</tt>, create a directory:
mkdir -p ~/FGscenery-workbench/Custom\ Scenery

Choose <tt>FGscenery-workbench</tt> as "X-PLANE FOLDER" the first time you start WED:
build/Linux/release_opt/WED

There is a beta binary of WorldEditor 1.2 which is quite usable but you have to be careful and save your work often because it could crash and make you lose your work. Note that this binary works only on 64 bit linux systems. [http://developer.x-plane.com/tools/worldeditor/ developer.x-plane.com]

== Related content ==
* [[TaxiDraw]], editor for [[Interactive traffic#Ground networks|groundnetworks]] and apt.dat below version 850.

== External links ==
* [http://wiki.x-plane.com/Airport_Creation Airport Creation] (X-Plane wiki)
* [http://wiki.x-plane.com/X-Plane_Scenery_Tools_Development How to compile WED] (X-Plane wiki)
* [http://xsimreviews.com/2012/12/16/x-plane-scenery-design-tutorial-4-wed-pt1/ WED tutorial part one] (Xsimreviews blog)
* [http://xsimreviews.com/2013/02/03/x-plane-scenery-design-tutorial-5-wed-part-ii/ WED tutorial part two] (Xsimreviews blog)

[[Category:Software]]
[[Category:Scenery enhancement]]

Airbus A380

2013-05-08T02:16:13Z

J8d4c3: Add external link to http://en.wikipedia.org/wiki/Airbus_A380

{{infobox Aircraft
|image = A380 in flight.png
|name = Airbus A380
|type = Airliner
|livery = Airbus, Singapore, Qantas
|liverydbid = 5
|authors = Ampere K, Innis Cunningham, Fahim Dalvi, S.Hamilton
|fdm = JSBSim
|status-fdm = 4
|status-systems = 4
|status-cockpit = 4
|status-model = 4
|fgname = A380
|download =
|development = http://gitorious.org/airbus-aircraft/a380
}}
The '''Airbus A380''' is a double-deck, wide-body, four-engine [[:Category:Airliners|airliner]] manufactured by the European corporation [[:Category:Airbus|Airbus]], an EADS subsidiary. The largest passenger airliner in the world, the A380 made its maiden flight on 27 April 2005 from Toulouse, France, and made its first commercial flight on 25 October 2007 from Singapore to Sydney with Singapore Airlines. The aircraft was known as the Airbus '''A3XX''' during much of its development phase, but the nickname '''Superjumbo''' has since become associated with it.

The A380's upper deck extends along the entire length of the fuselage. This allows for a cabin with 50% more floor space than the next-largest airliner, the [[Boeing 747-400]], and provides seating for 525 people in standard three-class configuration or up to 853 people in all economy class configuration. The A380 is offered in passenger and freighter versions. The A380-800, the passenger model, is the largest passenger airliner in the world, superseding the Boeing 747, but has a shorter fuselage than the Airbus [[Airbus A340|A340-600]] which is Airbus' next biggest passenger aeroplane. The A380-800F, the freighter model, is offered as one of the largest freight aircraft, with a listed payload capacity exceeded only by the [[Antonov AN-225]]. The A380-800 has a design range of 15,700 kilometres (8,500 nm), sufficient to fly from Sydney to Helsinki, or Concepción to Dubai for example, and a cruising speed of Mach 0.85 (about 900 km/h or 560 mph at cruise altitude).

== Aircraft help ==

An [[A380 Tutorial]] takes the reader through the detail of how to control the aircraft and use many of the Airbus specific Flight Control features. There is also in built-in tutorial to the aircraft model that helps the beginner start the aircraft.

=== Startup ===
# Set fuel and CG (CG is displayed on centre pedestal ECAM screen)
# Start APU by clicking Master SW on the overhead
# Optionally enter flight plan on MFD
# Optionally set T.O. Performance on MFD [[File:A380 mcdu01.png|thumb|right|Left MCDU shows PERF page, right MCDU shows INIT page]]
# click on strobe and beacon lighting
# Switch Engine Start to IGN/START on overhead
# Turn on engines in pairs from the inboard first, waiting for N2 to reach 25% before starting the next pair
# once all engines are running, use the middle-mouse button to return the Engine Start knob back to Normal
# you can turn off the APU by clicking the APU Master Sw.

=== Takeoff ===
# release parking brake
# Flaps to position 2 (0-4)
# Push throttle to around 50% N1 and wait to stabilise
# use SHIFT+Page-Up to move thrust lever to FLEX or TOGA detent
# Get Vr speed (~165 kts) and rotate
# pitch up to around 10deg and maintain 210kts
# Gear up
# AP1 enabled, push HDG to managed mode if flight plan entered
# At THR LVR on PFD reduce thrust levers to CL detent using Shift+Page-Down
# Before THR ACCEL retract flaps fully

=== Airbus Flight Guidance ===
This aircraft supports the Airbus Auto-Flight System Flight Guidance controls. The controls on the AFS Control Panel operate in either "managed mode" or "selected mode". Managed mode is the normal operating position for most controls and is enabled by pushing the control. Managed Mode allows the FMC to calculate that control and will take parameters from;
# the flight plan as entered on the MFD
# the current phase of flight
# the performance characteristics as entered on the MFD
Selected Mode is enabled by pulling the control, the pilot can enter a value before enabling the control, the Flight Guidance system will attain and hold that value once the control is enabled. Use the Glareshield AFS Control Panel rather than the Autopilot Dialog (F11) as the autopilot values will be over-written by the FMC.
[[File:Cockpit a380.png|right|thumb|A380 Cockpit during managed climb]]

=== Flight Management System ===
The Flight Management Computer requires airport SID/STAR data files to be located under the FMS directory under the aircraft install path (ie: [[$FG_ROOT]]/Aircraft/A380/FMS/ ), the files are in the Level-D 767 XML Format and can be downloaded from various public websites for free or for a fee. These are used to calculate the Runway Transition, SID, SID Transition, Top of Descent, STAR Transition, STAR and Instrument Approach Path.

If you use the MFD to enter a departure and arrival airports, flight level and SID/STAR routes, the ILS frequencies will also be tuned with the current airport ILS frequency set in the active NAV1 and the destination ILS frequency set in the standby NAV1 frequency. You can then remain in "managed mode" from cruise level to ILS interception.

== Development status/Issues/Todo ==
Volunteers with knowledge of object-orientated-programming and Nasal-scripting are needed to script the AFDX system. Those who are interested in helping should contact Ampere on the developers' mailing list or react at the [[Talk:Airbus|talk page]].

=== Complete ===
* basic model
** fuselage
** wings (with wing flex)
** vertical and horizontal stabilisers
** flaps and slats
** engines, pylons and wing-tips
* FDM
* autopilot tuning
* engine, wind, seat-belt chime sounds
* pushback
* gear retraction and doors
* fuel tanks
* cargo, crew and passenger point mass
* CL, FLEX and TOGA thrust detents and A/THR
* majority of FMS
* SID/STAR parser
* Flight Guidance Computer
* simple electrical system
* door system, just needs objects to animate!
* animated jetway positions
* auto changeover level
* Environment Control System (cabin pressurisation)
* auto-tuned VOR on NAV2
* anti-ice and air packs take bleed air
* Rembrandt lighting for;
** cockpit lighting
** cockpit panel lighting
** wing lighting
** landing lights
** tail logo lighting
** cabin lighting

==== Glareshield ====
* altitude selected mode
* heading selected mode
* speed selected mode
* vertical managed mode
** SRS
** CLB
** OP CLB
** CRZ
** DES
** OP DES
* lateral managed mode
** NAV
** LOC
* speed managed mode
** CLB
** CRZ
** DES
* localizer and approach
* Flight Director, AP 1 and AP 2
* EFIS baro select (inHg/kPa) and pressure and 'Std' setting
* ND VOR/ADF 1 and VOR/ADF 2 display switch on EFIS
* ND nearby airports display switch on EFIS
* ND traffic display switch on EFIS
* airspeed AP control on FCU selectable between knots or mach value
* altitude selectable between 100ft and 1000ft
* Pre-flight and take-off tutorial (it contains useful stuff, recommended reading)

==== Front Panel ====
* FMA on PFD (active and some armed lateral, vertical and thrust)
* indicated speed ribbon on PFD
* localizer and Glide scope indicators on PFD
* E/WD
* updated Nav Display
** ARC mode
** ROSE mode
** aerodrome moving map with 'ZOOM' scale in PLAN mode
** nearby airports on ND^
** multi-player and AI traffic on ND
** VOR/ADF left-hand and right-hand display
* E/WD checklists
* gear lever and indicators

==== Overhead ====
* apu start
* engine IGN
* strobe, beacon, nav lights, landing, nose
* seat-belt and no-smoking switches
* electrical panel
* air panel
* anti-ice panel

==== Pedestal ====
* Flaps lever
* MFD keyboard and number pad
* ECAM/SD page select
* System Display (ECAM/SD) (many pages)
** permanent data zone
** doors
** cruise
** engines
** apu
** fuel
** electrical AC
** electrical DC
* engine master switches
* MFD (several pages)
** active init
** active departure and SID
** active arrival and STAR
** T.O. Performance
** CRZ Performance
** Active Flight Plan

=== To Do ===
* window and door cut-outs (to work with door system and lighting)
* animate parking brake and <del>speed brake</del>
* <del>cabin interior</del>
* <del>tune LOC and G/S</del>
* flap/slat position on PFD
* <del>livery refresh</del>
* <del>landing</del>, wing, tail and cabin lighting
* <del>landing, wing, tail lighting switches</del>
* <del>engine start sounds</del>
* <del>complete PFD and EFIS selection switches</del>
* <del>complete ND EFIS selection switches</del>^
* <del>complete ND display modes</del>
** PLAN
** <del>LS</del>
** <del>VOR</del>
** <del>MAP</del>
* add standard procedure check-lists to EWD
* complete remaining ECAM pages (skeleton pages already in-place)
** <del>DOOR</del>
** <del>APU</del>
** <del>ENGINE</del>
** COND
** WHEEL
** PRESSURE
** BLEED
** <del>ELEC AC</del>
** <del>ELEC DC</del>
** <del>FUEL</del>
** HYDRAULIC
* complete remaining MFD pages (too numerous to list)
* <del>animation for air/cond overhead panel</del>
* <del>animation for elec overhead panel</del>
* complete fuel overhead panel
* radio panels on pedestal
* <del>gear lever and indicators</del>
* thrust levers
* auto-brake selector
* standby instruments
* <del>calculation of V speeds as part of FMS</del>
* air systems; <del>cabin pressure</del> and temperature
* <del>complete DC and AC electrical system</del>
* <del>replace digit textures with text animation</del>
* <del>fix up scaling of texture sizes</del>
* ATN/FANS+

^ = in recent Git development repository

== External links ==
* [http://www.condoreng.com/support/downloads/tutorials/AFDXTutorial.pdf AFDX Tutorial]
* [http://www.arinc.com/aeec/general_session/gs_reports/2002/presentations/18_adn/adn_summary.pdf ARINC 664 presentation]
* [http://www.airbus.com/en/aircraftfamilies/a380/ Airbus A380 Family Official Homepage]
* [http://www.gillesvidal.com/blogpano/cockpit1.htm Airbus A380 Panoramic 3D Photo]
* [http://en.wikipedia.org/wiki/Airbus_A380 Airbus A380 Wikipedia page]

{{Airbus}}

[[Category:Airliners]]
[[Category:Quadjets]]
[[Category:Cargo aircraft]]

File talk:Seneca II reference left.jpg

2013-03-04T01:32:20Z

J8d4c3: Error in http://wiki.flightgear.org/File:Seneca_II_reference_left.jpg

== Error in http://wiki.flightgear.org/File:Seneca_II_reference_left.jpg ==

3 Mar 2013 - I edited T3r's talk page to inform him of the following error:
The autopilot mode switch is labelled with the number 13. It should be labelled with the number 57.
I thought it best since he created the image to allow him to fix it.
[[User:J8d4c3|J8d4c3]] 01:32, 4 March 2013 (UTC)

User talk:T3r

2013-03-04T01:26:22Z

J8d4c3: /* Error in http://wiki.flightgear.org/File:Seneca_II_reference_left.jpg */ new section

Hi, I have tried to follow your tutorial to learn, how to fly the seneca right (until now, I did just flew it)

As you fly the Seneca yourself it might be hard to understand that a newbee cannot follow "At 500ft above the field reduce the power to 31" manifold pressure and 2500 RPM.Accelerate to 100knots climb speed for a better engine cooling."

I am using a normal joystick. So I reduced the throttle to about those values, with the success, that I slowed down, even if I reduce the climb rate. The plane simply did not accelerate to 100.

I guess there is something left out. Could you please explain some basics? How do you control MP and RPM seperately? With throttle and propeller? What means "Propeller High RPM?" In which position are the cowl flaps open? Lever up or down?
There are many problems for someone who wants to try and learn using this already very detailed tutorial...

Would be a great thing if you could explain it a bit more detailed...

Thanks Wolfram

== Error in http://wiki.flightgear.org/File:Seneca_II_reference_left.jpg ==

Hi T3r,
You have an error in this image.
You have the autopilot mode switch labelled with a 13. It should be labelled with a 57.
And thanks for providing those images and the reference guide.
[[User:J8d4c3|J8d4c3]] 01:26, 4 March 2013 (UTC)