I have a small number of 'AFX_****.bgl' type AFCAD files which have errors and I want to correct them: for the moment though I have only AFCAD2 (waiting for a new PC to be installed before I purchase the AFX tool itself), so cannot edit the files directly without losing information. I am able to correct faults, but only by creating a corrected (AF2_) copy of the AFX AFCAD, and saving it somewhere which has a higher priority than the original.My question though is, are both AFCADs - the AFX original and my AF2 'dummy' - used by FS9? In other words, as my AF2 file has a higher priority in FS9 than the original AFX AFCAD, will the latter still be read and the data in it used? I assume yes, as that is what happens with stub files (to change altitudes in default airports, for instance), but maybe someone can give me a definitive answer.Apart from the small corrections I make, the AFCADs are identical otherwise, so there won't be conflicts of taxiways, parking etc. No other repercussions though I haven't foreseen, are there?Once I buy AFX this point will probably be superfluous, but I'd still like to know.Thanks,Martin

Martin.Save your money and get ADE9X for free.It's SDK compliant, easy to use, free and available here- http://www.airportdesigneditor.co.uk/To answer your question, if you have multiple Afcads that have the same ICAO and the same reference point FS will not crash.FS will use the higher priority Afcad.If you de-compile an Afcad the first thing you will see at the top is (basically) delete the lower priority airport(s).Stub Afcads are different in that they are used to deal with a specific quirk in the way FS9 processes airport elevations.Yep, save your cash, get ADE9X. You will not regret it.regards,Joe

Joe,Thanks for the reply. I've had ADE9X installed for some time - I use it to change elevations and one or other things it does (I admit, I really UNDERuse it!), but can it save AFX type AFCADs without losing information, in the same way as Flight1's paywre AFX? I must look at it again, clearly.Martin

My question though is, are both AFCADs - the AFX original and my AF2 'dummy' - used by FS9? In other words, as my AF2 file has a higher priority in FS9 than the original AFX AFCAD, will the latter still be read and the data in it used? I assume yes, as that is what happens with stub files (to change altitudes in default airports, for instance), but maybe someone can give me a definitive answer.

That is a definitive yes.The AF2 at the higher level will only modify the features contained within it. The other features in the AFX file will not be affected.The one thing to watch carefully when using multiple A&F Data files is to ensure the airport co-ordinates are the same in all files, otherwise there can be problems when the airport comes into range of your aircraft and loads the AI traffic, resulting in a FS software crash.JohnPS like yourself, I have ADE9 and use it occasionally but I must admit I do not find it "easy to use" as Joe says and generally find easier to drop back to using AFX for quick and dirty changes. But there is no disputing ADE9 has more features, such as building placement, and I suspect I haven't yet learnt half of what it can do.

That is a definitive yes.

How about a definite maybe.To test I took an AFX file that contains taxi signs.With the original AFX at a lower priority I placed a copy of it at a higher priority.I opened the higher priority AFX copy with AFCad 2.21 and deleted a taxi link, then saved.I went to visit the airport and not only was the link gone, so were the taxi signs.As for comparing ease of use between AFX and ADE9X, I cannot, never having used AFX.I prefer not to pay for non-SDK compliant software when there is an SDK-compliant freeware alternative.All software has a learning curve and at first I was challenged by ADE9X. After time I have become accustomed to it in spite of it's few minor flaws.I do know Jon has about 8 or 9 pages of suggested changes for the next version at fsdeveloper.com that he is working on, when was the last update for AFX?I am not trying to start a flame-war, simply offering alternatives.Martin, if you make your changes to AFX files with ADE9X instead of AFCad2.21, I believe you will have a better chance of success.regards,Joe

Sorry for the extra post, the phone rang, the dog started barking at who knows what, and the thought train went screaming off the tracks.

.. ADE9X ... save AFX type AFCADs without losing information, in the same way as Flight1's paywre AFX? I must look at it again, clearly.Martin

Yes.I completed the same test described above with ADE9X and the link was gone, yet the taxi signs were still there.AFAIK ADE9X will only have problems working with AFX files if they contain non-SDK compliant info. An example, we can have AI floatplanes in FS9 if we create 0 width concrete runways in the water. Because AFCad uses a compiler other than the SDK-compliant BGLComp, it will compile a water airport with 0 width concrete runways.If you open a seaport with ADE9X that was created in AFCad with 0 width concrete runways, make changes and try to compile it, the compile will fail. It does so because ADE9X uses BGLComp, which requires concrete runways to be at least 3 feet wide.I do not know how AFX will handle this, but suspect it would compile that water airport, based on what I have read.I keep AFCad around for that purpose because seaports are always quite basic for me, only occasional comms, no navaids, approaches etc.Hope this helps.regards,Joe

