Hi. Usually, if I have this problem I can fix it by opening the relevant AFCAD in AFCAD2 and, after selecting to make Navaids visible, dragging the green triangles so that the localizer is in the centre of the PDF LOC scale when the a/c is on the centre-line of the runway.In this instance though (3rd. party OMDB), that hasn't worked. Rather than use the navaid information in the OMDB AFCAD that comes with the scenery, the navaid information in the default file (AP962230.BGL) is being used. If I remove AP962230.BGL then all is well (but I assume this is not a good idea!! Especially as the file contains information for other airports!). So I tried editing the AP962230.BGL file - I decompiled it to an xml file and edited that in notepad and saved it. But the xml file (even the unedited one) refuses to recompile to a bgl file - too many errors come up.So I next tried creating a stub with Airport Design Editor, but this is not working either. I tried opening AP962230.BGL and then (under lists/navaids) unchecking the Glide Scope and DME boxes, but that didn't change a thing. So I reset all the navaids to 111.95 (totally different from the frequencies in the OMDB AFCAD file). That worked, (up to a point - read below) but only if I activate the stub file higher than the OMDB scenery - but doing that causes a lot of default FS9 scenery (terminals etc.) to appear. If I activate the ADE bgl file lower than the OMDB scenery it has no effect. (I also noted that, even when activated higher and 'working', the file is very, very sensitive. If I nudge the a/c just a foot or two to the left or right of the centre-line, the localizer indicator on the cockpit PDF shoots way off to the right or left, totally disproportionate to how much I moved the a/c - so that's not going to work during approach).I then deleted all default Navaid info in the stub file - Tools/Remove Stock Data/Navaids & Waypoints. I deleted the ILS green triangles too - I get the warning about not being able to delete and agree to orphan the ILS - and then in 'Approach Mode' deleted all the Approach info too.The end result is that I do get the ILS centred on the runway, but now when I load up a flight at any of the OMDB four runways, FS9 is using the data from the stub file/default airport for the runway information/start points, and the flight starts with the a/c aligned not to the 3rd. party runways, but the default FS9 runways (I can see this when I open the AFACDs in AFCAD2).So I am back to where I started in effect - I have corrected the ILS problem but in doing so have created far worse 'evils'. Has anyone got a better idea - I feel I should be able to do this with ADE9x, but whatever I have done so far is clearly not right.Thanks,Martin*** LATER ***: Managed a sort of 'sticking plaster job' - placed the ADE9x stub to AP962230.BGL (with all navaid/approach details deleted and the ILS green triangles 'orphaned', as ADE9x puts it) in a folder with higher priority than OMDB. I then opened the stub file in AFCAD2 and moved the start positions to the same locations as in the addon OMDB AFACD file. I then used ADE9x again to create an exclusion file for the whole airport ("all"). I have to place that in a folder with LOWER priority than OMDB (or all the runways and taxiways disappear too). Now, as I approach the runways, I am lined up with the centre-lines and I can't see any default FS9 stuff. Not sure this is an elegant solution, but seems to work...

What a waste of hours and hours - this still doesn't work!!! If the ADE9x stub is higher priority than the OMDB AFCAD, I get all the default FS9 OMDB parking at the FlyTampa airport. (If I delete all parking from the stub file, then there's no parking at OMDB at all - FS9 uses that ADE9x file in preference to the airport AFCAD). If the stub is lower priority than the OMDB AFCAD, it has no effect and a/c land to the right or left of the runways. The only way I can fly ILS to OMDB is to remove the default AP962230.BGL file - apart from OMAA (for which I have other 3rd. party scenery) there are no other airports I ever fly to in that file. Does it matter I've removed it in any other respect?I don't recall having any problems last time I flew into Dubai, so no idea what's happened now. I spend (almost literally) more time these days fixing FS9 - a different problem every time I start it up - than actually flying it. I sometimes wonder whether it's worth the stress and frustration.M.

Is this a download from somewhere? I've seen ILS problems when FS2k2 airports are put in FS9. What I've found is you can sometimes open the files with bglanalyze and find airport data in them, including ILS commands. bglanalyze creates files that can be compiled with SCASM and deleting the ILS commands and compiling might get rid of the offending ILS and allow AFCAD/ADE9 to take control again.scott s..

It's the FlyTampa FS9 OMDB scenery. They are FS9 files so only decompile to xml (not scasm - is there a way to make sca files from the 'new type' uncompressed bgl files?). As I say, I cannot get the xml file to recompile with BglComp.exe - it brings up errors and aborts (even with an unchanged xml file).M.

I have had to delete the default AP******.bgl file - I can find no other way of landing properly (ILS) at OMDB. I have opened the AP...bgl file in AFCAD2 and saved all the individual airports as separate bgl files, so I shouldn't lose anything, other than the default OMDB, which I have disabled. Flew into OMDB yesterday and all seems to work just fine now.I wonder why the FS9 default OMDB data is 'leaking through' into the 3rd. party airport in this way? It doesn't usually happen...M.

I participated in a very long forum discussion on this problem a few years back. When it was all said and done, I concluded that there are multiple reasons why this happens and probably no reliable solution. If you do a search, you should be able to find the thread - I'm pretty certain it was "post-hack." As I recall, some of the relevant issues were:AI aircraft flight modelsBuilt-in issues with the add-on scenery (Which I seriously doubt in this case as FlyTampa would have resolved it long ago)Approaches that are over, or near large bodies of water (Yeah, I know, sounds crazy but several people observed that this seemed to be a pattern)Others I can't remember...The upshot of it all is that finding a solution is pretty hit and miss and mostly missGood luck with it

