Navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:62:parsing groundnet XML took 0 Navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Airports\xmlloader.cxx:52:reading groundnet data from Path "D:/Programmes/FlightGear 2017.3.1/bin/FlightGear/TerraSync/Airports/L/F/L/" Gui:4::0:libpng warning: iCCP: known incorrect sRGB profile General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:1220:init package root at:Path "FlightGear/Aircraft" Navaid:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Navaids\NavDataCache.cxx:1347:NavCache: no main cache rebuild required 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:261:NavCache at:Path "C:/Users/Harrisson/AppData/Roaming//navdata_2017_3.cache" Input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\globals.cxx:790:Reading user settings from Path "C:/Users/Harrisson/AppData/Roaming//autosave_2017_3.xml" General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:542:Finished Reading global defaults General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:532:Reading global defaults General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\options.cxx:2888:platform default fg_root = Path "./data" General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:478:Jenkins number/ID 223:223 General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:476:Built with Microsoft Visual C++ version 1900 General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:475:FlightGear: Build Type Release General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:474:FlightGear: Version 2017.3.1 General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\main.cxx:447:CrashRpt enabled General:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_init.cxx:451:Created multi-app mutex, we are in writeable mode Harrisson Posts: 12 Joined: Tue 11:31 pmįor the failure: the options I have are like this I'm sorry if the screens made this post sooooooo long, I haven't found an option to hide them (like the "spoilers warning" option in some forums).Īnd I'm happy with your effort to help me, thank you very much ! I will keep trying by myself too - if I find the problem I will inform you. I don't think the battery is drained out since I installed everything yesterday and I don't have any failure checked. because the voltage is zero ?):Īnd, finishing the "before engines start" checklist, the hydraulic pressure is at zero when it should be between 13 PSI. In this one, the first checklist, just remove the external covers (we can see the external power too)Īnd then the problems start: the checklist says to check this indicator, and it is not above the indicated valor (18V)Īfter this point, more problems: the indicated boxes should turn on when the caution light is on, but this is not the case (I think. I will post screens of the checklist (FlightGear version 2017.3.1): When starting the simulation, the DHC 6 300 Twin Otter (downloaded from the official hangar) has an external power supply, and we can choose the power from the battery or the external power (makes no difference, still the engines won't start). I hope I gave you all the information needed (but if you need some debug logs or anything like that just tell mehow and I will provide you).Īnd I thank you for your help =) Harrisson Posts: 12 Joined: Tue 11:31 pm This error (or bug) is always there If I try to start at the runway or at the gates. The airport is at Clermont-Ferrand (France). I'm running on a fresh install of Windows 10 and a fresh and clean install of FlightGear. Also, the lights of these aircrafts will not go on (and the battery indicator reads "empty").įirst, I was using the latest version (2017.3.1), I though that maybe it was some compatibility issue (because I used them before) and installed 2017.2.1 but the same thing happens. Everything works fine with other aircrafts (Cessna 172P, Tupolev, Boeings etc).Įverything loads too (airports, AI traffic, etc). They simply don't start the engines (I tested in manual and autostart mode, for the DHC I removed the exterior covers too). I have a little problem with two aircrafts : De Havilland Canada DHC 6 300 Twin Otter (wheels) and Cessna Citation II Hi there ! I'm new here in the forum but i use FlightGear for some time already.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |