Seems the scruffyduck forum (http://ccgi.scruffyd...lus.com/phpBB2/) isn't there now? Hopefully someone here could advise though .. My Fly Tampa scenery for Dubai, OMDB, places the runways in a different position from the default FS9 AFCAD (AP962230.bgl) and for some reason all my ILS landings there seem to favour the default over the FT file. That means that all my ILS landings are way off the runway - if I slew my a/c to the centre of a runway, it is clear that the localizer markers are way off centre (I land in the grass). I have used ADE9x to orphan the ILS settings in the AP962230.bgl file, but having read the section in the manual on this I am not sure what to do with the bgl file that results when I compile the airport. I decompiled a copy of the new bgl file to see what it contains - the ILS frequencies have been deleted but all the other airports in AP962230.bgl have gone too, so clearly the bgl file that ADE9x created is a supplement to AP962230.bgl, not a replacement. But no matter where I place it in the scenery library, high or low priority, it makes no difference to the airport localizers in FS - I am still taken way off centre of the runways on an ILS landing (in the cockpit the localizer is dead centre on the Attitude Indicator as I land in the grass - in which same place I am shown to be in centre of the the runway if I open AP962230.bgl in AFCAD2 - not in the FT AFCAD of course). If I disable AP962230.bgl then the new ADE9x bgl works fine, but that is clearly not how it is meant to work. Could someone please advise me on this? Many thanks, Martin (BTW - posted on this a while back but there was no solution. OMBD ground textures bleed through badly with my earlier file I find. Previous posts here: http://forum.avsim.net/topic/326874-aircraft-land-off-the-runway/http://forum.avsim.net/topic/349413-dubai-omdb-airport-scenery-very-bad-flickering-of-textures/

You really can't orphan the original ILSs in FS9. You can add and change frequencies but not idents or runway assignments. ADE will build a project from stock airport files but not create a new AP file for you since they contain several airports. A file that successfully compiles to a .bgl is put in a new scenery folder at higher priority. I have seen several scenery add-ons that replace the original stock AP files and have as a side effect caused defects in other airports in that covered range. Besides that, if you have multiple scenery projects modifying that same AP file you can get a conflict. In other words, it is somewhat dangerous in my opinion to do that. What you need to do is insure your Fly-Tampa scenery afd type file has the highest priority in FS. You also need to make any other afd type file ineffective by renaming the extension. Many traffic applications put afd type files in your add-on scenery\scenery folder and these can cause a conflict. You can use AFCAD to search for OMDB in FS9. You can open each layer found that shows runways and do file properties to get the full path. (I would not modify any longer any file with AFCAD but it is good for searching.) get the path for each layer (other than stock) and any that do not point to your Fly Tampa scenery should have the extension renamed via Explorer from .bgl to .bgh to make them ineffective. While there also read the ILS properties to see what Fly-Tampa placed in there. If the airport was moved they may have created new ILSs to be used since originals can not be deleted. There is a free utility called makerwys.exe used by Radar Contact to extract airport data. You do not require FSUIPC to run it. I am going to paste below extracted instructions I use to RC users to use it as a diagnostic modified for your use. It can be downloaded from:http://forum.simflight.com/topic/66136-useful-additional-programs/and the exe installed in your FS folder. Run that makerwys.exe directly in your FS9 (or FSX) folder then follow this extract: ----------------When you rebuild the scenery database (makerwys.exe is executed) a log file is created in your FS folder called runways.txt. This is a large file that should be loaded in Word or Wordpad.Search for OMDB. That first section has a path pointing to the stock airport.The rest of the sections are paired with a delete section followed by an add section with each pointing to the scenery folder involved.Repeat your OMDB search. The last pair of OMDB sections is the dominant high priority scenery set which forms the data for RC. The path for each section within that pair should be to your Fly Tampa OMDB scenery folder for OMDB. Any preceding sets for OMDB (except the default) might represent a conflict if they don't point to that same folder. ------------------------ Examine that last add-on section for OMDB and in it you find the various ILS ident and frequency descriptions as part of runway properties that you aircraft (and ai) should see. In addition a data file created by makerwys.exe called r5.csv is created. Use the Open With function to use word or wordpad, not Excel. Here are the lines for the last instance I have of OMDB which I think is default or UT: OMDB,0121,25.266481,55.347000,34,119.770,13137,110.10BDG,197,1.700,25.257076,55.363991,1312,,OMDB,0122,25.262133,55.347549,34,119.770,13143,110.90BDG,151,1.700,25.252722,55.364548,394,,OMDB,0301,25.243311,55.381546,34,299.770,13143,111.30BDG,151,1.700,25.252722,55.364548,394,,OMDB,0302,25.247671,55.380981,34,299.770,13137,109.50BDG,197,1.700,25.257076,55.363991,0,,Here the last character of field two is the runway left or right indicator so in order you have 12L, 12R, 30L, and 30R. The seventh field shows the ILS frequency where B represents back-course, D represents DME, and G represents glide slope. This data is extracted from the scenery that has the highest priority. You can also open up in ADE9X the afd file created by Fly Tampa using Open Airport Direct From bgl and browse to it. You can turn on the navaid view and see how they are loaf out. You can also use List\Navaids to check the idents and frequencies. In this default all frequencies are unique but anyway hopefully Fly-Tampa turns off the back course property anyway which causes a problem where frequencies are the same at each runway end. I'm sure you are experiencing a conflict and perhaps a priority issue. FYI: The link to the ADE forum is http://www.fsdeveloper.com/forum/forumdisplay.php?f=95 and to Fly Tampa:http://flytampa.org/forum/ . Note that OMDB is listed as legacy. If this is a new design released by Aerosoft go to the Aerosoft.com page and select flight sim. Then in the lower left hand column under FAQ and knowledge base register the product. That will give you access to any service pack and knowledge base regarding it. Aerosoft also has scenery forums and something may be there.

Thanks very much for the detailed reply Ron. (I have the old legacy version of OMDB by the way). There are only two OMDB AFCADs in my FS9 setup, the FT one and the default AP file. I have already seen that the runways are in different locations in the two files, but the ILS frequencies are the same. Maybe the easiest thing to do is to change the ILS frequencies in the FT AFCAD - a lot easier than trying to fiddle with the default one. I did change the frequencies (or try to!) of the default AP file using ADE9x and then saved and compiled the airport, but unlike when I use the change altitude tool on occasion, there is no stub file created, just a new bgl file, which doesn't seem to do anything, even when it is placed at high priority (I have an active scenery folder which I use for various exclude/flatten files that need to be at the top of the scenery library to work - putting the ADE9x file there doesn't change anything - FS9 still uses the information in the AP bgl file. I think maybe I haven't fully understood how ADE9x is supposed to work under those circumstances?). The FT AFCAD is in the OMDB folder - should I move it to my high priority folder? I have AES at the very top of the scenery library, i.e. bottom of the scenery.cfg file, (necessary for it to work), then Cloud9 EHAM (if that is any lower, the jetways don't show - had a long thread on the Cloud9 forum about this and this is the only way to have things and have EHAM work), then FSGenesis mesh, then the high priority folder, then everything else... I will try changing the FT ILS frequencies first (though I can't imagine I didn't try that before). I have makerwys.exe - have rarely used it, but will read through what you wrote in conjunction with that too. Thanks again for taking the time to reply in detail. Martin

