FlightGear wiki - User contributions [en]

Release plan

2012-02-14T20:59:37Z

Intrepid: Just fixed 3 typos

This page contains details about how to release a new version of [[FlightGear]] into the wild. It is a continous work in progress to be improved with every new release.

[[File:ReleasePlan.jpg|thumb|250px|The original plan]]
This release plan was originally developed by Mathias Fröhlich, Martin Spott, Thorsten Brehm and Torsten Dreyer during LinuxTag 2011.

If you think you have something to contribute to the release process, feel free to <span class=plainlinks>[{{SERVER}}{{localurl:{{NAMESPACE}}:{{PAGENAME}}|action=edit}} edit this page]</span>. Please discuss this concept at the mailing-list.

=== General Release Concept ===
New FlightGear releases will be scheduled twice a year. The magic number to remember is 17 (we tried 42, but that didn't turn out so well. 17 is perfect: 1 is not a prime, 7 is a prime and so is 17). On the 17th of January (1) and July (7) a new release branch will be created for SimGear, FlightGear and FGDATA.

After branching, we will allow one month for bug fixing in the release branch, so building and packing of the binaries and FGDATA will take place around February, 18th and August, 18th. Allowing a few days for distribution of the files, new versions should be publically available around the 20th of February and August.

The development stream of SimGear, FlightGear and FGDATA will be set into a frozen state one month before the branch-day (17th) to let the dust of development settle and to allow fixing the most annoying bugs in the code. During this period, developers are requested not to add any new features, subsystems or alike. Immediately after the stream has branched for the release, development in the main stream (next/master) is open for major changes until one month before the next branch-day. This results in a duty cycle of 5 month developing and 1 month thinking.

=== Version Numbers ===
* '''Major releases''' always have '''even numbers''' as the second version element, i.e. 2.4.0, 2.6.0, 2.8.0.
* '''Bugfix releases''' increase the least significant digit: 2.6.1, 2.6.2, 2.6.3.
* The '''development stream''' (''latest Git version'') uses an '''odd number''', increasing the second element of the latest stable release's version by 1: (latest release is 2.4.0 => current development stream is 2.5.0, next official release is 2.6.0).
* The major version number is increased after significant changes to the functionality of the software (i.e. FG 1.x => 2.0 due to switch to OSG).

=== Detailed Time Schedule and Checklist ===
# '''Dec/Jun 17th:''' Development stream is declared "frozen" or "yellow"
#:Send a mail to the flightgear-devel mailing-list to announce the state
#:Create a "release preperations" topic at the forum and make it a "Global Announcement"
#:Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:frozen}}</nowiki></tt>
# '''Jan/Jul 17th:''' Create new release branch, assign new version number to dev-stream, re-open streams
##Send a mail to the flightgear-devel mail-list, asking not to commit/push anything, declare the streams "closed" or "red"
##Post an update to the forum topic
##Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:closed}}</nowiki></tt>
##Bump up the version-number of simgear/next, flightgear/next and fgdata/master to an even number (2.5.0 -> 2.6.0)
##Compile and test drive FlightGear with the new version-number
##Commit the new version number to next (flightgear+simgear) and master(fgdata)
##Tag (annotated) flightgear, simgear and fgdata with "version/2.6.0"
##:''git tag -a version/2.6.0'' (Enter a wise comment)
##Create the release branches on simgear, flightgear and fgdata named release/2.6.0
##:''git branch release/2.6.0''
##On the next/master branches, bump up the version-number of simgear, flightgear and fgdata to an odd number (2.6.0 -> 2.7.0)
##Compile and test drive FlightGear with the new development version number
##Commit the changes of version-number to next/master
##Tag (annotated) flightgear, simgear and fgdata with "version/2.7.0"
##:''git tag -a version/2.7.0'' (Enter a wise comment)
##Push the branches next/master '''and''' release/2.6.0 '''and''' the tags upstream
##:for flightgear, simgear and fgdata: ''git push origin release/2.6.0''
##:for flightgear, simgear and fgdata: ''git push origin version/2.6.0''
##:for flightgear, simgear and fgdata: ''git push origin version/2.7.0''
##:for flightgear and simgear: ''git push origin next''
##:for fgdata: ''git push origin master''
##: Declare dev-streams "open" or "green"
##: Change the content of wiki template at [[Template:GitStatus]] to <tt><nowiki>{{GitStatus:open}}</nowiki></tt>
##:Send a mail to the flightgear-devel mailing-list to announce the state.
## Trigger James for the Jenkins-builds and Curt for a snapshot release and ThorstenB for the OpenSuse build
# '''Feb/Aug 1st:''' Start preparing the release notes and a press announcement
# '''Feb/Aug 17th:''' Create binaries/installers, pack fgdata, publish files, announce new version, close the release-branch
##Tag the release/2.6.0 branches of simgear, flightgear and fgdata and push the tags.
##:for flighgear, simgear and fgdata: ''git tag version/2.6.0-final''
##:for flighgear, simgear and fgdata: ''git push origin version/2.6.0-final''
##Merge the branch release/2.6.0 into '''master''' (<u>'''NOT'''</u> next) for flightgear and simgear and push the branch
##:We don't have a next branch for fgdata, no merging of the release branch here.
##:for flighgear and simgear:
##:''git checkout -b master origin/master'' or ''git checkout master'' if you already have the local branch
##:''git merge version/2.6.0-final
##:''git push origin master''

=== To bump up the version number ===
* fgdata
** edit the ''version'' file
* SimGear
** edit the ''version'' file
* FlightGear
** edit the ''version'' file
** <s>edit ''CMakeLists.txt''</s>
**: <s>change the line '''find_package(SimGear 2.5.0 REQUIRED)'''</s>
** <s>edit ''src/Main/options.cxx''</s>
**: <s>change the line '''static char required_version[] = "2.5.0";'''</s>
** <s>edit configure.ac</s> (Obsolete, automake is gone)
**: <s>change the line '''AC_MSG_CHECKING([for SimGear 2.5.0 or newer])'''</s>

=== Definition of Repository States ===
* Open/Green
: Normal development of the code base and fgdata. Unrestricted (well, sort of) access to the streams. This state lasts for five month after the release branches were created.
* Frozen/Yellow
*:No new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches.
*:It's a good idea for aircraft developers to adhere to this rule. However, aircraft in FGDATA may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period.
* Closed/Red
*:Nothing shall be pushed to the development streams (simgear, flightgear and fgdata). This state is for creating the release branches. It lasts for just a few hours on Jan 17th and Jul 17th around 12:00 UTC.

=== Bug fix committing policy ===
Fixes for bugs during the shakedown test of the release branch may be applied to the branches next or release/2.6.0.
A fix goes into release/2.6.0 if the development of next has moved forward and this fix does not apply there. It also goes into the release branch if there will be a better fix for next.
A fix goes into next if it is also solves an issue for the next version. Cherry-pick this commit into the release/2.6.0 branch.

'''DO NOT''' merge next into release/2.6.0 or vice versa. Most likely, there will be commits that are not welcome in or even break the other branch.

=== Bug Tracking ===
The [http://flightgear-bugs.googlecode.com bugtracker] will be our primary source for the bug fixing period. Bugs reported on the mailing list or forum will not be tracked! Reporters shall be requested to file a bug report at the bugtracker. Bugs shall be assigned a priority and a keyword to make the assignment to a developer easier. Bug reports that can't be confirmed or need more input from the reporter to get fixed will be assigned a new state "stalled" and only processed after more information has been provided. Bugs assigned a high priority will be downgraded, if no progress has been made over a certain amount of time. This is to prevent the release from being blocked by a bug that no developer is able (or willing) to fix. The only exception is "does not compile for one of the major platforms", which certainly is a release-blocker.

Bugs that were present in the latest stable release, and now considered "fixed", should be assigned a milestone label, corresponding with the upcoming stable release number. By doing so, they'll end up in [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=label%3AMilestone-2.6.0 the list of fixed bugs].

=== Legacy ===
The branch for version 2.2.0 will be left untouched. No release has ever been created from this branch.
The last official release was made from branch ''release/2.4.0'', tag ''version/2.4.0-final''.
If everything goes well, version 2.6.0 will be available around Jan, 18th 2012.

=== Tasks and Owners ===
(taskowners not yet assigned)
* Announce the state-change of the dev-streams
* Create/maintain the git branches
* Track the bugs on the tracker, trigger developers, adjust bug-priorities
* Beta testing
* Update documentation: [[FAQ]], [https://www.gitorious.org/fg/getstart/ The Manual], wiki
* Pack RC and final version of FGDATA
* Create the RC and final version (source-tarball)
* Create the RC and final version for Linux
* Create the RC and final version for Windows
* Create the RC and final version for MacOS
* Distribute files to download servers
* Make adjustments on the web-site
** Collect/make screenshots for the gallery
* Announce the new version to the public
** Write a changelog: [[Changelog 2.6.0]]
** Contact flightsim websites and send them/link them to the "press announcement"

=== Open Items, Questions ===
* Automate the creation of Windows and Mac installers
* Automate the creation of FGDATA distribution

=== Lessons Learned ===
This is a list of lessons learned from the previous release, things that turned out well and should be kept for the next release as well as thing thad didn't turn out so well and should be changed for future releases.
* Good: feature freeze in general
*: helped a lot during release management. Kept the commit traffic low and thus helped identifying those commits required to pick into the release.
* Not so good: feature freeze for aircraft
*: Technically, a feature freeze for aircraft is not necessary as long as this aircraft is not part of the base distribution and no common parts are affected. If it's guaranteed that the changes remain in FGDATA/Aircraft/MyAircraft and no other files are touched, these updates should be OK up to shortly before the release.
* Not so good: switching to a new version of supporting libraries like OSG.
*: The move to OSG 3.x introduced some major issues. If at all possible, switch to a new library early in the development cycle.
* Not so good: manual creation of release candidates and the release binaries
*: It's preferable to have equal numbers for release candidates for all O/S and probably a git-tag for each candidate.

$FG ROOT

2011-10-03T09:06:12Z

Intrepid: Edited path for Ubuntu: The path described before didn't work for me

'''$FG_ROOT''' is refered to as the main directory of [[FlightGear]], containing the so called ''base package'' ([[aircraft]], [[scenery]], [[Menubar|GUI]] files etc). When running FlightGear from a [[command line]], you can set $FG_ROOT via <tt>--fg-root=path/to/root</tt>. In [[FGRun]], it is set on the paths page, previous to the aircraft selection page.

On Mac OS X, $FG_ROOT is not installed automatically. See [[New to FlightGear#Installing on Mac OS X|New to FlightGear]] for an installation manual.

===Common paths===
* '''Mac OS X:''' <tt>Applications/FlightGear.app/Contents/Resources/data/</tt>
* '''Ubuntu:''' <tt>/usr/share/games/flightgear/</tt>
* '''Windows:''' <tt>%ProgramFiles%/FlightGear/data/</tt>

[[Category:Special directories|ROOT]]

[[nl:$FG_ROOT]]

$FG SCENERY

2011-10-03T09:05:38Z

Intrepid: Edited path for Ubuntu: The path described before didn't work for me

'''$FG_SCENERY''' is refered to as the scenery directory or directories of [[FlightGear]].

===Common paths===
* '''Mac OS X:''' <tt>Applications/FlightGear.app/Contents/Resources/data/Scenery</tt>
* '''Ubuntu:''' <tt>/usr/share/games/flightgear/Scenery</tt>
* '''Windows:''' <tt>%ProgramFiles%/FlightGear/data/Scenery</tt>

[[Category:Special directories|SCENERY]]

Howto:Multiplayer

2011-09-29T23:07:49Z

Intrepid:

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops during loading of aircraft models. Especially heavy models can cause severe lag. Therefore, it is suggested to fly in locations other than [[KSFO]], where there are fewer pilots flying around.

== Servers ==
'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you, has the lowest latency (ping time) or is the least busy.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|No
|Anders Gidenstam
|AndersG
|AndersG
|Offline from 2011-06-20 and until further notice.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, mostly short pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|No
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Yes
|Charles Ingels
|charles
|cbz-026
|
|}

Use [http://mpmap01.flightgear.org/mpstatus/ this], [http://mpmap02.flightgear.org/mpstatus/ this] or [http://flightgear.mxchange.org/mpstatus/ this] link to check if the MP servers are online. Locations of the servers are also available at [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://mpmap01.flightgear.org mpmap01] and/or [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server.

== Multiple connections per computer ==
It is possible to run multiple FlightGear instances on a single computer and connect them all to the multiplayer network. However, this requires some extras to keep in mind:
* both instances use the same out-port.
* one instance uses in port=5001, the other port 5002.
* and of course should both instances have unique callsigns.

== Using the Windows launcher / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
# On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice (check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!), enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes.
# Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

== Using fgfs from the command line ==
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

[[Category:Howto|Multiplayer]]

De/Howto: Multiplayer

2011-09-29T23:06:07Z

Intrepid:

Mit der '''multiplayer''' Funktion von [[FlightGear]] können Sie andere Piloten sehen. Das macht es möglich in Formation zu fliegen, [[Howto: Air-Air Refueling|zu Lufttankern zu verbinden]], die von echten Personen gesteuert werden, oder eine echte [[ATC|Flugsicherung]] um Start/Landefreigabe zu erbitten.

Der Multiplayermodus kann extrem hohe [[Howto: Improve Framerates|Frameraten]] verursachen, während dem Laden der Flugzeugmodellen. Gerade grosse Modelle können Stocken verursachen. Es wird empfohlen mit diesen an anderen Orten als [[KSFO]] zu fliegen, wo weniger Piloten in der Luft sind.

== Servers ==
'''Bitte beachten Sie:''' Die Multiplayerserver sind untereinander verbunden; Sie '''müssen sich nicht''' zu einem bestimmten Server verbinden, damit Sie andere Piloten sehen können, die gerade auf diesem Server spielen. Am schnellsten geht es, wenn Sie sich mit dem Server verbinden, der ihnen geographisch am nähesten liegt, der der die kleinste Ping Zeit hat, oder zu denen, die am wenigsten besetzt sind.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Standort
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracker]
! style="background:#efefef" |Verantwortlicher
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Kommentare
|-
|mpserver01.flightgear.org
|Deutschland
|Ja
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Ja
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|Vereinigtes Königreich
|Ja
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Ja
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|Nein
|Anders Gidenstam
|AndersG
|AndersG
|Offline seit 20.6.2011 bis in unbestimmte Zeit.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Ja
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Ja
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, meistens kurze Pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Ja
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Ja
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Ja
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Nein
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Ja
|Charles Ingels
|charles
|cbz-026
|
|}

Benutzen Sie [http://mpmap01.flightgear.org/mpstatus/ das hier], [http://mpmap02.flightgear.org/mpstatus/ dieses] or [http://flightgear.mxchange.org/mpstatus/ das hier] um zu überprüfen, ob die Multiplayer Server online sind. Die Standorte der Server können auch auf [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps] abgerufen werden.

Wenn Sie daran interessiert sind, einen eigenen Multiplayer Server zu hosten, könnte das hier für Sie interessant sein. [[Howto: Set up a multiplayer server|Einen Multiplayer Server aufsetzen]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Karte ===
{{Main article|MPMap}}

Es gibt eine schöne Online Karte, die die Position der Piloten, die gerade online sind, anzeigt. Die Karten sind hier zu finden: [http://mpmap01.flightgear.org mpmap01] und/oder [http://mpmap02.flightgear.org mpmap02]. Das kann auch nützlich sein, um herauszufinden, ob Sie zu einem bestimmten Server verbinden können.

== Mehrere Verbindungen pro Computer ==
Es ist möglich mehrere FlightGear Instanzen auf einem einzigen Computer auszuführen und mit all denjenigen zu einem Multiplayer Netzwerk zu verbinden.
Bei dem jedoch muss man folgendes beachten:
* Beide Instanzen benutzen denselben out Port
* Die eine Instanz benützt den in port 5001, die Andere den in Port 5002.
* Natürlich müssen beide Instanzen ein unterschiedliches Rufzeichen haben.

== Den Windows Starter benutzen / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FGRUN]]]]
# Wählen Sie ihr [[Flugzeug]] und Startflughafen wie normal in [[FlightGear Launch Control|FGRun]].
# Im nächsten Dialog, wählen Sie die "Multiplayer" Box an. Wählen Sie auch die Box "AI models" an, da Sie sonst die Flugzeuge anderer Piloten nicht sehen könnten. Geben Sie ein gewünschtes Rufzeichen ein (Bitte überprüfen Sie auf [http://fgfs.i-net.hu/modules/fgtracker/ dieser Seite] ob ihr gewünschtes Rufzeichen bereits in Verwendung ist oder nicht. Nehmen Sie kein Rufzeichen, das bereits verwendet wird!), geben Sie mpserver01.flightgear.org im Feld "Hostname" an, und 5000 in die Felder "in" und "out".
# Nach einem Klick auf "Run" werden Sie mit anderen Piloten fliegen können.

Um zu bestätigen dass es funktioniert, können Sie zur Multiplayer Karte gehen: http://mpmap02.flightgear.org/ (in Hong Kong).
Wenn FlightGear einmal gestartet ist, werden Sie Chatnachrichten bemerken, die alle "Hello" sagen, mit den dazugehörigen Namen der Piloten, die gerade online sind und eben dem Server beigetreten sind.
(Sie können diese Nachricht verändern, indem Sie die die Zeile <tt><chat type="string">Hello</chat></tt> in <tt>[[$FG ROOT]]/preferences.xml</tt>) enstprechend anpassen. Vielleicht möchten Sie ja auch einen anderen Server benutzen.

Für weitere Einstellungen, kann der <tt>Advanced > Network</tt> Tab geöffnet werden. Nur dort können Sie z. B. die in oder out lines entfernen.

== Die Benutzung von fgfs aus der Kommandozeile ==
Erstens: Für alle, die sehr ungeduldig sind, und einigermassen eine Idee haben, was sie gerade tun, sind die Standardargumente, die fgfs übergeben werden müssen, folgende:

--multiplay=out,10,server.ip.Adresse,5000
--callsign=rufzeichen

Hier ist 5000 der Port, auf dem der Server eingehende Verbindungen akzeptiert. (Wobei 5000 die Portnummer der offiziellen Server ist)

Wenn Sie aus irgendeinem Grund einen anderen Port oder ein anderes Interface benutzen müssen, so sollten Sie folgende Argumente mitübergeben:

--multiplay=in,10,Ihre.ip.Adresse,Portnummer

Wobei "Portnummer" in der Regel 5000 ist, und Ihre.ip.Adresse die IP Adresse ihrer Netzwerkschnittstelle ist, die von FG benutzt werden soll, um zum Server verbinden. Auch wenn das eine lokal 192.168. Adresse ist.
Sie können das Feld Ihre.ip.Adresse auch leer lassen. FG wird dann auf allen verfügbaren Schnittstellen Verbindungen akzeptieren.
--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]
[[de:Howto: Multiplayer]]

[[Category:Howto|Multiplayer]]

De/Howto: Multiplayer

2011-09-29T22:53:49Z

Intrepid:

Mit der '''multiplayer''' Funktion von [[FlightGear]] können Sie andere Piloten sehen. Das macht es möglich in Formation zu fliegen, [[Howto: Air-Air Refueling|zu Lufttankern zu verbinden]], die von echten Personen gesteuert werden, oder eine echte [[ATC|Flugsicherung]] um Start/Landefreigabe zu erbitten.

Der Multiplayermodus kann extrem hohe [[Howto: Improve Framerates|Frameraten]] verursachen, während dem Laden der Flugzeugmodellen. Gerade grosse Modelle können Stocken verursachen. Es wird empfohlen mit diesen an anderen Orten als [[KSFO]] zu fliegen, wo weniger Piloten in der Luft sind.

== Servers ==
'''Bitte beachten Sie:''' Die Multiplayerserver sind untereinander verbunden; Sie '''müssen sich nicht''' zu einem bestimmten Server verbinden, damit Sie andere Piloten sehen können, die gerade auf diesem Server spielen. Am schnellsten geht es, wenn Sie sich mit dem Server verbinden, der ihnen geographisch am nähesten liegt, der der die kleinste Ping Zeit hat, oder zu denen, die am wenigsten besetzt sind.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Standort
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracker]
! style="background:#efefef" |Verantwortlicher
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Kommentare
|-
|mpserver01.flightgear.org
|Deutschland
|Ja
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Ja
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|Vereinigtes Königreich
|Ja
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Ja
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|Nein
|Anders Gidenstam
|AndersG
|AndersG
|Offline seit 20.6.2011 bis in unbestimmte Zeit.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Ja
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Ja
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, meistens kurze Pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Ja
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Ja
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Ja
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Nein
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Ja
|Charles Ingels
|charles
|cbz-026
|
|}

Benutzen Sie [http://mpmap01.flightgear.org/mpstatus/ das hier], [http://mpmap02.flightgear.org/mpstatus/ dieses] or [http://flightgear.mxchange.org/mpstatus/ das hier] um zu überprüfen, ob die Multiplayer Server online sind. Die Standorte der Server können auch auf [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps] abgerufen werden.

Wenn Sie daran interessiert sind, einen eigenen Multiplayer Server zu hosten, könnte das hier für Sie interessant sein. [[Howto: Set up a multiplayer server|Einen Multiplayer Server aufsetzen]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Karte ===
{{Main article|MPMap}}

Es gibt eine schöne Online Karte, die die Position der Piloten, die gerade online sind, anzeigt. Die Karten sind hier zu finden: [http://mpmap01.flightgear.org mpmap01] und/oder [http://mpmap02.flightgear.org mpmap02]. Das kann auch nützlich sein, um herauszufinden, ob Sie zu einem bestimmten Server verbinden können.

== Mehrere Verbindungen pro Computer ==
Es ist möglich mehrere FlightGear Instanzen auf einem einzigen Computer auszuführen und mit all denjenigen zu einem Multiplayer Netzwerk zu verbinden.
Bei dem jedoch muss man folgendes beachten:
* Beide Instanzen benutzen denselben out Port
* Die eine Instanz benützt den in port 5001, die Andere den in Port 5002.
* Natürlich müssen beide Instanzen ein unterschiedliches Rufzeichen haben.

== Den Windows Starter benutzen / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FGRUN]]]]
# Wählen Sie ihr [[Flugzeug]] und Startflughafen wie normal in [[FlightGear Launch Control|FGRun]].
# Im nächsten Dialog, wählen Sie die "Multiplayer" Box an. Wählen Sie auch die Box "AI models" an, da Sie sonst die Flugzeuge anderer Piloten nicht sehen könnten. Geben Sie ein gewünschtes Rufzeichen ein (Bitte überprüfen Sie auf [http://fgfs.i-net.hu/modules/fgtracker/ dieser Seite] ob ihr gewünschtes Rufzeichen bereits in Verwendung ist oder nicht. Nehmen Sie kein Rufzeichen, das bereits verwendet wird!), geben Sie mpserver01.flightgear.org im Feld "Hostname" an, und 5000 in die Felder "in" und "out".
# Nach einem Klick auf "Run" werden Sie mit anderen Piloten fliegen können.

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

