srcooke

You need to run AivlaSoft.Efb.SupportFile.exe on the server PC also Reinhold and post the file generated as well.

Reboot the PC and try again.

I cannot test for P3Dv4 but assume the same file structure Navigate to the P3D \Scenery\0701\scenery\ folder and APX56150.bgl Select the ILS editor Enter ICAO and runway/ILS ID Select Align LOC and Get from AIRAC data ( unless noted as offset ) Commit changes and edit reciprocal runway as required. Alternatively you can update the whole sim easily using the World FSXP3D package available on Herve's site

Is this P3D, addon scenery or default ?

AIE v3.15 If P3D default you'll need to open the \Scenery\0701\scenery\APX56150.bgl to access UKOO. Alternatively use the World FSXP3D package, for P3Dv5 you will need to request the package via email from Herve.

Your scenery is likely outdated John. If using an FSX/P3D platform then these can be updated with an afcad editor such as ADE or easier still with Herve Sor's Airport Inspector and Editor , the latter using current AIRAC data. Having made the change update the EFB database.

@PeterDa the afcad has been modified to ensure ai traffic depart at the E5/7 intersection rather than full length.

I cannot replicate the issue here but then again I do not use ONEDRIVE for my sim files. Onedrive is not recommended:

Which simulator platform, what weather source is selected ?

Have you tried rebooting the PC Jaap?

I'm not aware of a change list Ray, however Herve now publishes a spreadsheet of airac ILS data so it would be possible going forward to run a comparison of data. By checking the ILS in AIE it was apparent that the identifier did not match the chart.

The bonus of using Herve's tool is that can apply the airac data including adding/removing and correcting location of the ILS DME that are often incorrect.

Try updating the AFCAD Ray using Herve's airport inspector and editor to correct the invalid IOL identifier which should be IOLB

Having installed the new airac on the server you have run the database builder, imported the airac via the 'update navdata' function and selected which database to be active?

A workaround Ray is to rename that add-on.xml to add-on.xml.off as this is only used to add the scenery entry to the sim upon install. I don't believe a folder containing the word scenery can be excluded from scanning, in this case add.scenery.

Try using one of EFB supported weather programs such as ActiveSky for the source until a fix is available. ActiveSky and FS Global Real Weather appear to function ok.

Quite possibly due to data changes at NOAA/Aviation Weather Center that occurred yesterday.

There is already a running topic with the answer posted by a dev:

For my own instance Simbrief is not used at all, PFPX is used for planning and a copy/paste of the route returns a corrupt T16 airway. A new database has been created, NG 2307 rev1 installed and activated and 'update simulator' run. Route text string: EIDW PELIG DCT KURUM DCT BIBLA DCT GUNSO DCT OMOKO T16 NAVIX DCT ORTIS GCTS The construction of the T16 airway contains incorrect waypoints.

The same issue can be reproduced with the OP's route KSLC EKR DCT LAA DCT IRW J20 EIC DCT SWB DCT HRV Q105 REDFN Y280 CHRGE KMCO, "Could not find airway 'Y280' which contains entry point 'REDFN' and exit point 'CHRGE' " Simulator P3D v5.4 EFB v2 Server and Client Build # 2.3 139 EFB v2 setup: networked EFB v2 setup: custom path Using licensed version If the issue is related to database or procedures: - Navigraph 2307 Rev1 If the issue is related to a certain airport: - NO. Steps to reproduce the behavior: Have imported cycle 2307 via FMS Data Manager and also via manual installer with the same result. On each occasion the data imported and was activated with no error in the dbBuilderLogFile. Tried creating a new database again with the same result

If you are referring to the exported plan to the 777 Ken then it cannot be done. PMDG would remove the SID/STAR on import to avoid inconsistencies with data.

You'll need to check that a fix is not already defined in the EFB airac, it differs to that of PFPX.

I created and named a waypoint H4010 in pfpx to indicate a half degree N40.30.0W009.30.0, you could use N40.33.0 W009.33.0 and name in a similar fashion.

Within PFPX I created H4010 which when imported to EFB:

Via the route data icon and user waypoints and airways, possibly within the user database.