Good afternoonI recently purchased London City Airport X from Aerosoft. I ran the appropriate rebuilds as required. However when I build a flight plan, RC does not pick up EGLC as the departure point. I checked the scenery file, and there appears to be a AFCAD.I compiled the plan using first FSCommander, then FSBuild and then FSX. Each time RC did not have a departure airport.What file does RC look for to accept the flight plan. I was wondering if the AFCAD format supplied with the product has someting to do with the issue. many thanksLaurie

I recently purchased London City Airport X from Aerosoft. I ran the appropriate rebuilds as required. However when I build a flight plan, RC does not pick up EGLC as the departure point. I checked the scenery file, and there appears to be a AFCAD.

I had this problem with Aerosoft's recently released Monastir X. I searched the MakeRunways log ("runways.txt" -- you'll find it in the mainFS folder) for all instances of its ICAO (DTMB) and saw that there were actually three AFD type BGL files in the Monastir X folder. Two appearently identical but with different names and dates, and one containing only the same deletions as the other two and no runways, taxiways, etc.They got installed in alphabetic order, which unfortunately made the one with only deletions the last, effectively saying "delete all the stuff just installed by the previous two"! So I deleted the older of the two identical files and the unnecessary deletion file, re-ran the scenery update, and everything was fine.So, I am guessing that the EGLC install might have done something similar. Search the runways.txt file for EGLC and see if there are active successive AFDs which cancel each other out. The log gives the exact location and filenames, and the log is the actual order they are processed by MakeRunways and FS itself.Note that the runways.txt file contains all of the information from all of the active AFD data in your system so it will be rather large. WinXP and later editions of Notepad should cope (eventually), but a more efficient editor would be better. I use UltraEdit.RegardsPete

Good evening PeteThanks for your replyI opened the Runways text doc, and sure enough down the bottom was the EGLC runways. However there was reference to other files that again you mentioned.Would you be kind enough to have a look at this attachement, which is just the last of the text file as I'm not sure what I should be removing. At least I'll know what to look for if it happens again.Oops not allowed to upload a word file. Anyways I will try the one that looks the problem.thanksLaurie

Would you be kind enough to have a look at this attachement, which is just the last of the text file as I'm not sure what I should be removing. At least I'll know what to look for if it happens again.Oops not allowed to upload a word file. Anyways I will try the one that looks the problem.

Don't actually delete anything -- just rename it. I just change the "l" in "bgl" to an "x". That's enough. Then you can always undo what you've done very easily.If you want me to look at something, ZIP it up and send as an attachment to an email: [email protected]

Here's how to prioritize the correct file:Create a folder called AFDs somewhere on your FS drive but not under your FS folder. Under that create as scenery folder. Move (not copy) the file indicated in runways.txt that contains more than just the deletions into this new folder AFDs\scenery preferably the one with all of the runways, gates, taxiway points, etc. The file names and path are in runways.txt.Open FS and go to settings/scenery. Use the ADD button to browse to the new AFDs folder and OK it. It should go to the number 1 position in the library listing. OK every thing. If FSX requires a restart to reindex its scenery do so. After it is done close it.Now go into RC4 and run the database builder from within. When complete close RC4.Go back into your FS folder and open runways.txt in Notepad. See if the last section for EGLC now has runways and taxi points, etc. To reinsure the RC database is correct go into your RC4\data folder. With Notepad, not Excel, examine first r4,csv. Search for EGLC and you should have a line for the runway. Close Notepad. With Notepad now open a4.csv. Search it for EGLC and there should be a line for the airport. Close Notepad.If r4.csv and a4.csv have entries for EGLC you should be good to go.The file that resulted in deletions only I'd leave as is in the EGLC scenery folder as sometimes there is navaid information in it.In the future if you have similar scenery problems you can move the appropriate .bgl file into that new AFDs\scenery folder and start FS so it reindexes, shut it down, and then run the RC4 scenery database rebuild.I'm an FS9 user and this procedure has worked for me. FSX is similar.

Thanks RonThat worked like a treat. Do you do this for all AFCADS or just the major ones like UK Extreme Airports or Aerosoft portsI named the folder AFCADUK just in case I want to seperate the AFCADS by countrymany thanksLaurieOh Ron just a thought here. What about FSCommander DBManager that reads the airports from only within FSX. What would be the result by moving that AFCAD folder back in FSX outside the AddonScenery folder.

Many freeware and payware add-ons to work around FS limitations have more than one AFD type file in their scenery folder. This method insures that the proper file gets priority.FS9 users can use AFCAD221 freeware to look at each layer as a diagram rather than search runways.txt. FS9 and FSX users can inspect them using the more complex ADE9X Airport Design Editor ( http://www.scruffyduck.org.uk/filemanager/...99c08bfef75fb17 ) or the payware AEX for both FSs.By the way, if you have a traffic package that adds its own afcad or afd files, be sure you do not have both that and your add-on airport afcad or afd both active to insure there is no conflict. Just rename the extension.With regard to your second question, many types of add-ons that form a database from scenery use the scenery.cfg file formed by your library settings. That's what we were changing in this procedure. It should therefore not be necessary to move back the afcad\afd files into their main scenery folder. If you do, you risk losing the data fix when you do the next scenery rebuild. Many scenery add-ons directly manipulate the scenery.cfg file during installation using an .exe install so it never hurts to check the FS library order after running the scenery installer and apply this fix if necessary. If you have trouble you can move the AFD/AFCAD folder back into ADD-ON scenery if necessary but still insure you place that folder in the first place of the scenery library settings list. A well designed add-on database builder will use the index provided by scenery.cfg so you should not have to do this. Glad this worked out for you.

Thanks RonThat worked like a treat. Do you do this for all AFCADS or just the major ones like UK Extreme Airports or Aerosoft portsI named the folder AFCADUK just in case I want to seperate the AFCADS by countrymany thanksLaurieOh Ron just a thought here. What about FSCommander DBManager that reads the airports from only within FSX. What would be the result by moving that AFCAD folder back in FSX outside the AddonScenery folder.