Forum Flightgear France

Une communauté prend son envol

Vous n'êtes pas identifié(e).

Annonce

Futur nouvel inscrit, tu dois au préalable lire l'intégralité des 10 articles des règles, s'il te plaît. Tout nouveau compte qui ne respecte pas les règles sera supprimé par l'administration.

#1 17/09/2017 21:27:43

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

[RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Re-Bonjour

Je serais très intéressé pour envoyer la position GPS (NMEA) sur le port bluetooth de mon PC pour récupérer cette position sur une tablette Android. Sur le forum anglophone j'ai trouvé quelques post associés à la même fonctionnalité et besoin sur MAC mais rien sur PC; y aurait-il un utilisateur qui ait déjà monté cette capacité au travers de paramètres à coller au lancement de FG (fgfs + paramètres) pour l’émission de la position avion au format MNEA sur le port Bluetooth du PC ?

Merci d'avance.

Dernière modification par tcx32fr (7/10/2017 7:28:41)


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#2 17/09/2017 23:45:16

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour et bienvenue!
Dis nous ce que tu as trouvé, peut-être on peut "creuser" wink

Tu cherches quelque chose dans ce sens?:
http://equipe-flightgear.forumactif.com … -bluetooth
http://wiki.flightgear.org/Air_Navigation_(Software)


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#3 18/09/2017 14:27:51

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour,

oui exactement, j'ai un copain pilote qui utilise ça sur MAC:
"tu fais démarrer Flight Gear avec "--nmea=file,out,5,/dev/cu.Bluetooth-Incoming-Port" dans les options de démarrage.
/dev/cu.Bluetooth-Incoming-Port est le port BT sur Mac, faut trouver l'équivalent sur PC en fonction de ton hardware, mais ça doit se faire".

Mais n'étant pas un expert du monde Windows je n'ai pas trop d'idée de la chaine de caractère qui fonctionnerait pour remplacer /dev/cu.Bluetooth-Incoming-Port.

La seule chose que je sais est que lorsque je vais dans le gestionnaire de périphériques de WIN7, je vois que le port comm 8 est attribué au Bluetooth

Merci


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#4 18/09/2017 17:16:21

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Je ne suis pas spécialiste, mais...
Dans la doc:
https://sourceforge.net/p/flightgear/fg … /README.IO
on trouve:

Serial Port Communication:

    --nmea=serial,dir,hz,device,baud

    device = OS device name of serial line to be open()'ed
    baud = {300, 1200, 2400, ..., 230400}

    example to pretend we are a real gps and output to a moving map application:

    --nmea=serial,out,0.5,COM1,4800

donc par déduction si tu es sûr de ton port com:
--nmea=serial,out,0.5,COM8,4800
devrait "envoyer" quelque chose...
"fréquence" (0.5) et "baudrate" (4800) à tester


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#5 19/09/2017 4:37:25

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir
Je regarde ça dans deux jours n'étant pas chez moi et vous tiens au courant
Merci


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#6 20/09/2017 23:56:19

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir

J'ai donc ce soir essayé de lancer FG avec les paramètres indiqués, et COM8 vu que j'ai "paramètres BlueTooth, Ports COM, COM8 Entrant
et j'ai modifié la cible du raccourci : "D:\Program Files\FlightGear 2017.2.1\bin\fgfs.exe" --launcher  --nmea=serial,out,5,COM8,4800  -->

FG se lance mais reste bloqué sur "finalisation de la position" sur l'écran d'accueil, il faut que je tue l'appli via le gestionnaire de taches.

Si je retire le paramètre supp et ne laisse que le --launcher, pas de pb

Si vous avez une idée ...

Merci


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#7 20/09/2017 23:59:53

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Nb: y a-t-il un log qui permettrait de voir ce qui se passe ?


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#8 21/09/2017 8:21:29

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

tcx32fr a écrit :

Nb: y a-t-il un log qui permettrait de voir ce qui se passe ?

Sauf erreur sous win le log se trouve dans: C:\Users\<user>\AppData\Roaming\flightgear.org
On y trouve le log actuel "fgfs.log" + celui de la séance précédente "fgfs_0.log"

Si je comprends bien com8 est un port "entrant", ne devrais-tu pas paramétrer un port "sortant"?

https://www.youtube.com/watch?v=Fg1dDEjk9UA

Le "baudrate" du protocole fg doit correspondre à celui du port com

PS: j'ai lancé fg ici (sous linux) avec --nmea,serial,out,5,COM8,4800, le log:

io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:92:Parse I/O channel request: nmea,serial,out,5,COM8,4800
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:103:  protocol = nmea
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:252:  medium = serial
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:256:  direction = out
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:261:  hertz = 5
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:271:  device = COM8
io:3:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:275:  baud = 4800
io:5:/home/tt/fg-s/simgear/simgear/serial/serial.cxx:104:Cannot open COM8 for serial I/O
io:5:/home/tt/fg-s/simgear/simgear/io/sg_serial.cxx:56:Error opening device: COM8
io:5:/home/tt/fg-s/flightgear/src/Network/nmea.cxx:498:Error opening channel communication layer.
io:5:/home/tt/fg-s/flightgear/src/Main/fg_io.cxx:370:I/O Channel config failed.

Et en console:

Cannot open COM8 for serial I/O
Error opening device: COM8
Error opening channel communication layer.
I/O Channel config failed.

il semblerait que du côté fg ça fonctionne, mais comme il ne trouve pas com8...
Je vais voir si je peux emuler un port com

Dernière modification par ctesc356 (21/09/2017 9:04:35)


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#9 21/09/2017 11:17:46

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour

Merci pour les infos - je regarde ce soir.
En ce qui concerne la création d'un port sortant j'ai essayé mais l'interface Windows ne me permet pas de sélectionner un n° de port, la liste déroulante est vide.
Mais je ne crois pas que ce soit nécessaire: en utilisant "Navigation" de FouFou + dans les paramètres BT (clic droit sur l'icone de la barre sur PC), on fait "Ajouter" et il a défini un port entrant "Tab S2 TCx" (le nom de mon Smartphone) en COM5.
Dans Navigation>Options>GPS, j'ai coché "copier NMEA sur", COM5, 4800 bauds, j'ai chargé une route et j'ai lancé le mode simulation et c'est bien reçu sur la tablette et donc à travers d'un port entrant

Merci


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#10 21/09/2017 21:37:46

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir

Ci joint des éléments du Log

io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:103:  protocol = nmea
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:252:  medium = serial
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:256:  direction = out
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:261:  hertz = 5
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:271:  device = COM8
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:275:  baud = 4800
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:133:Looking for bindings for joystick "Logitech Extreme 3D"

et à priori pas de messages d'erreur I/O, et la dernière ligne affichée est:

view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position

et l'écran reste figé sur "Finalisation de la position"

Comment lance-t-on le mode console sur Windows ?

Je peux joindre le log mais je ne comprends pas comment joindre un fichier ... roll

Merci


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#11 21/09/2017 23:18:31

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Comment lance-t-on le mode console sur Windows ?

essaie de lancer avec --console
tu peux mettre les options de ligne de commande dans "Settings >Additional options" du lanceur.
voir aussi: http://wiki.flightgear.org/Howto:Showin … on_Windows

bizarre apparemment c'est pas --nmea... qui le fait tousser??

Pour joindre un fichier volumineux, le mieux est de le charger sur Pastebin ou autre et de mettre le lien ici.


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#12 21/09/2017 23:23:07

f-toro
Administrateur
Lieu : LFLA
Inscription : 16/12/2007
Messages : 2 202

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

tcx32fr a écrit :

je ne comprends pas comment joindre un fichier ... roll

Joindre un fichier, à un message ?

On ne peut pas, le forum n'est pas comme un mail où on peut mettre une pièce jointe.

Il faut passer par un hébergeur et mettre le lien dans son message.
Par exemple Pastebin comme te le suggère ctesc356.

tcx32fr a écrit :

Je peux joindre le log...

C'est très bien mais il vaut mieux le mettre entre les balises code, comme l'a fait ctesc356 trois messages plus haut.
Ceci pour une meilleure lisibilité.
Et aussi parce que certains logs sont très longs.
Les balises n’afficheront qu'un nombre limité de lignes et il y aura un ascenseur pour visualiser les autres.
Je l'ai fait pour toi.
Si tu veux savoir comment ça marche, édite ton message et tu verras comment sont positionnées les balises.


André. anciennement taureau89_9
Debian Testing Amd64. CM Sabertooth 990FX, FX8350, 32 Go Ram DDR3 1866 Mhz, GTX 750ti 2Go, DD 2To Sata 3, THRUSTMASTER T.Flight StickX, FG 2017.4.0 Git.

Hors ligne

#13 21/09/2017 23:36:19

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

C'est bon j'ai trouvé: j'ai mis le set de paramètres  --nmea,serial,out,1,COM8,4800 non pas en rajout dans le raccourci Windows mais dans la page d'accueil, "settings", "additional settings" et ça marche tip top.

Bon je vais me coucher car du coup ça m'a pris des heures de sommeil dernièrement, j'aurai une question sur les touch&go qui me semblent couper le moteur mais c'est pour plus tard smile


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#14 22/09/2017 23:45:32

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir

Je ne sais pas s'il faut que j'ouvre une nouvelle discussion mais malgré le fait qu'hier soir tout marchait impeccable, ce soir j'ai le même comportement d'arrêt de l'initialisation au message "Finalisation de la position", avec les paramètres NMEA settés dans le menu "settings". Si je les retire, l'initialisation se fait correctement. Sur le log, la dernière ligne enregistrée est toujours la même.

Pb connu ? sinon je peux aller faire un tour sur le forum en anglais.

Merci

NB: sur le pb de l’émission BT sur Windows, on peut considérer que le sujet est résolu, j'imagine que c'est f-toro d'Auxerre qui passe le titre en statut "résolu" ?


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#15 23/09/2017 8:29:00

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour,
bizarre en effet. Non ce n'est pas un problème connu, en général quand ça marche, ça marche smile

Essaie de supprimer "autosave_**.xml" et "navdata_**.cache" dans C:\Users\<user>\AppData\Roaming\flightgear.org si de fois il y aurait un paramétrage "contrariant"

Eventuellement comparer les logs avec et sans . Juste la dernière ligne ne signifie pas grand chose.

Dernière modification par ctesc356 (23/09/2017 8:41:21)


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#16 23/09/2017 12:46:10

dany93
Administrateur
Lieu : Région Parisienne
Inscription : 5/07/2009
Messages : 2 611

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

tcx32fr a écrit :

NB: sur le pb de l’émission BT sur Windows, on peut considérer que le sujet est résolu, j'imagine que c'est f-toro d'Auxerre qui passe le titre en statut "résolu" ?

Bonjour tcx32fr,

(je ne vois pas de quel problème tu parles mais peu importe)
Non, c'est toi, tu le passes en [RESOLU] quand tu estimes que c'est bon. Aucun risque, il reste ouvert. C'est simplement plus informatif pour ceux qui cherchent en ne voyant que les titres.

Tu fais comme si tu voulais modifier ton premier message ("Modifier"), tu as alors accès au titre.
Tu ajoutes alors [RESOLU] en début, éventuellement en le raccourcissant un peu si "ça dépasse". big_smile
Exemple : [RESOLU] emission position GPS (NMEA) avion sur port Bluetooth du PC


FG 2017.4.0, Linux Mint 18 (64b), Quad Q6600 (2.4 GHz), RAM 4Go DDR2, GEFORCE GTX 650 1GB, OSG 3.4.0
Boeing 787-8 (YASim, avec nickyivyca, aco)
DR400 JSBSim (PAF)
DC3 JSBSim (PAF)

Hors ligne

#17 23/09/2017 13:46:15

f-toro
Administrateur
Lieu : LFLA
Inscription : 16/12/2007
Messages : 2 202

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

tcx32fr a écrit :

j'imagine que c'est f-toro d'Auxerre qui passe le titre en statut "résolu" ?

lol lol

C'était dans les règles... roll


André. anciennement taureau89_9
Debian Testing Amd64. CM Sabertooth 990FX, FX8350, 32 Go Ram DDR3 1866 Mhz, GTX 750ti 2Go, DD 2To Sata 3, THRUSTMASTER T.Flight StickX, FG 2017.4.0 Git.

Hors ligne

#18 23/09/2017 21:54:02

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir

@ f-toto: désolé pour les règles...
@ dany93: Ok c'était pas très clair mon post en effet, c'était pas un problème mais une question qui a trouvé une réponse positive puisque j'ai réussi à émettre la position A/C sur BT... au moins un soir
@ctesc356: j'ai fait ce que tu proposais, même comportement: ça reste bloqué sur "initialisation de la position"

Ci joint le log d'init, et plus bas le log sans NMEA où ça fonctionne, et merci pour tout conseil car c'est un peu bizarre d'avoir réussi et que maintenant ça bugge ...:

general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:424:Created multi-app mutex, we are in writeable mode
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:443:CrashRpt enabled
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:470:FlightGear:  Version 2017.2.1
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:471:FlightGear:  Build Type Release
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:472:Built with Microsoft Visual C++ version 1900
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:474:Jenkins number/ID 219:219
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2832:platform default fg_root = Path "../data"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:505:Reading global defaults
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:515:Finished Reading global defaults
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:261:NavCache at:Path "C:/Users/C&T/AppData/Roaming/flightgear.org/navdata_2017_2.cache"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:264:NavCache read-only flags is:0
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:297:will create tables
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1545:readStringProperty: unknown:apt.dat files
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1128:NavCache: rebuild required for apt.dat files (no file in cache, but 1 such file found in scenery paths)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1343:NavCache: main cache rebuild required
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:261:NavCache at:Path "C:/Users/C&T/AppData/Roaming/flightgear.org/navdata_2017_2.cache"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:264:NavCache read-only flags is:0
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:297:will create tables
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1401:Loading apt.dat file: 'D:/Program Files/FlightGear 2017.2.1/data/Airports/apt.dat.gz'
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\apt_loader.cxx:137:apt.dat format version (D:/Program Files/FlightGear 2017.2.1/data/Airports/apt.dat.gz): 1000
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1412:apt.dat files load took: 3384
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\apt_loader.cxx:297:Loaded data for 34074 airports
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1445:processing airports took:10660
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1401:Loading fix.dat file: 'D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz'
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:18393: skipping fix CANIS (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:27229: skipping fix DF162 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:28227: skipping fix DITRE (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:28794: skipping fix DM072 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:28801: skipping fix DM078 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:28806: skipping fix DM082 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:34052: skipping fix ENETA (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:58351: skipping fix KESIX (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:62530: skipping fix LANZA (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:65499: skipping fix LOPNA (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:69430: skipping fix MENDI (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:82429: skipping fix PAS21 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:102812: skipping fix TEXIT (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\fixlist.cxx:139:D:/Program Files/FlightGear 2017.2.1/data/Navaids/fix.dat.gz:114683: skipping fix WW022 (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1412:fix.dat files load took: 3258
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1401:Loading nav.dat file: 'D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz'
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:102: skipping navaid 'AKRON NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:157: skipping navaid 'ALGOA NDB' (nearby suspected duplicate 'ALGOA (LOM/NDB) NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:356: skipping navaid 'ASHLY NDB' (nearby suspected duplicate 'ASHLY (LOM/NDB) NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:606: skipping navaid 'BEDDS NDB' (nearby suspected duplicate 'BEDDS (LOM) NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:607: skipping navaid 'BEDDS NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:608: skipping navaid 'BEDDS NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:783: skipping navaid 'BOLLN NDB' (nearby suspected duplicate 'BOLLN LOM')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:791: skipping navaid 'BOMDE NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:802: skipping navaid 'BOOIE NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:840: skipping navaid 'BOUTN NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:989: skipping navaid 'BUSHE NDB' (nearby suspected duplicate 'BUSHE (LOM) NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:990: skipping navaid 'BUSHE NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:1779: skipping navaid 'DUSTT NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:1780: skipping navaid 'DUSTT NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:2126: skipping navaid 'FUROR NDB' (nearby suspected duplicate 'Furor LOM')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:2542: skipping navaid 'HERBB NDB' (nearby suspected duplicate 'Herbb LOM')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:2587: skipping navaid 'HOKITIKA NDB-DME' (nearby suspected duplicate 'HOKITIKA NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:2655: skipping navaid 'HUGGY NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:3209: skipping navaid 'KOLOE NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:3371: skipping navaid 'LAANG NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:3955: skipping navaid 'MCDEN NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:4477: skipping navaid 'NOVARA NDB-DME' (nearby suspected duplicate 'NOVARA NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:4518: skipping navaid 'OBLIO NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:4577: skipping navaid 'ONIDA NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:4578: skipping navaid 'ONIDA NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:4904: skipping navaid 'PIEVE NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:5073: skipping navaid 'PRILEP NDB-DME' (nearby suspected duplicate 'PRILEP NDB')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:331:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:5829: skipping navaid 'SNUFF NDB' (already defined nearby)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:10562: skipping navaid 'VELIKIYE LUKI VOR-DME' (nearby suspected duplicate 'VELIKIYE LUKI VOR')
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:272:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:16455: unable to parse (invalid stod argument): '6  40.75644400  016.94085000   1184        10  300321.163  LIBV 32L GS'
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:272:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:16758: unable to parse (invalid stod argument): '6  28.27461100  068.45741900    185        10  300327.389 MCCT OPJA 33  GS'
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:272:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:16812: unable to parse (invalid stod argument): '6  22.74861100  121.09566700    143        10  300038.513 MFNN RCFN 04  GS'
navaid:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:272:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:16827: unable to parse (invalid stod argument): '6  24.01447200  121.61319400     52        10  320026.187  RCYU 03  GS'
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:415:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:21006: couldn't find any colocated navaid for DME 'TBL' (DTTA 01 DME-ILS)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:415:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:21367: couldn't find any colocated navaid for DME 'ICBF' (KCBF 36 DME-ILS)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:21819: skipping navaid 'KTKI 18 DME-ILS' (nearby suspected duplicate 'KTKI 17 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:415:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:22113: couldn't find any colocated navaid for DME 'OKR' (LZIB 22 DME-ILS)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:415:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:22114: couldn't find any colocated navaid for DME 'OB' (LZIB 31 DME-ILS)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:410:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:22396: DME 'GP' (SCSN 23 DME-ILS): while looking for a colocated navaid, found that the closest match has wrong name: 'GP' (ESGP 19 ILS-cat-I)
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26004: skipping navaid 'AALBORG TACAN' (nearby suspected duplicate 'AALBORG VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26006: skipping navaid 'ABBEVILLE DME' (nearby suspected duplicate 'ABBEVILLE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26010: skipping navaid 'AGEN DME' (nearby suspected duplicate 'AGEN-Gaudonville VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26011: skipping navaid 'AJACCIO DME' (nearby suspected duplicate 'AJACCIO VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26032: skipping navaid 'AMBOISE DME' (nearby suspected duplicate 'AMBOISE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26060: skipping navaid 'BALE MULHOUSE DME' (nearby suspected duplicate 'BALE-MULHOUSE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26072: skipping navaid 'BASTIA DME' (nearby suspected duplicate 'BASTIA PORETTA VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26083: skipping navaid 'BIARRITZ DME' (nearby suspected duplicate 'BIARRITZ BAYONNE ANGLET VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26085: skipping navaid 'BIKF 02 DME-ILS DME' (nearby suspected duplicate 'BIKF 02 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26086: skipping navaid 'BIKF 20 DME-ILS DME' (nearby suspected duplicate 'BIKF 20 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26087: skipping navaid 'BIKF 29 DME-ILS DME' (nearby suspected duplicate 'BIKF 29 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26088: skipping navaid 'BIKR 01 DME-ILS DME' (nearby suspected duplicate 'BIKR 01 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26092: skipping navaid 'BORDEAUX DME' (nearby suspected duplicate 'BORDEAUX MERIGNAC VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26095: skipping navaid 'BOURSONNE DME' (nearby suspected duplicate 'BOURSONNE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26097: skipping navaid 'BRAY SUR SEINE DME' (nearby suspected duplicate 'BRAY SUR SEINE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26107: skipping navaid 'BUDAPEST DME' (nearby suspected duplicate 'BUDAPEST VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26108: skipping navaid 'BURGOS DME' (nearby suspected duplicate 'BURGOS VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26112: skipping navaid 'CACERES DME' (nearby suspected duplicate 'CACERES VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26115: skipping navaid 'CAMBRAI DME' (nearby suspected duplicate 'CAMBRAI EPINOY VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26123: skipping navaid 'CASELLE DME' (nearby suspected duplicate 'CASELLE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26130: skipping navaid 'CHARLES-DE-GAULLE (PARIS) DME' (nearby suspected duplicate 'PARIS CHARLES DE GAULLE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26131: skipping navaid 'CHARLES-DE-GAULLE (PARIS) DME' (nearby suspected duplicate 'PARIS CHARLES DE GAULLE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26132: skipping navaid 'CHARTRES DME' (nearby suspected duplicate 'CHARTRES La Loupe VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26133: skipping navaid 'CHATILLON SUR MARNE DME' (nearby suspected duplicate 'CHATILLON SUR MARNE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26145: skipping navaid 'CITY CENTRE DME' (nearby suspected duplicate 'CYTZ 08 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26147: skipping navaid 'CLERMONT DME' (nearby suspected duplicate 'CLERMONT FERRAND AUVERGNE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26159: skipping navaid 'COULOMMIERS DME' (nearby suspected duplicate 'COULOMMIERS Voisins VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26171: skipping navaid 'DEELEN TACAN' (nearby suspected duplicate 'Deelen VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26176: skipping navaid 'DIJON DME' (nearby suspected duplicate 'DIJON-LONGVIC VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26178: skipping navaid 'DINARD DME' (nearby suspected duplicate 'DINARD PLEURTUIT SAINT MALO VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26183: skipping navaid 'DONETSK DME' (nearby suspected duplicate 'DONETSK VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26196: skipping navaid 'EDMONTON MUNI DME' (nearby suspected duplicate 'CYXD 34 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26201: skipping navaid 'EINDHOVEN TACAN' (nearby suspected duplicate 'Eindhoven VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26213: skipping navaid 'EPERNON DME' (nearby suspected duplicate 'EPERNON VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26222: skipping navaid 'EVREUX DME' (nearby suspected duplicate 'EVREUX FAUVILLE VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26223: skipping navaid 'EZEIZA DME' (nearby suspected duplicate 'EZEIZA VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26241: skipping navaid 'GANDER DME' (nearby suspected duplicate 'CYQX 03 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26244: skipping navaid 'GENOVA DME' (nearby suspected duplicate 'GENOVA VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26250: skipping navaid 'GILZE RIJEN TACAN' (nearby suspected duplicate 'Gilze Rijen VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26259: skipping navaid 'GOMEL DME' (nearby suspected duplicate 'GOMEL VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26268: skipping navaid 'GROSTENQUIN DME' (nearby suspected duplicate 'GROSTENQUIN VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26325: skipping navaid 'IZA DME' (nearby suspected duplicate 'LDZA 05 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26331: skipping navaid 'JIAYUGUAN DME' (nearby suspected duplicate 'JIAYUGUAN VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26354: skipping navaid 'KBHM 24 DME-ILS DME' (nearby suspected duplicate 'KBHM 24 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26386: skipping navaid 'KYZYL DME' (nearby suspected duplicate 'KYZYL VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26389: skipping navaid 'LA TOUR DU PIN DME' (nearby suspected duplicate 'LA TOUR DU PIN-Lyon Est VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26401: skipping navaid 'Lanzhou DME' (nearby suspected duplicate 'Lanzhou VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26404: skipping navaid 'LE BOURGET (PARIS) DME' (nearby suspected duplicate 'PARIS LE BOURGET VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26412: skipping navaid 'LFPN 25R DME' (nearby suspected duplicate 'LFPN 25R DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26416: skipping navaid 'LIMOGES DME' (nearby suspected duplicate 'LIMOGES VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26429: skipping navaid 'LYON/SAINT EXUPERY DME' (nearby suspected duplicate 'LYON SAINT EXUPERY VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26444: skipping navaid 'MARSEILLE PROVENCE DME' (nearby suspected duplicate 'MARSEILLE PROVENCE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26445: skipping navaid 'MARTIGUES DME' (nearby suspected duplicate 'MARTIGUES VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26454: skipping navaid 'MENDE DME' (nearby suspected duplicate 'MENDE-Nasbinals VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26473: skipping navaid 'MONTELIMAR DME' (nearby suspected duplicate 'MONTELIMAR ANCONE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26482: skipping navaid 'MOULINS DME' (nearby suspected duplicate 'MOULINS VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26490: skipping navaid 'MURCIA/SAN JAVIER TACAN' (nearby suspected duplicate 'MURCIA/SAN JAVIER VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26494: skipping navaid 'NANTES DME' (nearby suspected duplicate 'NANTES ATLANTIQUE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26502: skipping navaid 'NICE DME' (nearby suspected duplicate 'NICE COTE D AZUR VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26526: skipping navaid 'ORLY (PARIS) DME' (nearby suspected duplicate 'PARIS ORLY VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26560: skipping navaid 'PRILEP NDB-DME' (nearby suspected duplicate 'PRILEP DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26562: skipping navaid 'PRISTINA DME' (nearby suspected duplicate 'BKPR 17 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26570: skipping navaid 'RAMBOUILLET DME' (nearby suspected duplicate 'RAMBOUILLET-Les Bordes VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26577: skipping navaid 'REIMS DME' (nearby suspected duplicate 'REIMS CHAMPAGNE VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26585: skipping navaid 'ROLAMPONT DME' (nearby suspected duplicate 'ROLAMPONT VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26586: skipping navaid 'RONNE TACAN' (nearby suspected duplicate 'RONNE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26589: skipping navaid 'ROSARIO DME' (nearby suspected duplicate 'ROSARIO VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26593: skipping navaid 'SAAR 20 DME' (nearby suspected duplicate 'SAAR 20 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26603: skipping navaid 'SANKT-PETERBURG DME' (nearby suspected duplicate 'SANKT-PETERBURG Pulkovo VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26618: skipping navaid 'SESTRI DME' (nearby suspected duplicate 'SESTRI VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26639: skipping navaid 'SOESTERBERG TACAN' (nearby suspected duplicate 'Soesterberg VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26640: skipping navaid 'SOFIA DME' (nearby suspected duplicate 'SOFIA VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26654: skipping navaid 'ST. TROPEZ DME' (nearby suspected duplicate 'SAINT TROPEZ VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26655: skipping navaid 'STEFANIK DME' (nearby suspected duplicate 'LZIB 22 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26659: skipping navaid 'STRASBOURG DME' (nearby suspected duplicate 'STRASBOURG ENTZHEIM VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26687: skipping navaid 'TERRACE DME' (nearby suspected duplicate 'CYXT 33 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26694: skipping navaid 'TIVAT DME' (nearby suspected duplicate 'LYTV 32 DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26700: skipping navaid 'TORONTO DME' (nearby suspected duplicate 'CYYZ 24R DME-ILS')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26702: skipping navaid 'TOULOUSE DME' (nearby suspected duplicate 'TOULOUSE BLAGNAC VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26729: skipping navaid 'VIENTIANE DME' (nearby suspected duplicate 'VIENTIANE VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26757: skipping navaid 'WOENSDRECHT TACAN' (nearby suspected duplicate 'Woensdrecht VORTAC')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26761: skipping navaid 'XIANYANG DME' (nearby suspected duplicate 'XIANYANG VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\navdb.cxx:346:D:/Program Files/FlightGear 2017.2.1/data/Navaids/nav.dat.gz:26763: skipping navaid 'Yakutsk DME' (nearby suspected duplicate 'YAKUTSK VOR-DME')
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1412:nav.dat files load took: 2656
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1459:stage 1 commit took:339
navaid:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1463:SKIPPING POI load on Windows
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1489:awy.dat load took:6953
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1498:final commit took:102
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:187:cache rebuild took:27777msec
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:1181:init package root at:Path "FlightGear/Aircraft"
gui:4::0:libpng warning: iCCP: known incorrect sRGB profile
gui:4::0:libpng warning: iCCP: known incorrect sRGB profile
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:52:reading groundnet data from Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Airports/L/F/B/LFBR.groundnet.xml"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:62:parsing groundnet XML took 7
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2135:aircraft = c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:211:found aircraft in dir: D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:138:Found language resource for: fr_FR
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/sys.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/sys.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/atc.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/atc.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/tips.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/tips.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:aircraft-dir = D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:aircraft = c172p
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:fg-scenery = FlightGear/Scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:airport = LFBR
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:runway = 12
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-auto-coordination = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-terrasync = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-fullscreen = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:918:Setting geometry to 1920x1080

general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:geometry = 1920x1080
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/multi-sample-buffers=false
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/multi-samples=0
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-rembrandt = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/shaders/skydome=true
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:682:Channel string = serial,out,5,COM8,4800
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:nmea = serial,out,5,COM8,4800
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:timeofday = noon
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:season = summer
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:enable-real-weather-fetch = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:launcher = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2466:Using default download dir: Path "FlightGear"
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:390:read-allowed path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/AI"
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:390:read-allowed path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Liveries"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2491:Using TerraSync dir: Path "FlightGear/TerraSync"
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\sky\cloud.cxx:343:initializing cloud layers
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:557:Enabling ATI/AMD viewport hack
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:708:Configuration State
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:709:======= ==============
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:711:aircraft-dir = "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:712:fghome-dir = "Path "C:/Users/C&T/AppData/Roaming/flightgear.org""
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:713:download-dir = "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:714:terrasync-dir = "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/TerraSync"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:716:aircraft-search-paths = 
	
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:717:scenery-search-paths = 
	D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/TerraSync
	D:/Program Files/FlightGear 2017.2.1/data/Scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:121:NVIDIA Corporation
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:124:GeForce GTX 650 Ti BOOST/PCIe/SSE2
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:127:4.5.0 NVIDIA 384.94
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:137:4.50 NVIDIA
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-aircraft-list
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-nav-dat
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:674:General Initialization
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:675:======= ==============
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:684:FG_ROOT = "Path "D:/Program Files/FlightGear 2017.2.1/data""

general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\positioninit.cxx:323:Attempting to set starting position for LFBR:12
event:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\timing\sg_time.cxx:84:Reading timezone info from: Path "D:/Program Files/FlightGear 2017.2.1/data/Timezone/zone.tab"
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\scenery.cxx:353:Selected scenery is tilecache
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\terrain_stg.cxx:244:FGStgTerrain::init - init tilemgr
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:156:Initializing Tile Manager subsystem.
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:64:Initializing the tile cache.
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:67:  max cache size = 100
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:69:  current cache size = 0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:73:  done with init()
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress creating-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:726:Creating Subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:727:========== ==========
input:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\material\matlib.cxx:74:Reading materials from D:/Program Files/FlightGear 2017.2.1/data/Materials/regions/materials.xml
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Systems\system_mgr.cxx:41:Reading systems from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/systems.xml"
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\HUD\HUD.cxx:116:Initializing HUD Instrument
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\fg_fx.cxx:122:Reading sound sound from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/c172-sound.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:324:Creating subsystems took:3264
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress binding-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:332:Binding subsystems took:2
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/menu.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/menu.xml"
input:4:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\new_gui.cxx:373:dialog Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/gui/dialogs/c172p-menu.xml" has no name; skipping.
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\FGPUIMenuBar.cxx:56:Initializing old dialog commands:
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:325:Reusing metar properties at /environment[0]/metar[0] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[1] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[2] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[3] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[4] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[5] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[6] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[10] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[11] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:390:NoaaMetarRealWxController::update(): nearest airport with METAR has changed. Old: '', new: 'LFBO'
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:481:NoaaMetarRealWxController::update(): spawning load request for station-id 'LFBO'
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:58:  Loading stars from Path "D:/Program Files/FlightGear 2017.2.1/data/Astro/stars"
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:114:  Loaded 3141 stars
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/metarinterpolator.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Environment METAR Interpolation Rule
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/interpolator.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Environment Interpolation Rule
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/local-weather-rules.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Local Weather Rules 
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/Generic/g-forces.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem g force effects
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instruments.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem FiltersOnly
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/ground-effects.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_101
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/als-lights.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_102
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/engine.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_103
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/damage.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_104
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/pax.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_105
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/views.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_106
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/sounds.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_107
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/electrical.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_108
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:92:Parse I/O channel request: nmea,serial,out,5,COM8,4800
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:103:  protocol = nmea
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:252:  medium = serial
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:256:  direction = out
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:261:  hertz = 5
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:271:  device = COM8
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_io.cxx:275:  baud = 4800
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:133:Looking for bindings for joystick "Logitech Extreme 3D"
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:139:... found joystick: D:/Program Files/FlightGear 2017.2.1/data/Input/Joysticks/Logitech/extreme-3d-pro.xml
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:63:FlightRecorder: Recorder configuration #0
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:97:FlightRecorder: Using custom recorder configuration: Cessna 172P Flight Recorder
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/alpha-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/side-slip-rad'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/beta-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/roll-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/pitch-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/yaw-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/accelerations/pilot/x-accel-fps_sec'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/accelerations/pilot/y-accel-fps_sec'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/instrumentation/slip-skid-ball/indicated-slip-skid'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/elevator-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/left-aileron-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/right-aileron-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/rudder-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/yoke-aileron'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/yoke-elevator'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/pedals-rudder'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/flaps-lever'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[0]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[1]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[2]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[0]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[1]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[2]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[19]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[20]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[21]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[22]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[23]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[24]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[25]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/contact/unit[4]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/contact/unit[5]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/systems/vacuum/suction-inhg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/systems/pitot/measured-total-pressure-inhg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/velocities/vias-kts'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/instrumentation/magnetic-compass/indicated-heading-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/alarms/stall-warning'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/hazards/icing/wing'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[23]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[24]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[25]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:120:FlightRecorder: record size is 645 bytes
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:246:  loaded aero.
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:253:
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:254:
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:255:After loading aero definition file ...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:258:num engines = 2
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Systems\electrical.cxx:397:No xml-based electrical model specified for this model!
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\instrument_mgr.cxx:76:Reading instruments from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instrumentation.xml"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.term"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.low"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.high"
instruments:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\instrument_mgr.cxx:92:creating default GPS instrument
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/KAP140.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem generic autopilot
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/glass-rain.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem autopilot helpers
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/control-lock.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_2
network:3:G:\Jenkins\workspace\Windows-release\flightgear\src\MultiPlayer\multiplaymgr.cxx:919:FGMultiplayMgr - multiplayer mode disabled (no MP server specificed).
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Cockpit\cockpitDisplayManager.cxx:68:Reading cockpit displays from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instrumentation.xml"
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'ATC/Approach/Ground' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'Pilot' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cstr_uk_female-1.0.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'Copilot/Instructor' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'AI-Plane' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
event:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Time\light.cxx:100:Initializing Lighting interpolation tables.
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/ambient"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/diffuse"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/specular"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/sky"
opengl:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:
opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:Warning: Material::setShininess() of 200 is above permitted maximum, clamping to 128.

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

sound:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\sound\soundmgr_openal.cxx:171:Initializing OpenAL sound manager
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finishing-subsystems
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:KMA20 audio panel initialized
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Hobbs system stopped
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Hobbs system stopped
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Starter off
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:KI266 dme indicator #0 initialized
general:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:284:addEventListener(/sim[0]/gui[0]/canvas[0], mousedown)
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:951:Nasal init took:2427
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Time\TimeManager.cxx:411:After TimeManager::setTimeOffset(): warp = 0
instruments:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\gps.cxx:377:GPS saw route-manager flight-plan replaced.
instruments:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\gps.cxx:1380:empty GPS search query
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\route_mgr.cxx:812:route manager, current-wp is now -1
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\AIModel\AIManager.cxx:161:loading scenario 'nimitz_demo'
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:956:Subsystems postinit took:107
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:965:

view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:424:Created multi-app mutex, we are in writeable mode
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:443:CrashRpt enabled
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:470:FlightGear:  Version 2017.2.1
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:471:FlightGear:  Build Type Release
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:472:Built with Microsoft Visual C++ version 1900
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:474:Jenkins number/ID 219:219
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2832:platform default fg_root = Path "../data"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:505:Reading global defaults
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:515:Finished Reading global defaults
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:261:NavCache at:Path "C:/Users/C&T/AppData/Roaming/flightgear.org/navdata_2017_2.cache"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:264:NavCache read-only flags is:0
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1347:NavCache: no main cache rebuild required
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:1181:init package root at:Path "FlightGear/Aircraft"
gui:4::0:libpng warning: iCCP: known incorrect sRGB profile
gui:4::0:libpng warning: iCCP: known incorrect sRGB profile
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:52:reading groundnet data from Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Airports/L/F/B/LFBR.groundnet.xml"
navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:62:parsing groundnet XML took 8
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2135:aircraft = c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:211:found aircraft in dir: D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:138:Found language resource for: fr_FR
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/sys.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/sys.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/atc.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/atc.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/tips.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/tips.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:aircraft-dir = D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:aircraft = c172p
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:357:scenery path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Scenery"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:fg-scenery = FlightGear/Scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:airport = LFBR
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:runway = 12
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-auto-coordination = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-terrasync = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-fullscreen = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:918:Setting geometry to 1920x1080

general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:geometry = 1920x1080
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/multi-sample-buffers=false
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/multi-samples=0
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:disable-rembrandt = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:prop = /sim/rendering/shaders/skydome=true
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:timeofday = noon
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:season = summer
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:enable-real-weather-fetch = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2441:	option:launcher = 
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2466:Using default download dir: Path "FlightGear"
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:390:read-allowed path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/AI"
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:390:read-allowed path not found:Path "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/Liveries"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2491:Using TerraSync dir: Path "FlightGear/TerraSync"
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\sky\cloud.cxx:343:initializing cloud layers
general:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:557:Enabling ATI/AMD viewport hack
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:708:Configuration State
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:709:======= ==============
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:711:aircraft-dir = "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:712:fghome-dir = "Path "C:/Users/C&T/AppData/Roaming/flightgear.org""
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:713:download-dir = "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:714:terrasync-dir = "D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/TerraSync"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:716:aircraft-search-paths = 
	
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:717:scenery-search-paths = 
	D:/Program Files/FlightGear 2017.2.1/bin/FlightGear/TerraSync
	D:/Program Files/FlightGear 2017.2.1/data/Scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:121:NVIDIA Corporation
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:124:GeForce GTX 650 Ti BOOST/PCIe/SSE2
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:127:4.5.0 NVIDIA 384.94
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\gui.cxx:137:4.50 NVIDIA
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-aircraft-list
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-nav-dat
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-scenery
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:674:General Initialization
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:675:======= ==============
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:684:FG_ROOT = "Path "D:/Program Files/FlightGear 2017.2.1/data""

general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\positioninit.cxx:323:Attempting to set starting position for LFBR:12
event:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\timing\sg_time.cxx:84:Reading timezone info from: Path "D:/Program Files/FlightGear 2017.2.1/data/Timezone/zone.tab"
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\scenery.cxx:353:Selected scenery is tilecache
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\terrain_stg.cxx:244:FGStgTerrain::init - init tilemgr
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:156:Initializing Tile Manager subsystem.
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:64:Initializing the tile cache.
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:67:  max cache size = 100
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:69:  current cache size = 0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilecache.cxx:73:  done with init()
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress creating-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:726:Creating Subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:727:========== ==========
input:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\material\matlib.cxx:74:Reading materials from D:/Program Files/FlightGear 2017.2.1/data/Materials/regions/materials.xml
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Systems\system_mgr.cxx:41:Reading systems from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/systems.xml"
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\HUD\HUD.cxx:116:Initializing HUD Instrument
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\fg_fx.cxx:122:Reading sound sound from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/c172-sound.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:324:Creating subsystems took:3545
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress binding-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:332:Binding subsystems took:13
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress init-subsystems
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'en' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/en/menu.xml"
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\locale.cxx:221:Reading localized strings for 'fr' from Path "D:/Program Files/FlightGear 2017.2.1/data/Translations/fr/menu.xml"
input:4:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\new_gui.cxx:373:dialog Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/gui/dialogs/c172p-menu.xml" has no name; skipping.
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\GUI\FGPUIMenuBar.cxx:56:Initializing old dialog commands:
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:325:Reusing metar properties at /environment[0]/metar[0] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[1] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[2] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[3] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[4] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[5] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[6] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[10] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:335:Adding metar properties at /environment[0]/metar[11] for 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:390:NoaaMetarRealWxController::update(): nearest airport with METAR has changed. Old: '', new: 'LFBO'
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\realwx_ctrl.cxx:481:NoaaMetarRealWxController::update(): spawning load request for station-id 'LFBO'
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:58:  Loading stars from Path "D:/Program Files/FlightGear 2017.2.1/data/Astro/stars"
astro:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\ephemeris\stardata.cxx:114:  Loaded 3141 stars
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/metarinterpolator.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Environment METAR Interpolation Rule
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/interpolator.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Environment Interpolation Rule
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Environment/local-weather-rules.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem Local Weather Rules 
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/Generic/g-forces.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem g force effects
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instruments.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem FiltersOnly
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/ground-effects.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_101
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/als-lights.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_102
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/engine.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_103
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/damage.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_104
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/pax.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_105
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/views.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_106
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/sounds.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_107
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/electrical.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_108
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:133:Looking for bindings for joystick "Logitech Extreme 3D"
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Input\FGJoystickInput.cxx:139:... found joystick: D:/Program Files/FlightGear 2017.2.1/data/Input/Joysticks/Logitech/extreme-3d-pro.xml
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:63:FlightRecorder: Recorder configuration #0
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:97:FlightRecorder: Using custom recorder configuration: Cessna 172P Flight Recorder
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/alpha-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/side-slip-rad'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/beta-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/roll-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/pitch-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/orientation/yaw-rate-degps'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/accelerations/pilot/x-accel-fps_sec'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/accelerations/pilot/y-accel-fps_sec'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/instrumentation/slip-skid-ball/indicated-slip-skid'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/elevator-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/left-aileron-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/right-aileron-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/surface-positions/rudder-pos-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/yoke-aileron'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/yoke-elevator'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/pedals-rudder'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/model/c172p/cockpit/flaps-lever'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[0]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[1]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[2]/steering-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[0]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[1]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[2]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[19]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[20]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[21]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/gear/gear[22]/compression-norm'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[23]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[24]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[25]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/contact/unit[4]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/contact/unit[5]/z-position'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/systems/vacuum/suction-inhg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/systems/pitot/measured-total-pressure-inhg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/velocities/vias-kts'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/instrumentation/magnetic-compass/indicated-heading-deg'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/sim/alarms/stall-warning'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/hazards/icing/wing'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[23]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[24]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:266:FlightRecorder: Recording non-existent property '/fdm/jsbsim/gear/unit[25]/WOW'.
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Aircraft\flightrecorder.cxx:120:FlightRecorder: record size is 645 bytes
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:246:  loaded aero.
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:253:
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:254:
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:255:After loading aero definition file ...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:258:num engines = 2
systems:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Systems\electrical.cxx:397:No xml-based electrical model specified for this model!
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\instrument_mgr.cxx:76:Reading instruments from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instrumentation.xml"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.term"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.low"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Navaids/range.high"
instruments:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\instrument_mgr.cxx:92:creating default GPS instrument
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/KAP140.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem generic autopilot
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/glass-rain.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem autopilot helpers
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:201:Reading property-rule configuration from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/control-lock.xml"
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\autopilotgroup.cxx:208:adding  property-rule subsystem unnamed_autopilot_2
network:3:G:\Jenkins\workspace\Windows-release\flightgear\src\MultiPlayer\multiplaymgr.cxx:919:FGMultiplayMgr - multiplayer mode disabled (no MP server specificed).
cockpit:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Cockpit\cockpitDisplayManager.cxx:68:Reading cockpit displays from Path "D:/Program Files/FlightGear 2017.2.1/data/Aircraft/c172p/Systems/instrumentation.xml"
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'ATC/Approach/Ground' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'Pilot' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cstr_uk_female-1.0.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'Copilot/Instructor' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\voice.cxx:103:creating flite voice
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\flitevoice.cxx:54:FLITEVoice initialized for sample-group 'flite-voice'. Samples will be named 'AI-Plane' voice is 'Path "D:/Program Files/FlightGear 2017.2.1/data/ATC/cmu_us_arctic_slt.htsvoice"'
event:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Time\light.cxx:100:Initializing Lighting interpolation tables.
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/ambient"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/diffuse"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/specular"
math:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\math\interpolater.cxx:81:Initializing Interpolator for Path "D:/Program Files/FlightGear 2017.2.1/data/Lighting/sky"
opengl:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:
opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:Warning: Material::setShininess() of 200 is above permitted maximum, clamping to 128.

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

opengl:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\fg_os_osgviewer.cxx:203:PNG lib warning : iCCP: known incorrect sRGB profile

sound:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\sound\soundmgr_openal.cxx:171:Initializing OpenAL sound manager
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finishing-subsystems
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:KMA20 audio panel initialized
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Hobbs system stopped
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Hobbs system stopped
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Starter off
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:KI266 dme indicator #0 initialized
general:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\canvas\elements\CanvasElement.cxx:284:addEventListener(/sim[0]/gui[0]/canvas[0], mousedown)
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:951:Nasal init took:2431
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Time\TimeManager.cxx:411:After TimeManager::setTimeOffset(): warp = 0
instruments:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\gps.cxx:377:GPS saw route-manager flight-plan replaced.
instruments:4:G:\Jenkins\workspace\Windows-release\flightgear\src\Instrumentation\gps.cxx:1380:empty GPS search query
autopilot:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Autopilot\route_mgr.cxx:812:route manager, current-wp is now -1
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\AIModel\AIManager.cxx:161:loading scenario 'nimitz_demo'
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:956:Subsystems postinit took:121
general:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:965:

view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress finalize-position
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:3
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:3
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:504:FGTileMgr: at lon = 1.25776deg, lat = 43.4514deg, elev = -3047.7m, scheduling needed for:1:1, 43:3, visibility=32000
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:293:scheduling needed tiles for 1:1, 43:3, tile-width-m:20187.1, tile-height-m:13914.9
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:1
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:2
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:3
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:4
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:5
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:0:3, 43:6
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:1
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:2
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:4
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:5
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:0, 43:6
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:1
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:2
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:4
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:5
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:1, 43:6
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:1
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:2
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:3
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:4
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:5
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:2, 43:6
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:0
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:1
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:2
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:3
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:4
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:5
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\tilemgr.cxx:251:sched_tile: new tile entry for:1:3, 43:6
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957635.stg
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress loading-scenery
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957635.stg"
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\fgmetar.cxx:153:2017/09/24 04:00 LFBO 240400Z AUTO 16003KT 130V200 CAVOK 13/12 Q1019 NOSIG 
environment:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Environment\fgmetar.cxx:157:METAR from tgftp.nws.noaa.gov
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974041.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974041.stg"
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Primer reset to 0
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974033.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974033.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974040.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974040.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974042.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974042.stg"
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\fdm_shell.cxx:171:Scenery loaded, will init FDM
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:384:Starting and initializing JSBsim
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:404:T,p,rho: 518.67, 2116.22, 0.0023769
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:139:Start common FDM init
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:146:...initializing position...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1047:FGJSBsim::set_Longitude: 0.0219521
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1026:FGJSBsim::set_Latitude: 0.75837
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1027: cur alt (ft) =  0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:158:Checking for lon = 1.25776deg, lat = 43.4514deg, alt = -9999ft
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1060:FGJSBsim::set_Altitude: 620.293
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:175:...initializing ground elevation to 620.193ft...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:178:...initializing sea-level radius...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:181: lat = 43.4514 alt = 620.293
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:186:...initializing Euler angles...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1158:FGJSBsim::set_Euler_Angles: 0, 0.0074002, 2.04256
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:195:...initializing velocities...
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1072:FGJSBsim::set_V_calibrated_kts: 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\flight.cxx:231:End common FDM init
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:433:Ready to trim, terrain elevation is: 620.189
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:1293:  Trim complete
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:448:  Initialized JSBSim with:
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:455:  Vn,Ve,Vd= -0, 0, 0 ft/s
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:477:  Bank Angle: -0.134471 deg
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:479:  Pitch Angle: 2.36007 deg
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:481:  True Heading: 117.019 deg
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:483:  Latitude: 43.2593 deg
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:485:  Longitude: 1.25776 deg
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:487:  Altitude: 624.591 feet
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:488:  loaded initial conditions
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:490:  set dt
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:492:Finished initializing JSBSim
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:495:FGControls::get_gear_down()= 1
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Electrical system initialized
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:0: GEAR_CONTACT: 0 seconds: NOSE 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:1: GEAR_CONTACT: 0 seconds: LEFT_MAIN 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:2: GEAR_CONTACT: 0 seconds: RIGHT_MAIN 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:3: GEAR_CONTACT: 0 seconds: TAIL_SKID 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:4: GEAR_CONTACT: 0 seconds: FRONT_BROKEN_GEAR 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:5: GEAR_CONTACT: 0 seconds: LEFT_BROKEN_GEAR 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:6: GEAR_CONTACT: 0 seconds: RIGHT_BROKEN_GEAR 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:7: GEAR_CONTACT: 0 seconds: NOSE_TOP 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:8: GEAR_CONTACT: 0 seconds: NOSE 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:9: GEAR_CONTACT: 0 seconds: LFFloatGear 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:10: GEAR_CONTACT: 0 seconds: RFFloatGear 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:11: GEAR_CONTACT: 0 seconds: LMFloatGear 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:12: GEAR_CONTACT: 0 seconds: RMFloatGear 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:13: GEAR_CONTACT: 0 seconds: NOSE_SKI 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:14: GEAR_CONTACT: 0 seconds: LEFT_SKI 1
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:15: GEAR_CONTACT: 0 seconds: RIGHT_SKI 1
view:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Viewer\splash.cxx:678:Splash screen progress 
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/A"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974049.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974049.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/B"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/C"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974032.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974032.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/D"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974034.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974034.stg"
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:16: GEAR_CONTACT: 0.00833333 seconds: TAIL_SKID 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:17: GEAR_CONTACT: 0.00833333 seconds: FRONT_BROKEN_GEAR 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:18: GEAR_CONTACT: 0.00833333 seconds: LEFT_BROKEN_GEAR 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:19: GEAR_CONTACT: 0.00833333 seconds: RIGHT_BROKEN_GEAR 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:20: GEAR_CONTACT: 0.00833333 seconds: NOSE_TOP 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:21: GEAR_CONTACT: 0.00833333 seconds: NOSE 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:22: GEAR_CONTACT: 0.00833333 seconds: LFFloatGear 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:23: GEAR_CONTACT: 0.00833333 seconds: RFFloatGear 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:24: GEAR_CONTACT: 0.00833333 seconds: LMFloatGear 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:25: GEAR_CONTACT: 0.00833333 seconds: RMFloatGear 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:26: GEAR_CONTACT: 0.00833333 seconds: NOSE_SKI 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:27: GEAR_CONTACT: 0.00833333 seconds: LEFT_SKI 0
flight:3:G:\Jenkins\workspace\Windows-release\flightgear\src\FDM\JSBSim\JSBSim.cxx:550:28: GEAR_CONTACT: 0.00833333 seconds: RIGHT_SKI 0
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974048.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974048.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974050.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974050.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/E"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957659.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957659.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/F"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/G"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974025.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974025.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/H"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/I"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974043.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974043.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/J"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974057.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974057.stg"
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Garmin 196 loading cities
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/K"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/KEQA"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/L"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/M"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/N"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/O"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/P"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/Q"
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:Garmin 196 loading cities done
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/R"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/S"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957651.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957651.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/T"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957667.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957667.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974024.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974024.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974026.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974026.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/U"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974035.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974035.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974051.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974051.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974056.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974056.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974058.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974058.stg"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/V"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/W"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:383:parsing traffic in:Path "D:/Program Files/FlightGear 2017.2.1/data/AI/Traffic/misc"
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:393:parsing traffic schedules took:14244msec
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Traffic\TrafficMgr.cxx:585:finishing AI-Traffic init
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957643.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957643.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957675.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957675.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974027.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974027.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974059.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974059.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974017.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974017.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974065.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974065.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974016.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974016.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974018.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974018.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974064.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974064.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974066.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974066.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2957683.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e000n43/2957683.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974019.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974019.stg"
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:624:Loading tile 2974067.stg
terrain:3:G:\Jenkins\workspace\Windows-release\simgear\simgear\scene\tgdb\ReaderWriterSTG.cxx:321:Loading stg file Path "D:/Program Files/FlightGear 2017.2.1/data/Scenery/Terrain/e000n40/e001n43/2974067.stg"
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_scene_commands.cxx:76:Program exit requested.
io:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:827:Saving user settings to Path "C:/Users/C&T/AppData/Roaming/flightgear.org/autosave_2017_2.xml"
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:56:FLITE synthesis thread exiting
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:109:FLITE synthesis thread joined OK
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:56:FLITE synthesis thread exiting
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:109:FLITE synthesis thread joined OK
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:56:FLITE synthesis thread exiting
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:109:FLITE synthesis thread joined OK
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:56:FLITE synthesis thread exiting
sound:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Sound\VoiceSynthesizer.cxx:109:FLITE synthesis thread joined OK
terrain:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Scenery\terrain_stg.cxx:265:FGStgTerrain::shutdown - shutdown tilemgr
ai:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\dynamics.cxx:170:destroyed dynamics for:LFBR

Dernière modification par tcx32fr (24/09/2017 6:14:31)


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#19 24/09/2017 9:03:06

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour,
je ne vois rien d'anormal dans le log.
Ici, avec la commande --nmea... il y a des messages d'erreur (absence de com8) mais fg se lance.

io:5:/home/tt/fg-1/simgear/simgear/serial/serial.cxx:105:Cannot open COM8 for serial I/O
io:5:/home/tt/fg-1/simgear/simgear/io/sg_serial.cxx:57:Error opening device: COM8
io:5:/home/tt/fg-1/flightgear/src/Network/nmea.cxx:498:Error opening channel communication layer.
io:5:/home/tt/fg-1/flightgear/src/Main/fg_io.cxx:370:I/O Channel config failed.

Essaie avec un com "bidon" (com1, com200) pour voir si il affiche les erreurs?

Si tu réussis à afficher la console, il y a plusieurs niveaux de log. Essaie de lancer avec "--log-level=warn" ou plus (info, bulk)
http://wiki.flightgear.org/Commonly_use … ging_tools

Pose aussi la question sur le forum anglais. Je vois que c'est fait wink

PS:

Pb connu ?

Apparemment oui, il y aurait un problème de caractère de fin de ligne, quoique là il semble que c'est en "input":

- I already saw many other users on the forum having the same problem (FG stuck at "finalising position"), but no answer was really brought except using another method (telnet, udp, etc.)

https://forum.flightgear.org/viewtopic.php?f=36&t=32873

Dernière modification par ctesc356 (24/09/2017 10:47:57)


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

#20 24/09/2017 19:51:19

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir
J'ai compris dans quelles conditions j'arrive à émettre sur COM8 sans planter l'init FG: en fait je lance une autre simulation avant via le logiciel de prépa de NAV de Foufou (voir http://francois.fouchet.free.fr/ ) qui possède dans ses paramètres la faculté d’émettre les messages NMEA sur le port de son choix (voir https://drive.google.com/file/d/0B-Weut … p=sharing), et de lancer une simulation de vol sur un plan de vol. Si je passe par ce lancement, je paramètre les NMEA sur COM8, je lande la simu, que je stoppe la simulation et quitte Foufou, que je lance FG alors ça marche...

Est-ce que Foufou positionne des paramètres qui sont "conservés" et utilisés pas défaut par FG ? ça voudrait dire qu'il manque à FG des paramètres à positionner ?

Tout se passe


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#21 7/10/2017 0:55:07

tcx32fr
Membre
Inscription : 17/09/2017
Messages : 14

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonsoir

Pour ceux que ça intéresse j'ai enfin résolu mon pb. En fait le pb vient du fait que si la liaison BT n'est pas établie pendant l'initialisation de FG, alors ce dernier n'essaie jamais de se reconnecter. Donc, quand on utilise une tablette android avec notamment l'appli Bluetooth GPS, qui capture les trames NMEA et en déduit positions, cap, altitude et vitesse, cette appli doit être paramétrée en reconnect permanent tant que la connexion BT n'est pas établie, et il faut lancer une demande de connexion AVANT l'initialisation de FG, lancer ce dernier avec les bons paramètres (--NMEA etc, voir plus haut) et là tout marche correctement.

Pour info pour ceux que ça intéresse, vous pouvez télécharger par ex la version gratuite de Flightassistant V2 (voir https://www.flightassistant.aero/fr/) ou tout autre appli de votre choix, et ainsi visualiser sur tablette android la trajectoire de votre machine sur une carte déroulante en autorisant l'appli Bluetooth GPS à émuler un GPS (dans les options de développement Android). C'est ce qui se passe dans la vraie vie et ça aide nettement pour les approches par exemples

@+


Pilote Privé, FlightGear 2017.2.1
Win7 SP1, NVIDIA GeForce GTX 650 TI Boost 2GO, Directx11, proc AMDFX-8350 8 coeurs, 8 GO RAM, Stick Logitech Extreme 3D Pro

Hors ligne

#22 7/10/2017 9:40:06

ctesc356
Membre
Inscription : 18/05/2010
Messages : 2 226

Re : [RESOLU]: emission position GPS (NMEA) avion sur port Bluetooth du PC

Bonjour,
c'est bon à savoir, merci pour l'info.


Intel i5 3570 3.4Mhz, Nvidia GTX 660, 8Go Ram, Linux Mint

Hors ligne

Pied de page des forums