== Using fgfs from the command line ==
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

[[Category:Howto|Multiplayer]]

De/Howto: Multiplayer

2011-09-29T22:47:19Z

Intrepid: Created page with "Mit der '''multiplayer''' Funktion von FlightGear können Sie andere Piloten sehen. Das macht es möglich in Formation zu fliegen, [[Howto: Air-Air Refueling|zu Lufttankern z..."

Mit der '''multiplayer''' Funktion von [[FlightGear]] können Sie andere Piloten sehen. Das macht es möglich in Formation zu fliegen, [[Howto: Air-Air Refueling|zu Lufttankern zu verbinden]], die von echten Personen gesteuert werden, oder eine echte [[ATC|Flugsicherung]] um Start/Landefreigabe zu erbitten.

Der Multiplayermodus kann extrem hohe [[Howto: Improve Framerates|Frameraten]] verursachen, während dem Laden der Flugzeugmodellen. Gerade grosse Modelle können Stocken verursachen. Es wird empfohlen mit diesen an anderen Orten als [[KSFO]] zu fliegen, wo weniger Piloten in der Luft sind.

== Servers ==
'''Bitte beachten Sie:''' Die Multiplayerserver sind untereinander verbunden; Sie '''müssen sich nicht''' zu einem bestimmten Server verbinden, damit Sie andere Piloten sehen können, die gerade auf diesem Server spielen. Am schnellsten geht es, wenn Sie sich mit dem Server verbinden, der ihnen geographisch am nähesten liegt, der der die kleinste Ping Zeit hat, oder zu denen, die am wenigsten besetzt sind.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Standort
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracker]
! style="background:#efefef" |Verantwortlicher
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Kommentare
|-
|mpserver01.flightgear.org
|Deutschland
|Ja
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Ja
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|Vereinigtes Königreich
|Ja
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Ja
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Göteborg, Sweden
|Nein
|Anders Gidenstam
|AndersG
|AndersG
|Offline seit 20.6.2011 bis in unbestimmte Zeit.
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Ja
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Ja
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, meistens kurze Pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Ja
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Ja
|[mailto:admin@mpserver10.flightgear.org Alexis Bory]
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Ja
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|Nein
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Ja
|Charles Ingels
|charles
|cbz-026
|
|}

