Jump to content


  • Content Count

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Any word on update for the NAT and PACOT download - AUSOT seems to be working fine.
  2. Thanks, I will change setting to UTC World and see if that helps. Just curious though, the problem occurs with only server and client started before I start P3Dv4 so where would EFB2 be getting a simulator UTC from? Additional info: I'm not sure how it might be connected, if at all, but I had not updated my ActiveSky (ASP4) on the 2nd computer to cycle 1808. I just updated ASP4 and EFB2 seems to be loading normally now including tracks with P3Dv4 running or not. It could be just a coincidence and rather may have something to do with the fact the track info online was just updat
  3. Urs going through the steps 1808 is in the folder and I have one additonal file in the folder - "cycle_info.txt". Moved it to desktop before proceeding. "cycleInfo.txt" contains "Cycle = 1808 Revision = 1" plus some statistics Did it Did it the info in the Cycle information block is "Cycle 1808 Rev 1, valid from 2018-07-19 to 2018-08-15" Did it Did it Started the EFB Server and the message "Organized tracks disabled because AIRAC cycle is outdated"´╗┐ is still there´╗┐ have attached updated support files Regarding the Act
  4. Updated EFB2 to Navigraph cycle 1808/R1, ran AivlaSoft EFB2 DbBuilder to create new database file, selected it and opened AivlaSoft EFB2 Server. The server log shows: 2018-07-19 09:31:31.892 Debug : Database selected = P3Dv4.NG-1808/R1 . 2018-07-19 09:31:56.325 Debug : Organized tracks disabled because AIRAC cycle is outdated The Client shows that tracks are unavailable for the same reason dbBuilderLogfile.txt Additional troubleshooting, I deleted all files in the "...Documents\AivlaSoft\EFB2\Server\DbBuilder" folder and the "...Docum
  5. Get error message regarding NATS "Could not parse NATS tracks due to: An item with the same key has already been added." 1. updated Navigraph data to 1807 2. ran DbBuilder 3. started EFB2 Server 4. started EFB2 Client 5. checked "Use Organized Track Systems (NAT,... 6. clicked Apply 7. Got the following 2018-07-04 23:19:18.727 Debug : Start downloading AUSOTs data 2018-07-04 23:19:18.727 Debug : Start downloading NAT data 2018-07-04 23:19:18.728 Debug : Start downloading PACOT data 2018-07-04 23:19:19.138 Debug :
  6. Reading the "scenery.cfg" file located at "C:\ProgramData\Virtuali\Couatl\prepar3dv4" to capture the airports located outside the root prepar3dv4 install folder is a great idea but I found one problem. The path to the sceneries listed in "scenery_add-ons.xml" and the Couatl "scenery.cfg" file includes "\Scenery" at the end - for example this is the path to Flightbeam KSFO - "Local=C:\Simulators\Addon Manager\Flightbeam\KSFOHD\Scenery". It appears, at least in my case, that the EFB DataProvider is unable to process this path correctly. The KSFO from ORBX NORTHERN CALIFORNIA is wh
  7. Urs: here is some info for you that may help those folks getting this error message. I recently started doing some long range flights with the PMDG 700-300ER. On some flights everything worked fine concerning EFB inputting the flight plan into the Garmin. But on other flights, such as KDFW-VHHH, I was getting the beep along with "Exception from FSX received: LOAD_FLIGHTPLAN_FAILED". I knew it wasn't a path issue as the file "EFB_current_garmin.pln" was being created normally in the "C:\Users\xxxxx\Documents\Flight Simulator X Files" folder. The flight plan in question was copied from
  • Create New...