Hello!

I have noticed recently that neither PMDG birds nor FSLabs buses pick up the frequencies for the above-mentioned runways. I have no duplicated AFCAD, no other sceneries, Navigraph DB is 2001. Meanwhile, it turns out that new KORD runways inherited freqs from old and currently demolished pair of 14/32s. Umberto (as always) denying any FSDT involvement into this issue and I'm too lazy to argue with him as it's been a same old song for the last 15+ years.  

Please position your PMDG/FSlabs plane at either 28L or 28C, tune up ILS freq and please (pretty please) post a screen of your left PFD. 

Would appreciate your help as I'd like to know whether it's solely my problem or the scenery's problem.

Thank you!!!

Dmitriy 

50 minutes ago, G-YMML1 said:

Meanwhile, it turns out that new KORD runways inherited freqs from old and currently demolished pair of 14/32s. Umberto (as always) denying any FSDT involvement into this issue and I'm too lazy to argue with him as it's been a same old song for the last 15+ years.  

I really don't know what you are trying to say here. I'm not "denying" anything. I provided EVIDENCE that:

- The ILS WORKS with two different default airplanes, the default 737 and the default Mooney Bravo. 

- The AFCAD that comes with KORD V2, opened with ADE ( so everybody can check it too ), has all the correct frequencies. In addition to that, opposite to what you said the scenery "inherited" the frequencies for the old 14/32 runways, it clearly doesn't. By opening the AFCAD with ADE, one can easily see that all ILS that don't exists anymore, like the 14/32 that USED to have the frequency now used by the runways, have been *changed* and correctly orphaned in ADE, which is the correct method to replace an ILS.

For example:

ILS 32L doesn't exists anymore, and it *used* to be on 108.95, with the I-RVG ID. This frequency in real life now belongs to 28C with I-VZE ID. And of course, in the FSDT KORD V2 AFCAD, the ILS has been corrected as follows:

I-RVG now is moved to 108.00, orphaned from the non-existing runway, and renamed as "DO NOT USE". 

I-VZE has the correct frequency 108.95, and is associated to the correct runway, 28C

So, if you tune 108.95, and still get the old 32L ILS, it's NOT coming from the FSDT KORD V2 AFCAD, because we moved it to 108.00 and the only ILS set to 108.95 is the one for 28C.

Here's a screenshot from ADE with the AFCAD that comes with FSDT KORD V2 opened. The first lines shows the now defunct ILS, which has been all orphaned and moved to a different frequency, and it clearly shows the ONLY ILS using the 108.95 frequency ( for example ) are the new ones for 10C/28C.

 

And here, a screenshot showing ILS 28 C correctly working with the PMDG 737 NGUx. The frequency is correct at 108.95, and the ND shows the correct ID for 28C IVZE

Umberto,

Which software did you use to create orphaned ILS - AFX or ADE?

ADE, of course. AFX, as far as I know, has never been updated to fully support P3D4. See my last post, showing the 28C ILS working fine with the PMDG 737 NGUx

Ok...I suspect that I have a very first version of ADE without orphaned ILS as I immediately created my own custom AFCAD once the scenery was released and I intentionally have never updated the ADE file since then. Gotta test this theory once I get back home later tonight. 

29 minutes ago, G-YMML1 said:

Ok...I suspect that I have a very first version of ADE without orphaned ILS as I immediately created my own custom AFCAD once the scenery was released and I intentionally have never updated the ADE file since then. Gotta test this theory once I get back home later tonight. 

The very first versions of ADE long predate P3D.

Now let me see if I've got this right...you took the FSDT O'Hare, then modified it, possibly with a program that isn't up to date, then it didn't work, and then you lampooned the developer with "Umberto (as always) denying any FSDT involvement into this issue and I'm too lazy to argue with him as it's been a same old song for the last 15+ years."

Frankly, I think the guy is a saint for answering this complaint at all.

 

20 minutes ago, w6kd said:

The very first versions of ADE long predate P3D.

 

 

ADE File!!!! not ADE software. 

If I were told specifically that Navaids for KORD were modified after the initial release, this entire discussion would never have taken place. Yes, I do not update ADE files via FSDT Updater as I'm not satisfied with the quality of parking codes/wing span  + I'm applying my own system of runways' utilization for AI usage, hence I'm creating my own ADE files.

Instead, I have been told "here is the screen of PFD, we have everything working on our side". All I wanted to see is the second screen with the list of Navaids. With that information I should be able to add orphaned ILS by myself. In order to get a real help finally I had no choice but to appoach AVSIM forums as I haven't gotten any help via FSDT support forums.

Anyway, the problem has been solved. Thank you Umberto, hope it won't go that far in the future.   

1 hour ago, G-YMML1 said:

If I were told specifically that Navaids for KORD were modified after the initial release, this entire discussion would never have taken place. 

That's only because, when we updated it, you chose to IGNORE the AFCAD update ( which the Live Update alerts you of ), and never bothered to read the release notes when that fix was released:

https://www.fsdreamteam.com/couatl_liveupdate_notes.html

September 10th 2019

• Bugfix: KORD V2 - Fixed ILS 28C ID to be IVZE (not IVEZE).

Quote

Instead, I have been told "here is the screen of PFD, we have everything working on our side".

Because that's exactly what's happening.
 

Quote

All I wanted to see is the second screen with the list of Navaids.

You said yourself you modified the AFCAD, meaning you must know how to use ADE. And that "second screen" it simply the list of Navaids from ADE, so you could have obtained that information yourself, when checking the file, which should be the first thing to do, when reporting a supposed bug in the scenery related to Navaids, especially when you knew you modified the file yourself!

Edited January 10, 20206 yr by virtuali

I too have this problem. 28C.  I posted the issue on FSDT and per  Umberto's suggestion, I tried the default Bravo and that too did not pick up  the signal.  I said it must be the scenery, not blaming Umberto for anything.  It could be on something on my end.  I opened KORD with ADE and the frequencies are correct.  I opened the map in P3D, and that shows the correct frequencies same as ADE.  So what could be the issue?  It's working for Umberto and countless others because these are the only complaints I have seen on the forums.

Gnacino

2 hours ago, Gnacino said:

So what could be the issue?  It's working for Umberto and countless others because these are the only complaints I have seen on the forums.

 Run live update and let it update your ade for KORD. 

That was done countless times, thats not the issue.  It's got to be a scenery issue, either with my setup or something else.  The AFCAD is correct, all of the obvious has been checked.  Don't know what else to look for.

Gnacino

24 minutes ago, Gnacino said:

That was done countless times, thats not the issue.  It's got to be a scenery issue, either with my setup or something else.  The AFCAD is correct, all of the obvious has been checked.  Don't know what else to look for.

Gnacino

Could be a node issue with the updater. When FSDT pushes an update out, there vendor is, in theory, supposed to push it out to all 170+ nodes worldwide. As has happened before, sometimes that does not happen. So you run the update thinking you have the update when in reality you don't get the update. Got to love the internet.

deleted

Edited January 12, 20206 yr by MDFlier