trisager

Has there been any indication at all that PMDG is going to do anything in this area? I don't recall reading anything at all by anyone from PMDG on this topic.

... unfortunately this is only a temporary fix, at least on my system. I only see the traffic that is in the vicinity of my airplane when I start EFB. Traffic that I encounter later during my flight does not appear - unless I shut down and restart EFB.

Thanks for this tip, seems to work very nicely.

The NGX definitely does something unusual with simconnect, but PMDG isn't saying what or why. There is obviously a lot of clever programming in that product, and unfortunately it seems that at least one of their programming tricks makes it hard to coexist with for other simconnect users. Since the Aces team isn't around anymore, a solution would have to come from either Aivlasoft or PMDG. I don't know how likely that is - it might prove difficult or impossible to fix this.

It has been a while so I could be wrong, but as far as I remember FSCommander uses the Wideclient interface, not simconnect. That would explain the difference.

Yes, unless you invest in addon scenery for the airports that interest you the most. Fortunately for us, building new runways and such are expensive undertakings, so it doesn't happen on a daily basis

OK, if you use default KBOS scenery, put the following in your Runways.txt file: KBOS 15R 15R KBOS 33L 33L KBOS 04R 04R KBOS 22L 22L KBOS 04L 04L KBOS 22R 22R KBOS 09 09 KBOS 27 27 KOBS 15L 15L KBOS 33R 33R KBOS nil 14 KBOS nil 32 That gets rid of the error message about runway 14/32 which exists in real world, but not in default FSX scenery.

What is the problem you are trying to solve, Dougal?

I think you are right. The WAATS3 RNAV STAR into KSLC has an EXPECT 17,000' at KNOLE which is not in the Navigraph data. It also has an "At or above" 14,000' at WAATS and an "At" 12,000' at RAACE and DUGGY, and these restrictions do show up.

The NGX navdata has the same issue with the BULLZ1 STAR - no crossing altitudes. Not terribly surprising since the PMDG and Aivlasoft procedures are compiled from the same source data

Have you tried at other airports and/or other STARs? At most of the airports I've flown into using EFB the altitude restrictions have been present and accurate. Navigraph does a really good job of supplying navdata to us simmers at a fraction of the cost to real aviators. They are not infallible, though.

You most definitely did - I sincerely hope you are not accusing me of "doctoring" that quote? Maybe I was responding while you were still editing your post. When I load the default FSX EDDF, I cannot see all the eight runways that you mentioned in your original post - 07L 25R 18 36 26L 08R 07R 25L - hence the question about scenery. The ones I see in the "Choose runway/starting position" are 18, 25L, 25R, 36, 7L, 7R which correspond to the three physical runways at the airport. Maybe someone else can compare with their FSX installation. I have not seen any ill effects from leaving out rwy 36 from "Runways.txt", but for completeness you can add EDDF 36 36 / Tom

What scenery do you have installed for EDDF? FSX Default? "Runway 36" only exists in the sense that it is the opposite end of rwy 18 Take a look at it in Google Earth and you can see that it has none of the threshold markers, numbers, touchdown zone markers, or tyre marks that you find on a runway that is in use. Runway 18 is only used for southbound departures, not landings.

Runway 07L/25R have been renamed 07C/25C (a new runway is under construction to the north-west of the current airport). You can fix the issue with the scenery by adding the following lines to the Runways.txt file in the Documents\AivlaSoft\EFB\UserData folder: EDDF 07L 07C EDDF 25R 25C EDDF 18 18 EDDF 07R 07R EDDF 25L 25L Runway 36 is not in use.

Another example is Coffs Harbour - YSCH in FSX, renamed to YCFS in the real world. I've come across a few others that I don't remember right now. ORBX chose to keep the incorrect YSCH for their addon airport - probably to avoid having both the old and the new one in the scenery library. Something similar to the "runways.txt" for renamed airports would be nice.

Thanks - I was having the same issue, but deleting the EDDP lines from runway.txt and restarting the data provider fixed it.

Did a quick try on my setup - answer is yes to the above.

The problem is in the navdata. In the real world this runway has been closed, and FSX is correct in this respect. However, if you look in the FSX\AivlaSoft\NavData\wpnavapt.txt file and search for Brandon you will see that it still lists rwy 02 and rwy 20. Other than the error message this does not cause any problems, but if you want it fixed the right place to post about it is on the Navigraph forum.

They don't exactly make it easy for addon developers, do they The files must be linked somehow, since rwy 12/30 still shows up under YSCB in FSX. I'll ask about it on their forum. Tom

Thanks for pointing me to the update, Urs - I did not have it installed. However, it doesn't change anything to this particular issue. No big deal - and I realize it must be difficult to troubleshoot without having the scenery available. Tom

Hi Urs, I didn't edit the "Runways.txt" file, I'm not sure how I would do that in this particular case? My problem is that runway 12/30 exists both in FSX and in the real world and the runway designations agree, but somehow the runway is not recognized by EFB. Tom

Hi - I'm having a problem with a missing runway 12/30 at Orbx Canberra. The data prover says: Request for Airport [YSCB] from '192.168.1.103' received. Navdata runway ident 12 at airport YSCB could not be assigned to FSX runway. Navdata runway ident 30 at airport YSCB could not be assigned to FSX runway. Available FSX runways at this airport are as follows: 17, 35 However, the runway exists - both in the real world and in the sim (i.e. in "World" > "Go to airport" I can select 12, 17, 30, and 35 as starting positions). Any idea how to fix this? Tom

It opens a Foxit window - it doesn't display the .pdf in the browser? Maybe that's a problem. Try going into the "Tools" > "Preferences" menu in Foxit and select the "File Associations" tab. Make sure there is a checkmark in "Display PDF in Browser" and try again.

There is nothing special about Foxit Reader - I use it with EFB with no problems. (I don't even have the Adobe reader installed). What happens if you try to view a .pdf file in your browser - does that work? Tom

I seem to recall getting that error message when updating FSX scenery that included the OZx Australia freeware. Disabling OZx allowed the update to run to completion.