http://flytampa.org/forum/viewforum.php?f=6 is the Dubai fly-tampa forum. I noticed one topic, not answered, about incorrect ILS frequencies: http://flytampa.org/forum/viewtopic.php?f=6&t=3847http://flytampa.org/forum/viewtopic.php?f=6&t=1973http://flytampa.org/forum/viewtopic.php?f=6&t=1209 If you look at the ILSs in the supplied AFCAD, do they line up with that AFCADs runways? Check their idents and frequencies by using lists/navaids. You can put this AFCAD in your highest priority folder's scenery folder that you created. You can reposition LOC and GS transmitters in FS9. ADE allows you to drag them around or set the location coordinates and direction manually. One of the messages in that forum stated that current charts had different ILS frequencies than the scenery so you need to check those out if you are using current charts. You can change those frequencies in ADE9 to match the charts you have. If you are using nav radio tuning driven by an FMC database, like the PMDG B747s or maybe the 763s, there could be a discrepancy. It is odd that the runways do not line up with stock. The only time I have seen that is when FSX data was used by error somehow or another scenery messed around with the AP file and replaced it for the airports in those areas. Some other scenery installs have changed the magnetic declaration dll file that can affect some modeled navigation displays. There is a pinned topic on the PMDG support forum about this. Anyway, if you are using the package Fly-Tampa afcad at the highest priority all of its properties should dominate. Try a post on the forum there to see if you get a response.

Thanks again for the information. I will look through it for future reference, but for quick I simply reassigned the four runways' ILS frequencies in the FT OMDB AFCAD: I just flew a short hop OIBK to OMDB and all worked fine landing on 30R, so I assume all the others will be good too. I have no idea why the AP962230.bgl data, in the asia/scenery folder, would take precedence over the OMDB AFCAD, but no matter now, it works fine with the changes. Martin