I have a question whether the priority that an AFCAD is given has any influence on how RC / ATC executes it's tasks.I explain the issue:I still use FS Navigator in combination with several other tools and sources for route planning. Today I got aware of that for some airports Fs Navigator doesen't read the addon AFCAD although the FS Navigator database is properly updated. There may be several reasons for this. So far I have noticed that if a taxiway-signs-bgl and/or an approach-bgl reside in the same scenery folder (have the same layer number) as the addon AFCAD bgl, FS Navigator ignores the latter and thus update the database with a combination of the two first mentioned and the default airport data. (the default AFCAD)In order to test the updating process for the FS Navigator database I moved some actual addon AFCADs to a folder with higher priorty than the approach-bgl and/or taxiway-signs-bgl. After the updating the respectivly airports were in acordance with the addon AFCADs. As this is the case with FS Navigator I started wondering about RC and if this makes any difference for RC when running the -Rebuild Scenery DB- ?Regards,Carl

I have a question whether the priority that an AFCAD is given has any influence on how RC / ATC executes it's tasks.

All of the airport data active in your FS is processed by MakeRunways in order to build the data files which RC uses.MakeRunways processes ALL BGL files, in the order listed in the SCENERY.CFG file -- that is from the bottom of the in-program Scenery index to the top. The higher priority layers (higher in FS's list, but a larger Layer number in the CFG file) can add to or change lower priority layers depending on what they contain. There are "deletion" commands in them as well as commands adding new or different things.Within any specific layer there may well be more than one BGL file with data for the same airport. That shouldn't really happen, but it certainly can do. Often one of them only contains deletions, whilst the other contains the additions. This was a real problem in the old days when FS processed the files in file directory order -- particularly because it was difficult for the user to determine that order. I wrote a "DirSort" program to actually sort directories so you could control the processing by naming. Modern versions of FS appear to process the BGLs in strictly alphanumeric order of their filenames in any case, so names of files are still important. However, it also seems to do all the deletions first then all the additions, even if it reads some additions first. I only discovered that recently, and the current version (4.41) of MakeRunways also does that.So, in conclusion, provided that you re-run MakeRunways to regenerate RC's files whenever you change any scenery, RC should be using the same data as FS.RegardsPete

Thanks Pete,everything is actually OK then as long as I ALLWAYS re-run MakeRunways when doing changes, delete or add airport data. Giving some AFCADs higher priority (that is as you stated for those airports that have "too" many airport bgl's,which is the case for the developers using their "own" techniques I guess) in order to have more correct data for FS Navigator is OK as long as I re-run MakeRunways - just to be sure RC gets what's really there.Interesting !Regards,Carl

I also use FSNavigator in conjunction with RCV4. I rebuild the databases in both programs after every addition or change to the FS scenery db. However, I notice that the ILS frequency/course displayed in RCv4 for approach does not always reflect the runway course as displayed in FSNavigator.Any help with this? This is not an attempt to hijack this thread.ThanksDom

The latest makerwys did fix a problem with certain sceneries regarding priority when the afcad file is in the same folder as the rest of the scenery. Be sure you run it from within RC, not directly, so all files are completely processed to the RC database. See the links near the forum top to update it if needed.

I also use FSNavigator in conjunction with RCV4. I rebuild the databases in both programs after every addition or change to the FS scenery db. However, I notice that the ILS frequency/course displayed in RCv4 for approach does not always reflect the runway course as displayed in FSNavigator

I don't know where FSNav gets its data, but you should also note that not all localisers are oriented with the runway heading. Many are slightly offset, usually for terrain avoidance.RegardsPete