I've checked a couple of AFCADs from the bunch released from UT and there are no navaids listed. NO ILS's at all. I flew into KDTW this evening fo the fly-in, and had no ILS to fly to. Anyone else notice this?Do all the UT AFCAD's have to be fixed?

There was a discussion on the PAI AFCAD forum that the current version of AFCAD2 which creates the new format bgl airport afcads does not store navaids. I do not use UT, but I have used AFCAD2 to add gates to a default airport and third pary scenery as well. In FS2K4 the navaids were kept intact from the stock (base default) airport.If the base airport was deleted, you would then be missing the navaids. AFCAD2's navaid property modification is awaiting the release of the appropriate SDK, unless Lee Swordy figures it out by then per his own words either I saw posted or in the AFCAD2 docks.

Well, I was using an add-on Detroit scenery. But, I haven't had problems with it before. How it happened, I dialed in the ILS for 21L. Well, as luck would have it, 3R is the same frequency, different identifier. No matter what I did, couldn't get it to come over to the proper id. I would've had to fly a localiser backcouse, which of course there isn't a published one available. When I checked the AFCAD file, there were no navaids listed.I noticed there were no NAVAIDS for some other AFCAD releases, not just UT. If the base AFCAD contains navaids, which they do, would this establish that NAVAIDS are in fact available and not just being "supported" by whatever panel you are using?Since i was using PMDG NG, might the problem be with that panel?

We are talking about FS2K4 and AFCAD2, right? I just want to be sure.It is possible with "directional" antennas to use the same localizer frequencies with different localizers on each end of the runway.Open up AFCAD2, if you do not have it download it. Enter the ICAO airport code when the dialog box opens for Open Airport -- Sear for airport and execute the search. If there is more than one bgl file for that airport it will list stock and then the others. Highlight the stock code and open it. Under lists choose NAVAIDS and they should display and you should be able to tune them with at least regular NAV radios.The other non-stock bgl files, which now replace the AFD files as such that were used in FS2K2, will not show NAVAIDS for now, nor save them, until AFCAD2 is updated.I use KMSP and look at the 12/30 parallels to see what I am talking about in the stock version.If the stock version is not listed in the airport search results, then somehow it has been removed by exclusion or elimination and you will not have NAVAIDS at that airport for panels that use that info.

Others are seeing this too - only one side of an ILS will work, the other will be back course.When AFCAD 2 supports navaids hopefully we can modify this.Hope this helps,--Tom GibsonCal Classic Propliner Page: http://www.calclassic.comFreeflight Design Shop: http://www.freeflightdesign.comDrop by! ___x_x_(")_x_x___

With the combination of certain runway properties in FS2K4, I wonder if there is any relationship (erroneous) between the permissive landing properties and enabling of the landing NAVAIDS.

I just rear the part about AFCAD not saving navaids. Is this the reason when I give a runway an ILS freq it will not be there when I restart FS9?jgant