I meant to say (and forgot) that, before saving the original AFX file as an edited AF2 file, I deleted all the parking spots/gates, thinking that the file should be as 'minimal' as possible and that the original AFX file would cover what I had deleted. Then, as I said, I put the new AF2 file into a folder that is at a higher priority than the AFX AFCAD. Opened up the airport (YBBN) - where's all traffic gone?!! Reset traffic to 100%. Still no AI a/c - all gates empty. So I removed the new AF2 file and restarted FS9. Now I got a CTD every time I tried to go to YBBN - great!! Rebooted the PC, and then, all OK, no CTD (odd). With my AF2 file removed, Brisbane was full of aircraft again. So I redid my AF2 file, but removed nothing - just made my correction to one of the aprons and then reinstated it as before.Now all is fine, though I am not sure yet if I have lost features of the original AFX AFCAD, given my replacement is also active again.I will try editing the original file with ADE9X a bit later, a much better solution - and report back with any results.Martin

Typically ADE9X will cause things it "knows about" to be deleted from lower scenery layers, like taxi signs.

How about a definite maybe.

OK, I'll go with your "definite maybe".I have had numerous people contact me about my distributed AFX files and their desire to change them; all of those that reported back assured me that method worked perfectly. I guess the key factor for them would have been the retention of the "excludes" in the AFX file and may not have noticed the loss of taxiway signs.The true answer for Martin is to try it for his particular situation, of course, which he has.Note for Martin - I would expect the act of deleting all your parking spots to over-ride the lower layer because that is an item you have changed. You should only change what you need to change.Best wishes,John

AFCAD 2.21 has certain automatic excludes built in without option. It was developed before all of the MSFS SDK information was published (and some still withheld).While the major developer departed a fresh approach was taken by some members of that team starting the ADEX editor for FSX only and then a multiple FS version project for ADE9X.I opened once an AFX produced afd file in ADE9X and it showed expected objects and also exclude polygons where certain types of objects of lower layers would be deleted. In ADE9X you can delete (or add) the excludes by area and class of objects as I recall. Of course, with flexibility comes a higher learning curve but it is not too much more difficult to accomplish the same feats than with AFCAD or AFX. ADE9X also includes an approach editor tool that if you add a navaid to a runway creates an editable approach for AI to follow. ILS and other navaids added with AFCAD will not be recognized by FS9 AI nor show on its GPS or map but when added with ADE9X will show and be recognized by AI. This is helpful to update airports where new runways have been added. The now integrated approach editor was created by Jim Vile and you'll see for some airports scenery files regarding added navigation and approach facilities for new runways.ADE9X is freeware and if nothing else use it as an inspection utility. Manuals, tutorials, and the utility are available from here:http://www.scruffyduck.org.uk/filemanager/navega.php?id=2&PHPSESSID=568bb71cef7e6255f1870be7e1a935e5

At first, I managed to repair the small fault in the AFX_YBBN.bgl file ('torn' taxiway due to misplaced node) using ADE9X. I hadn't realised that the programme uses stubs for all changes to airports - it seemed to work very nicely. Then I made a few adjustments, (doing just what I did first time) and now the 'repair' no longer works. FS9 shows that the database is being compiled each time, so the bgl file is active, but the error is still there at the airport. I've tried a dozen times, to no avail. Worked once and then - nothing. Very annoying!! Tried putting a small patch of apron over the tear: in FS9 that just changes the shape of the tear. Maddening, especially after being used to AFCAD2 working like a dream every time.I find the ADE9X interface less intuitive than in AFCAD2: the tear in the runway looks to be fixed in the ADE9X window, but 'what you see' is not necessarily 'what you get' apparently: when I run FS9 the tear is still there, in spite of ADE9X showing otherwise. And why when I click on anything in the airport does the whole screen turn yellow? How do I 'grab' the side of an apron like in AFCAD2? Maybe I need to go back to the manuals...Not sure what to do now - go back to my 'pre-ADE9X solution' I suppose.Martin

Hi,Wherever you are placing the compiled BGL file from ADE9X must be in a higher scenery layer than the original BGL file, if you have left it in there. It cannot exclude the previous file if they are present in the same scenery layer, or the original is in a higher layer than your new BGL.Note also that FS9 and FSX have some drawing bugs that may not be reflected in the ADE9X display. You may have to add extra nodes and/or change the drawing surface type for various taxi segments to avoid these.Hope this helps,

Yes, I am placing the stub in a scenery folder with higher priority. It worked once, as I said, then not again. Tried ten times - but I've now given up. A bit disappointing..Martin

Not sure what you mean by stub, this typically refers to an elevation correction stub Afcad placed in Scenery\World\Scenery.If you are using ADE9 there is no reason to have 2 active Afcads unless you are changing the airport elevation.Open the AFX .bgl in ADE9, make your changes, save the file as an .ad2 (this is not compiling anything), then compile.Move the AFX .bgl out of any active scenery folder and use the ADE9 .bgl.If you want to make further changes, open the .ad2 file, not a .bgl file, make changes, save and compile.Hope this helps.regards,Joe

Joe,Thanks again, but this is exactly what I have done a dozen times now - open the saved airport, compile after correcting and re-save. No matter where I put the new bgl file (YBBN folder or a higher priority one) no correction is made in FS9, even though it appears that it has in ADE9X before I save and compile. I've tried having the ADE9 and the original AFX files active (?) and, as you say, just the ADE file - the error is alwsys there. I really don't understand what's wrong. So I've just put my original duplicate AFCAD back, which does correct the taxiway error. Not an elegant solution, but it works at least!Martin :(