trisager
Members-
Posts
27 -
Joined
-
Last visited
trisager's Achievements
-
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.
-
Need Some Tech Help Please?
trisager replied to Dougal's topic in EFB v1 (Read only, no longer supported)
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 -
Need Some Tech Help Please?
trisager replied to Dougal's topic in EFB v1 (Read only, no longer supported)
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. -
Need Some Tech Help Please?
trisager replied to Dougal's topic in EFB v1 (Read only, no longer supported)
What is the problem you are trying to solve, Dougal? -
Not seeing the altitude restrictions
trisager replied to chrisv007's topic in EFB v1 (Read only, no longer supported)
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. -
Not seeing the altitude restrictions
trisager replied to chrisv007's topic in EFB v1 (Read only, no longer supported)
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 -
Not seeing the altitude restrictions
trisager replied to chrisv007's topic in EFB v1 (Read only, no longer supported)
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. -
EDDF rwy assignement
trisager replied to ontheair's topic in EFB v1 (Read only, no longer supported)
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 -
EDDF rwy assignement
trisager replied to ontheair's topic in EFB v1 (Read only, no longer supported)
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. -
EDDF rwy assignement
trisager replied to ontheair's topic in EFB v1 (Read only, no longer supported)
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.