PeterDa

18L is in use at the moment for departures. A rough guess is about half of the departures are from the interesection and the other half from the end

Yes, I noticed that AI aircraft were doing that. Not sure how accurate that is. I shall have a look at Flightradar24 the next time I notice that 18L is being used for departures. I would reverse this "improvement" if I only knew how.

The top end of runway 18L (between the end of taxiway E6 and the intersection with runway27/09 is missing. The runway length is given as 2826 m instead of 3400 m. Taxiway E6 doesn't go anywhere. FlyTampa EHAM show the correct situation

It suddenly occured to me that this might be a virus-scanner issue, and ... indeed, after adding D:\Documents\AivlaSoft\EFB\Navdata to my exclusion list, the FIXes now appear.

The Dataprovider correctly identifies the Navigation data folder, and shows the correct AIRAC cycle. If I load a route and then select Modify Enroute and tick 'Fixes' I only see VORDMEs and DMEs, and not the FIXes as shown op page 18 of the manual. Running version 1.6.8.33245 on Windows 10.

Hello Urs, That is indeed the case. I enter a waypoint as 3346S15203E in the "Enter route description" box (my route starts "YSSY NOBAR 3346S15203E..."), and so it apears in the subsequent "ATR Routing" box. In the tabular representation of the route on the Route Setup page it appears as 3346S/15203E. In the .pln file generated by EFB this is represented as: |<?xml version="1.0" encoding="UTF-8"?> | |AceXML Document | | YSSY to KDFW|IFR |HighAlt |31000 |YSSY |S33° 56' 46.00",E151° 10' 38.00",+000020.00 |KDFW |N32° 53' 48.60",W97° 2' 16.80",+000606.00 |YSSY, KDFW |16R |Kingsford Smith Intl |Dallas-Ft Worth Intl | |10 |61472 | | |Airport |S33° 56' 46.00",E151° 10' 38.00",+000020.00 | |YSSY | | | |Intersection |S33° 47' 10.70",E151° 44' 24.30",+000000.00 | |NOBAR | || |User |S33° 46' 0.00",E152° 3' 0.00",+000000.00 |3346S/15203E | The PMDG .rte file generated by EFB contains: |PMDG RTE route exporter 1.20 for AivlaSoft GmbH's Electronic Flight Bag v1.3.2 | |43 | |YSSY |1 |DIRECT |1 S 33.9461 E 151.1772 20 |----- |1 |1 S 33.9461 E 151.1772 20 | |1 |20 |- |-1000000 |-1000000 | |NOBAR |2 |DIRECT |1 S 33.7863 E 151.7401 0 |0 |0 |0 | |33S52 |2 |DIRECT |1 S 33.7667 E 152.0500 0 |0 |0 |0 The .wx (weather) file that ASN generates from the .pln file generated by EFB contains: |YSSY 306@38(2) 301@39(-1) 299@47(-13) 314@52(-27) 310@63(-37) |310@80(-45) 307@85(-46) 302@88(-44) 302@74(-48) 306@47(-70) |NOBAR 306@38(2) 301@39(-1) 299@47(-13) 314@52(-27) 310@63(-37) |310@80(-45) 307@85(-46) 302@88(-44) 302@74(-48) 306@47(-70) |WPT01 306@38(2) 301@39(-1) 299@47(-13) 314@52(-27) 310@63(-37) |310@80(-45) 307@85(-46) 302@88(-44) 302@74(-48) 306@47(-70) Using the parameter as identifier. The PMGD 777 tries to link the identifier on the odd lines of the weather file (YSSY, NOBAR, WPT01) with the identifiers in the .pln file. This woeks for YSSY and NOBAR, but not for WPT01. I hope all this is clear. Best wishes, Peter D.

I generate flightplans in Aivlasoft EFB, and export them to Active Sky Next and to a PMDG 777 route. This works fine, however: the weather file that ASN injects into the ...\fsx\PMDG\WX folder shows lat/long waypoints as WPT01 etc, while the 777 CDU shows them in the lat/long format. This means that they are not recognised when importing the ASN winds aloft (a significant issue on long transoceanic flights). Kostas Terzides on the ASN forum writes "as you can see ASN just reads the waypoint ids and adds this in the exported file (e.g. ATCWaypoint id="WPT20"). Since ASN does not have a database of waypoints it relies on the flight planner to provide the correct ID and lat/lon in these cases and then calculates the weather conditions there. Is there an option maybe in EFB to assign the "Descr" field as the waypoint ID?" Peter D,

Thank you, Jack. That does indeed remove the error messages. Although the Navigraph charts show 08L/26R as a "real"runway, I see from Wikipedia that it is generally used as a taxiway, and only as a runway when 08R/26L is out of use. Peter Davis

Gatwick (EGKK) has runways 08L/26R and 08R/26L. I have just installed UK2000 Gatwick v3, and updated the scenery in the EFB. When I go to Gatwick the Data provider gives the following error messages: Warning - Navdata runway ident 08L at airport EGKK could not be assigned to FSX runway Warning - Navdata runway ident 26R at airport EGKK could not be assigned to FSX runway Available FXS runsways at this airport are as follows: 08R, 26L I don't understand this as the current runway designations are exactly the same as in FSX. The Dsplay unit shows Runway 08R/26L correctly; 08L/26R is also visible, but is grey instead of black. Peter Davis

Hello Jean-Louis, Thank you for your suggestion. Unfortunately it still doesn't work. I can however make it work by adding something like Added 1 after 5550N in which case I see "Added 1" as waypont identification. Active Sky Evolution must be less tolerant than other programmes as far as the structure of the waypoint data is concerned. Peter

Hello Urs, thank you for the feedback. PMDG .RTE files have no problem with them.

I enter the following track into the EFB: KJFK MERIT3 MERIT HFD PUT BOS TUSKY N63B VIXUN MALOT 55N050W 56N040W 56N030W 55N020W GISTI DUNLO DIBAL UL603 LAMSO EHAM If I save this in PMDG .rte format it is correctly read into the PMDG 737NGX FMC. If I save in in FSX .pln format, however, the NATS waypoints are not read bij Active Sky Evolution; this is because the following parameter is missing for these waypoints: xxxxxx Peter Davis

I was consistently getting CTDs with the combination NGX-EFB in FSX. I have now solved this (on the last day of my trial period!) by changing the internal FSX frame rate delimiter from 30 to Unlimited (I don't know if this has any relevance for the SimConnect problem). Peter Davis

Thank you, William. I gather that this fix doesn't apply for those of us running everything on one system. Unfortunately SP1 hasn't solved this problem voor me.

Wanting to try the simconnect.xml modification, but no such file is present in the directory with fsx.cfg (in my case C:\Users\Peter\AppData\Roaming\Microsoft\FSX), and -yes, I have turned on "show hidden files". Any suggestions? - Peter D.