Benutzen Sie [http://mpmap01.flightgear.org/mpstatus/ das hier], [http://mpmap02.flightgear.org/mpstatus/ dieses] or [http://flightgear.mxchange.org/mpstatus/ das hier] um zu überprüfen, ob die Multiplayer Server online sind. Die Standorte der Server können auch auf [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps] abgerufen werden.

Wenn Sie daran interessiert sind, einen eigenen Multiplayer Server zu hosten, könnte das hier für Sie interessant sein. [[Howto: Set up a multiplayer server|Einen Multiplayer Server aufsetzen]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Karte ===
{{Main article|MPMap}}

Es gibt eine schöne Online Karte, die die Position der Piloten, die gerade online sind, anzeigt. Die Karten sind hier zu finden: [http://mpmap01.flightgear.org mpmap01] und/oder [http://mpmap02.flightgear.org mpmap02]. Das kann auch nützlich sein, um herauszufinden, ob Sie zu einem bestimmten Server verbinden können.

== Mehrere Verbindungen pro Computer ==
Es ist möglich mehrere FlightGear Instanzen auf einem einzigen Computer auszuführen und mit all denjenigen zu einem Multiplayer Netzwerk zu verbinden.
Bei dem jedoch muss man folgendes beachten:
* Beide Instanzen benutzen denselben out Port
* Die eine Instanz benützt den in port 5001, die Andere den in Port 5002.
* Natürlich müssen beide Instanzen ein unterschiedliches Rufzeichen haben.

== Den Windows Starter benutzen / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|Der Flightgear Starter FGRUN]]]]
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
# On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft. Enter the callsign of your choice (check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!), enter mpserver01.flightgear.org in the "Hostname" box and 5000 into both the "in" and "out" boxes.
# Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

