Fr/FGCom: Difference between revisions

# Commencez par '''choisir un avion'''. Pour ce premier essai, nous suggérons le [[Cessna C172]]P, ainsi, nous comprendrons la suite. Considérez aussi que certains dessineurs d' avions réattribuant  des touches de clavier (p.ex. la barre d'espace”), ainsi, vous pouvez ne pas avoir la touche PTT (“Push To Talk”- Appuyez pour parler-) disponible. Voir[[FGCOM#Trucs et Astuces]].<br />→ Click "Next".

# Comme '''lieu de départ,''' précisez [[airport]] KPAO (Palo Alto) piste 13, ainsi, nous verrons tous les mêmes messages dans les rapports suivants. Une autre raison pour KPAO est que KPAO a les scènes de base par défaut, et donc est valable pour tout le monde. <br />→ Click "Next".[[File:FGrun_base.jpg|thumb|Basic & multiplayer options]]

#* “AI models” doit être activé afin de voir tout le trafic

#*tapez “'''mpserverXX.flightgear.org'''” dans le champ “Hostname:”, remplacez “XX” avec le numéro de serveur le plus proche de vouswit - selectionnez le dans http://pigeond.net/flightgear/mpstatus/. En fait, pas besoin de choisir (as long as it is online and pas aussi encombré que mpserver02) - you might try which server gives you the best response-times.  

#* Insert your “Callsign:” (max. 7 characters)

#* define the “in” and “out” ports both with the standard “5000”

#* With "Load/Save as" you may build up yourself a library of settings for different airports.<br />→ Click "Advanced".[[File:FGrun_IP.jpg|thumb|Advanced: Initial Position]]

# In the “'''Advanced Options'''” check the following sections (click/select them in the left column):

#* General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).

#* Features: “AI Traffic” should be activated already

#* Initial Position: You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''

#** ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.[[File:MPmap.jpg|thumb|[[MPMap]]]]

# Open the '''[http://mpmap01.flightgear.org MPMap]'''

#* if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”

#* click on “nav”

#* disable all options except “apt code”

#* type “KPAO” into the filed “Navaids lookup”

#* hit ENTER or click onto the reading-glass symbol

#* click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”

#* now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”

#* then zoom into the airport

#* set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen

#* type those long/lat values into the field below and also the wanted heading of the plane while parking[[File:FGrun_net.jpg|thumb|Advanced: Network]]

# '''Network:''' Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.

#* WARNING: When saving these settings and reloading them again, FGRun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".

#* If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type