I have had to delete the default AP******.bgl file - I can find no other way of landing properly (ILS) at OMDB. I have opened the AP...bgl file in AFCAD2 and saved all the individual airports as separate bgl files, so I shouldn't lose anything, other than the default OMDB, which I have disabled.

You will lose all your airport specific scenery (like ILS tramsmitters), taxisigns, and approach data doing that. Also I think that AFCAD2 works such that NAVAIDs are only compiled if you change something from stock.Out of curiosity I opened AP962230.bgl using BGL2XML, stripped out the runways and runway starts for OMBD, and recompiled with no problems. I would suggest that BGL2XML is the only decompiler to use. http://library.avsim.net/download.php?DLID=156017scott s..

Well, I'll probably never know why this particular airport has problems (especially, as I say, as far as I recall I flew in and out of OMDB just fine until the other day).I was using the FS2004SDK de/compiler - but downloaded the BGL2XML as you suggested Scott (though I couldn't get it from AVSIM - kept getting a file of zero bytes. used Flightsim.com instead). I decompiled the default AP bgl file with BGL2XML_GUI.exe and then, after editing, recompiled it successfully (but back with FS2004SDK's bglcomp.exe - I can't see how you use BGL2XML to recompile: nothing in the pdf, & dragging the xml file to the exe file doesn't work - just a quick flash of a cmd window. Perhaps you weren't meaning to imply you used BGL2XML to recompile - do you use FS2004SDK?).Well, I'll substitute the bgl files and see how I get on. Thanks, as ever, for the advice,Martin

I don't have this scenery so can't really comment directly but the first thing I would be doing would be comparing the original and new AFD files. Are these aircraft actually landing on the original FS runway alignment? Do AI aircraft park in the wrong places? One thing I would definitely check would be the airport co-ordinates using AFCAD, AFX or AF9 and make sure old and new are identical. Otherwise, FS might just be thinking there are two airports there even though you can only see one.Just some ideas . . .John

John, I didn't notice any oddities re. parking, but I had checked and a/c land on the default runways (the position of the runways is different in the AFCAD from the FS9 AP bgl). If I pause the sim and open the OMDB AFCAD, the cross showing a/c position is well off the runway (as I can see only too clearly in the sim!), but if I open the default AP******.bgl file, the cross is spot on where it should be (if I had been flying to the default airport). I haven't flown again to OMDB since I replaced the default FS9 AP file, but I suspect all will be OK (as it was when I deleted the AP file).M.

Sorry Folks but I have come to this very late. I am not sure I understand it all but it does seem to be very complicated. If the AFD file was created by AFCAD then we do see multiple ILS feathers if the ILS is moved. I am not sure I understand where the ADE stub bgl file comes in.If this is now all fixed then please just ignore my intervention. If there is still an issue then I would be very interested in understanding what is going on. If ADE cannot handle the problem then we would obviously like to look at way in which we might be able to improve the program to help.

W I can't see how you use BGL2XML to recompile: nothing in the pdf, & dragging the xml file to the exe file doesn't work - just a quick flash of a cmd window. Perhaps you weren't meaning to imply you used BGL2XML to recompile - do you use FS2004SDK?).

right, you need bglcomp to do the recompile. In my case I use the copy that is installed when you install ADE9X. The schema (xsd) file that was supplied with the sdk had some bugs. ADE9X and other sources have an updated schema that takes care of that.scott s..

Hi MartinYou have stirred my interest in you problem and I would like to see if I can help. If you would care to send me the FlyTampa FS9 OMDB AFCAD (just the copy of the afcad in a zip) I would like to put in my system and take a look at it and see what I can find or do. If you are interested please PM me a thumbs up and I will PM you my Email address.Regards,MelP.S. It just came to me; have you looked through the FlyTampa FS9 OMDB scenery package to see if there are any additional files such as approaches or airport data contained in separate bgls that may have been installed to one of the FS9 Scenery folders i.e. FS9/scenery/generic/scenery?

Mel, I PMed you...I've had the FlyTampa scenery pretty much since it came out (must be years ago now: I know the airport is no longer very accurate, but it still looks pretty good compared to the default!). My zip file doesn't have any files other than the airports scenery and running the exe file doesn't produce any either. Now that I have used BGL2XML to decompile the AP...bgl file (instead of the FS2004SDK BglComp.exe), BglComp.exe will recompile the xml file with no problem. I took OMDB out of the file and now all seems to work OK. So the practical problem is solved. (Famous last words: I hardly dare write them!).As for ADE9X (a great programme, thanks Jon et al!), I described earlier what happened. I used it to remove all Navaid/ILS information from the default airport (creating a stub file, as I described earlier in this thread), but couldn't find a folder to put the bgl file that worked: higher priority than OMDB and the ILS problem was solved, but things went very wrong with the airport scenery (default buildings reappearing - navaids in the middle of the runway. Odd??). Lower priority than OMDB and it had no effect at all: line an aircraft up on the runway and the ILS indicators in the cockpit are way off to right or left again.Martin

PM of my Email address has been sent to you Martin.Mel