c141fe

Any word on update for the NAT and PACOT download - AUSOT seems to be working fine.

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 updated about 30 minutes ago (2018/07/20 18:10 GMT) and EFB2 is getting some bad data from the online track files

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 ActiveSky entry, I run ActiveSky from a 2nd desktop and it just wasn't on at the time. I had the 2nd desktop up and running this time and EFB2 is reading the "current_wx_snapshot.txt file fine. Client_201807201042.txt.zip Server_201807201042.txt.zip

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 "...Documents\AivlaSoft\EFB2\Server\AIRAC\Navigraph FMS Data" folder Ran Navigraph FMS Data Manager to reinstall cycle 1808 files to EFB2 Ran AivlaSoft EFB2 DbBuilder to create new database file, selected it and opened AivlaSoft EFB2 Server Same problem exist fyi - Current nats.html file covers a period of JUL 19/0100Z TO JUL 19/1900Z which is valid fof NG 1808 Client_201807191138.txt.zip Server_201807191138.txt.zip

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 : NAT data download complete 2018-07-04 23:19:19.248 Debug : PACOT data download complete 2018-07-04 23:19:20.442 Debug : AUSOTs data download complete 2018-07-04 23:19:20.608 Error : Could not parse NATS tracks due to: An item with the same key has already been added. Confirmed the 3 html files are present in .../Documents\AivlaSoft\EFB2\Server\Downloads Current UTC is July 5, 2018 @ 0625. There are several Eastbound NATs valid at this time so they should be appearing. Have completely uninstalled and then reinstalled EFB2 with same results. Running Windows 10 64-bit P3Dv4.3 Windows Defender AV EFBv2 Server=2.0.52.0 Client=2.0.70.0

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 what the EFB DisplayUnit displays after reading the default Couatl "scenery.cfg" file - this is wrong My simulators (FSX, P3Dv3 and P3Dv4) are installed in a folder named Simulator located at the root of C: (C:\Simulators\). In the Simulator Folder I created a folder named "Scenery_cfg" and created folders within in it for v3 and v4 - e.g. "C:\Simulators\Scenery_cfg\Prepar3D v4". I then made a copy of the Couatl "scenery.cfg" file and placed it in "C:\Simulators\Scenery_cfg\Prepar3D v4". Using Notepad, I deleted the "\Scenery" from the end of the Local paths. "Local=C:\Simulators\Addon Manager\Flightbeam\KSFOHD\Scenery" became "Local=C:\Simulators\Addon Manager\Flightbeam\KSFOHD" etc. I then pointed the DataProvider to the folder "C:\Simulators\Scenery_cfg\Prepar3D v4" and ran Data | Simulator scenery data update again. This time the DisplayUnit displayed the Flightbeam KSFO correctly. Until such time as AivlaSoft EFB is updated to account for the new Add on Format of P3D, I will just have to remember to copy and modify the Couatl "scenery.cfg" file any time I add a new airport and prior to running the Data | Simulator scenery data update.

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 flightaware.com and pasted into EFB using the Route Setup|Select window. EFB processed and displayed it with no problems, but when I clicked the Activate button I got the error message. I tried loading "EFB_current_garmin.pln" manually within FSX using the FLIGHT PLANNER window and nothing happened (failed to load). I began to suspect a problem with the plan itself. Here is the plan copied from flightaware (with airport IDs added at beginning and end): kdfw FERRA5 PNH J17 PUB CHE J163 OCS J52 LKT MWH YVR QQ YZT KATCH B757 CJAYY 5700N 16000W 5600N 17000W DRAPP A342 AMOND OPAKE R580 OATIS OTR3 GOC Y88 KCC V52 CBE V17 LABEL Y50 IGMON A1 ELATO V521 ABBEY vhhh - I noticed the 2 waypoints designated by Lat/Long (5700N 16000W & 5600N 17000W) and to see if they were causing the problem, I deleted them and then reloaded flight plan. Everything worked perfect. - I started experimenting on the applicable lines of code in the .pln file and it turned out to be the way EFB processed the line. -- EFB converted the waypoint "5700N 16000W" to which is to long. It appears that the ATCWaypoint id string is limited to 12 (10 characters + 2 quote marks) -- I changed the 2 ATCWaypoint id to and and the pln file loaded fine -- I then went back to EFB, pasted the above flight plan into Route Setup|Select, deleted the 2 trailing zeroes in the Lat/Long waypoints (5700N 16000W 5600N 17000W became 57N 160W 56N 170W) and then clicked Activate. WORKED LIKE A CHARM. Bottomline: If any one is having this problem and the path to "\Flight Simulator X Files" is set correctly, they need to check their flight plan to make sure the name of any waypoint does not exceed 10 characters.