I searched the forum and found some references but no solutions. I installed this addon scenery.....went to make a flight, and RC had no info on this airport. Have been using RC4 for years so know how to rebuild database.Tried renaming AFCAD and even deleting scenery completely, then rebuiding database with no change. EBLG is a FS9 airport, but looking through the RC4 files, I see no reference to it.If there is no way for RC to add it automatically, is there a way for me to add it manually?RickAfter further investigation, I find references to the EBLG airport in the r4.csv, m4.csv, f4.csv files, but not the a4.csv file!

I looked at the a4 file, and edited it with notepad - adding EBLG. I converted the Lat-Lon to decimal, put in the Field Elev, and longest runway, and made the mag dev 1, not -1 as was in the AFCAD. RC4 now recognizes EBLG. I will not know for sure if everythings works until my next flight.Did I miss anything else?Thanks!Rick

1. Be sure you are using makerwys 4.16.2. The a4 file is created from r4. If it is not in a4 then something is not right in the r4 file or there is a bug in processing r4.Since you say the stock airport was missing that would be strange.To insure AFCADS have the highest priority I have created a dedicated folder (H:AFACD2Sscenery) and run this at higher priority (lower scenery library number) than other airport scenery files.If it were a priority problem I expect data was missing in r4,csv.Perhaps an exclude file from your add-on scenery was left around somewhere. Usually after adding and then removing add-on scenery if there is a problem, it can mean the add-on installation placed a modified APxxx.bgl overwriting the FS9 original. This has the effect of modifying stock attributes directly that AFCAD can not. This can apply to runway renumbering and ILS reassignments that require a change to the default APxxx.bgl files. When I install an add-on, if I see an AP file in there I always copy the original stock one somewhere. This technique is messy because if two add-ons replace the APxxx.bgl file, then you have a conflict.

Thanks Ron,I did find that the problem was in an exclude file in scenery folder. For some reason though, that exclude file showed up in AFCAD when I called up that a/p with AFCAD. When I opened it, it showed no runways etc. Renaming that exclude to a xxx extension, alowed RC to build the files correctly, but had the unpleasant effect of adding back in the default buildings. Renaming the xxx exclude back to a bgl file after rebuilding and everythings ok. But the next time I rebuild, the same thing is going to happen.Is there any remedy to this? Why would the exclude file prevent RC from correctly rebuilding the databaseRick

When looking I was not using the latest version of makerwys. I updated it and rebuilt the database with it, and all seems well now.Thanks!Rick

That exclude bgl file probably had a "delete all runways" code in it among other things. It also may have had navaids or other non-visible items.To insure makerwys gives the highest priority to the AFCAD that restores the runways install that AFCAD in a folder with higher priority than the scenery folder for that airport as I stated earlier. When the AFCAD resides in the same folder in the scenery it is sensitive to naming conventions and makerwys may not interpret the priority correctly.In your FS root folder, every time the scenery utility call makerwys it creates a log file called runways.txt. You can open runways.txt in wordpad, do a search/next find on EBLG, and keep going through all the layers of it to see how each file affects the end result makerws produces. In each section the **** lines indicate the processed result for each runway that will appear in the r4 file (if not deleted and replaced by a later section produced by another bgl file). The first lines of each section gives the name of the bgl file producing that section. It is a lot to read but can give a clue if a file priority is a problem.