Jump to content

Sign in to follow this  
G-YMML1

FSDT KORD and ILS freq for 10C/28C and 10R/28L

Recommended Posts

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 

Share this post


Link to post
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.

  • Upvote 2

Share this post


Link to post

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.

 

kord_ils_ok.jpg

Share this post


Link to post

Umberto,

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

Share this post


Link to post

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. 

Share this post


Link to post
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.

 

  • Like 3
  • Upvote 7

Bob Scott | AVSIM Forums Administrator | AVSIM Board of Directors

ATP Gulfstream II-III-IV-V

System: i7-8086K @ 5.3GHz on custom water loop, ASUS Maximus XI Hero, 16GB 3600MHz CAS15, eVGA 2080Ti XC Ultra, Samsung 55" JS8500 4K TV@30Hz, 2x1TB Samsung SSD 970Pro NVMe+850 Pro SATA 3, eVGA 1KW PSU

SB XFi Titanium, optical link to Yamaha RX-V467, Polk/Klipsch 6" bookshelf spkrs, Polk 12" subwoofer, 12.9" iPad Pro, PFC yoke/throttle quad/pedals with custom Hall sensors, Coolermaster HAF932 case, Stream Deck XL button box

Share this post


Link to post
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.   

Share this post


Link to post
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 by virtuali
  • Upvote 1

Share this post


Link to post

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

Share this post


Link to post
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. 


Dave Hazell

i7-8700K, 16gb DDR4 3200,  GTX1080Ti, Win 10, P3d V4.5

Share this post


Link to post

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

Share this post


Link to post
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.


Eric Fisher  

 

 

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    2%
    $540.00 of $25,000.00 Donate Now
×
×
  • Create New...