== Using fgfs from the command line ==
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

[[Category:Howto|Multiplayer]]

De/Hauptseite

2011-09-29T22:25:28Z

Intrepid:

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Willkommen im FlightGear Wiki!</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">wir haben zur Zeit [[Special:Statistics|{{NUMBEROFARTICLES}}]] Artikel</div>

[[File:de.gif|link=:de:Hauptseite]]
[[File:en.gif|link=:en:Main Page]]
[[File:es.gif|link=:es:Portada]]
[[File:fi.gif|link=:fi:Etusivu]]
[[File:fr.gif|link=:fr:Accueil]]
[[File:nl.gif|link=:nl:Hoofdpagina]]
[[File:pl.gif|link=:pl:Strona główna]]
[[File:pt.gif|link=:pt:Página principal]]
[[File:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[:de:Help:Tutorial|Hilfe zum Bearbeiten]]''' •''' [[:de:Help:Inhalt|Hilfe]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|Alle Seiten]]'''•''' [[Special:Search|Suchen]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[File:FGlogo.jpg|left]] '''[[:de:FlightGear|FlightGear]] Flight Simulator''' ist ein ausgereifter, anspruchsvoller, quelloffener Flugsimulator, welcher ausschliesslich von Ehrenamtlichen gestaltet, programmiert und weiterentwickelt wird. Die Quellen sind unter der [[GNU General Public License]] veröffentlicht und per [http://www.flightgear.org/cvs/anoncvs.html CVS] für jedermann zugänglich. Die jüngste stabile Version ist FlightGear 2.4.0, sie wurde am 18. August 2011 vom Stapel gelassen.

Ziele des [[:de:FlightGear|FlightGear]] Projektes sind die Entwicklung einer Grundstruktur für Forschung und Ausbildung im avionischen Bereich, die Erschaffung einer Basis zur Entwicklung weiterer/angepasster Simulatoren und natürlich die Bereitstellung eines Simulators für den Endanwender. FlightGear kann von [[Volunteer|jederman]] weiterentwickelt und angepasst werden. Eine Übersicht über Werkzeuge zur Entwicklung und Projekte auf welchen FlightGear aufbaut zeigt die [[FlightGear related projects|related projects]]-Seite sowie die [http://www.flightgear.org/links.html Links der Hauptseite].

FlightGear kommt mit einem Satz erläuternden Unterlagen, vornehmlich "Das Manual", das als [http://www.emmerich-j.de/FGFS/Getstart-DE/getstart-de.pdf PDF (de)] bzw. [http://mapserver.flightgear.org/getstart.pdf PDF (original en)] und [http://www.emmerich-j.de/FGFS/Getstart-DE/getstart-de.html HTML (de)] bzw. [http://www.flightgear.org/Docs/getstart/getstart.html HTML (original en)] vorhanden ist.

'''Wählen Sie bitte ein (Sub)Portal:'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Portal:Developer|Entwickler]]
** [[Portal:Developer/3D Modelers|3D Entwickler]]
** [[Portal:Developer/Aircraft|Flugzeuge]]
** [[Portal:Developer/Scenery|Landschaft]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[:de:Portal:Benutzer|Benutzer]]
* [[:de:Portal:Pilot|Piloten]]
|}

===== '''Angehende Wiki-Autoren sollten unbedingt einen Blick ins [[:de:Help:Inhalt|Handbuch]] werfen bevor sie Artikel bearbeiten oder erstellen.''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Erste Schritte</h2>
|-
|style="color:#000;"|
* [[:de:FAQ|FAQ]]
* [[Howto: Get rid of common errors|Allgemeine Fehler beheben]]
* [[Howto: Multiplayer|Multiplayer]]
* [[:de:Neu bei Flightgear|Neu bei Flightgear]]
* [[Troubleshooting Problems|Probleme mit Flightgear]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear benutzen</h2>
|-
|style="color:#000;"|
* [[:de:Flugzeuge|Flugzeuge]]
* [[:de:Fliegen mit dem Helikopter|Fliegen mit dem Helikopter]]
* [[:de:Liste der Modelle|Liste der Modelle]]
'''[[Portal:User|Mehr dazu...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Entwickler</h2>
|-
|style="color:#000;"|
* [[Building FlightGear|FlightGear kompilieren ]]
* [[Building terragear-cs in Ubuntu 64|Terragear-cs in Ubuntu 64Bit kompilieren]]
* [[FlightGear Package Manager|FlightGear Paket Manager]]
'''[[Portal:Developer|Mehr dazu...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nachrichten</h2>
|-
|style="color:#000;"|
{{News}}
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Abbildung der Woche </h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Wussten Sie...</h2>
|-
|style="color:#000;"|
{{Did you know}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Förderung</h2>
|-
|style="color:#000;"|
* [[FlightGear Reviews]]
* [[FlightGear Videos]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[en:Main Page]]
[[es:Portada]]
[[fi:Etusivu]]
[[fr:Accueil]]
[[nl:Hoofdpagina]]
[[pt:Página principal]]

De/Hauptseite

2011-09-29T22:23:46Z

Intrepid:

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Willkommen im FlightGear Wiki!</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">wir haben zur Zeit [[Special:Statistics|{{NUMBEROFARTICLES}}]] Artikel</div>

[[File:de.gif|link=:de:Hauptseite]]
[[File:en.gif|link=:en:Main Page]]
[[File:es.gif|link=:es:Portada]]
[[File:fi.gif|link=:fi:Etusivu]]
[[File:fr.gif|link=:fr:Accueil]]
[[File:nl.gif|link=:nl:Hoofdpagina]]
[[File:pl.gif|link=:pl:Strona główna]]
[[File:pt.gif|link=:pt:Página principal]]
[[File:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[:de:Help:Tutorial|Hilfe zum Bearbeiten]]''' •''' [[:de:Help:Inhalt|Hilfe]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|Alle Seiten]]'''•''' [[Special:Search|Suchen]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[File:FGlogo.jpg|left]] '''[[:de:FlightGear|FlightGear]] Flight Simulator''' ist ein ausgereifter, anspruchsvoller, quelloffener Flugsimulator, welcher ausschliesslich von Ehrenamtlichen gestaltet, programmiert und weiterentwickelt wird. Die Quellen sind unter der [[GNU General Public License]] veröffentlicht und per [http://www.flightgear.org/cvs/anoncvs.html CVS] für jedermann zugänglich. Die jüngste stabile Version ist FlightGear 2.4.0, sie wurde am 18. August 2011 vom Stapel gelassen.

Ziele des [[:de:FlightGear|FlightGear]] Projektes sind die Entwicklung einer Grundstruktur für Forschung und Ausbildung im avionischen Bereich, die Erschaffung einer Basis zur Entwicklung weiterer/angepasster Simulatoren und natürlich die Bereitstellung eines Simulators für den Endanwender. FlightGear kann von [[Volunteer|jederman]] weiterentwickelt und angepasst werden. Eine Übersicht über Werkzeuge zur Entwicklung und Projekte auf welchen FlightGear aufbaut zeigt die [[FlightGear related projects|related projects]]-Seite sowie die [http://www.flightgear.org/links.html Links der Hauptseite].

FlightGear kommt mit einem Satz erläuternden Unterlagen, vornehmlich "Das Manual", das als [http://www.emmerich-j.de/FGFS/Getstart-DE/getstart-de.pdf PDF (de)] bzw. [http://mapserver.flightgear.org/getstart.pdf PDF (original en)] und [http://www.emmerich-j.de/FGFS/Getstart-DE/getstart-de.html HTML (de)] bzw. [http://www.flightgear.org/Docs/getstart/getstart.html HTML (original en)] vorhanden ist.

'''Wählen Sie bitte ein (Sub)Portal:'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Portal:Developer|Entwickler]]
** [[Portal:Developer/3D Modelers|3D Entwickler]]
** [[Portal:Developer/Aircraft|Flugzeuge]]
** [[Portal:Developer/Scenery|Landschaft]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[:de:Portal:Benutzer|Benutzer]]
* [[:de:Portal:Pilot|Piloten]]
|}

===== '''Angehende Wiki-Autoren sollten unbedingt einen Blick ins [[:de:Help:Inhalt|Handbuch]] werfen bevor sie Artikel bearbeiten oder erstellen.''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Erste Schritte</h2>
|-
|style="color:#000;"|
* [[:de:FAQ|FAQ]]
* [[Howto: Get rid of common errors|Allgemeine Fehler beheben]]
* [[Howto: Multiplayer|Multiplayer]]
* [[:de:Neu bei Flightgear|Neu bei Flightgear]]
* [[Troubleshooting Problems|Probleme mit Flightgear]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear benutzen</h2>
|-
|style="color:#000;"|
* [[:de:Flugzeuge|Flugzeuge]]
* [[:de:Fliegen mit dem Helikopter|Fliegen mit dem Helikopter]]
* [[:de:Liste der Modelle|Liste der Modelle]]
'''[[Portal:User|Mehr dazu...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Entwickler</h2>
|-
|style="color:#000;"|
* [[Building FlightGear]]
* [[Building terragear-cs in Ubuntu 64|Building Terragear in Ubuntu]]
* [[FlightGear Package Manager]]
'''[[Portal:Developer|Mehr dazu...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nachrichten</h2>
|-
|style="color:#000;"|
{{News}}
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Abbildung der Woche </h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Wussten Sie...</h2>
|-
|style="color:#000;"|
{{Did you know}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Förderung</h2>
|-
|style="color:#000;"|
* [[FlightGear Reviews]]
* [[FlightGear Videos]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[en:Main Page]]
[[es:Portada]]
[[fi:Etusivu]]
[[fr:Accueil]]
[[nl:Hoofdpagina]]
[[pt:Página principal]]