Snarl ! More ILS crapola in FS 2002.....!

[JSACKS 0]

I know I posted a month ago about runways with the same ILS frequencies for both ends of the same runway not working for me and several folks posted replies. This has become a significant issue for me and I wonder if MS will fix it in the next edition of FS.After a lovely 5 hour test flight in a POSKY 777-200ER with PSS panel, I decided to land at KDEN. But just as I'd found at KPDX and then KSEA in recent weeks, to my annoyance, when I tuned the ILS for the arrival runway, it indicated the reciprocal runway heading on the ND of the PSS panel. I knew immediately that this was another major airport with ILS googlies for me. I tried 8 other ILS runway headings at KDEN and every time, the ND indicated reciprocal runway heading tuning. I finally slewed over to Dallas Ft Worth and successfully tuned an ILS and autolanded--on a runway with a single ILS frequency for both headings !It's fantastically annoying to fly for hours and have this sort of thing happen. MS may have modelled 28,000 ILS or airports or whatever, but there is a bug in FS2002 that makes an ILS approach to an arrival-reciprocal runway with a single radio frequency a totally random affair. To have this happen at major airports is just not acceptable, I'm sorry, but MS has fallen down on this one badly in this edition. I have tried some .bgl fixes for various regions of the U.S. posted by AVSImers and others, and none have cured this phenomenon. It was never like this in the early days of Fs2002. It all worked fine. What happened? I have no idea.Sorry to vent yet again but if this prompts anybody to think of an idea that would fix this annoyance, or something to experiment with, please be my guest.Thanks.JSP.S. The ILS into KDCA, a homne airport for me, is a bloody disaster. The nav rad switches to a totally different ILS arrival before crossing the aximuth for the runway 1 ILS. Darn these bugs !:~P :-fume :-mad :-bla

[Guest]

Man, that's totally bizare. After installing the KPDX ILS update to fix 28L (I think) I haven't had any ILS problems with any airports. I fly KSEA all the time and fly to KPDX often. Have a feeling something is goofy with your FS install somehow. Maybe one of the gauge packs you installed fowled something up? Hope you're able to figure it out :(

[JSACKS 0]

I don't know if I can figure it out!.I have wondered if I should try to reinstal FS2002 and see if that makes it better. I am really out of ny otht ideas. I thought it might be a radio gauge or some such thing but I have no idea how any of that stuff works in terms of coding and interpretation, etc.JS

[Vulcan 14]

JS,I too have only recently found this problem with my home airport and I know it used to work OK.I have uninstalled a local scenery but the problem persists so I am going to do fresh install of FS and all my add-ons....wish me luck :-lol I was going to do it anyway to put FS on a fresh HD, just hope it cures the problem.

[michal 44]

>airports or whatever, but there is a bug in FS2002 that >makes an ILS approach to an arrival-reciprocal runway with a >single radio frequency a totally random affair. Last time I did my best to explain that this is your precedural error how you fly the ILS and not the bug in FS2002. After expending so many words clearly in vain I am not about to do it again. I have absolutely no problem flying ILS to runways with the same frequency at both ends. The only way to 'fix' this bug is to have option to turn on/off ILS manually at either end - sort of what real tower controllers do. Whether they do it or not I have no clue.Michael J.

[JSACKS 0]

Michael:I assure you this is NOT a procedural error. I have two PCs with FS2002. I have many identical saved files with ILS approaches on each. On one PC the ILs approaches for certain airports works fine; on the other one, it does not. It has nothing to do with the way I intercept or cross the runway azimuth etc. I repeat this is NOT procedural. It is a technology issue related to the programming or coding or the way the application runs; there may be corruption involved. That is why I am posting here again. I am delighted that you have no problems flying an ILS with the same frequency at both ends of the same runway and wish I had the same good fortune. It used to be thus. Something happened within the PC or within FS2002. It's nothing to do with the way I fly. That said, I DID in fact do exactly as you suggested last time, several times, but it did nothing to cure the problem. I did what you suggested just in case it was a procedural issue, but it is not.You can see that others have similar issues to me both here and in prior threads.JS

[michal 44]

>On one PC the ILs approaches for >certain airports works fine; on the other one, it does not. JS,You then answered yourself. If this is the case then there is some corruption with one of your FS2002 installations.Michael J.

[Guest RonB49]

Dear JS,Never mind. R-

[JSACKS 0]

Dear Vulcan:Would you perhaps post if a fresh instal of FS2002 cures the problem for you? If so, I will do so as well.Good luck.Thanks!!JSP.S. Do you know or does anybody else out there know if uninstalling and reinstalling FS2002 will delete any 3rd party add-ons or saved flights, etc.?

[Vulcan 14]

Sorry Michael your explaination does not work, at least not in my case even if I delete my add-on EGCC airport and go back to the default MS scenery.The ILS at EGCC has worked perfectly in the past, something has changed to make it behave as a BC. In fact I think I replied to your post where you first mentioned your 'fix' to explaine that 'correct' porcedure did not change the ILS reading one bit.In the past I have been involved with a similar problem at Bristol in UK; some people were getting BC readings, I was not and each of us had the same add-on scenery.I seem to remeber a thread quite a long time ago about reselecting the ILS frequency on Nav1, something to do with FS picking up a 'default' one, but I cannot remember the details.Rgds

[JSACKS 0]

Vulcan:In Nick Dargahi's encyclopaedic book The Ultimate Flight Simulator Pilot's GuideBook (a must-have tome!), he writes (about FS98) on page 504 about how there are sometimes 2 localizers active on a single runway and how FS does not know which end you are intending to land on. He goes on to mention that FS98 has (had!) a feature in which you could select LOCALIZER 1 for the lower numbered runway and LOCALIZER 2 for the higher number runway through the menu Aircraft/Navigation/Nav Radios.This function no longer exists in FS2002. You CAN select an EFIS display with colored boxes and you can elect to display the intercept path as well and ask to lock on to the ILS or the VOR in FS2002. I've just tried this at KJFK (into 31L) with great success, but it was a disaster at KPDX because of the inversion of runway headings that has been driving me mad for several weeks now.There are no more options within FS2002. The sole remaining option is to uninstal FS2002 and then reinstal the whole thing which seems slightly risky and sort of crazy to try and fix this. I mean, if it worked for both of us perfectly in the beginning and got corrupted somehow, how can we be sure this will not occur again?Anyway, I guess we will each decide what we wish to risk doing!Post again and I'll reply if I can be of any use in the miserable affair.Cheers!JS

[JSACKS 0]

Minor addition to post above:"....two localizers are active ON THE SAME FREQUENCY."Important addition!!!!JS

[Guest]

Had a similar problem when I installed the KPDX fix for the 28L ILS. All of a sudden, all of the ILS in the U.S. NW with dual localizers(single frequency) were reversed, and I couldn't get the GS on either side.Anyhow, it involved some debugging, and to make this story short, the bug was:- When I installed the new usnwils.bgl, I renamed the default FS2002 usnwils.bgl as "usnwils.bgl old"Well, FS2002 still loaded the old one as well as the new one, thus the snafu.So, had to change the old one to "usnwils.bgl.old", notice the "." Period between bgl and old which I didn't have before.Everything works as advertised, the Nav1 tunes into the correct localizer depending on which heading I am from runway, etc. It's not an FS2002 bug this time.I also went back through my FS2002 to fix any other files I had renamed as "xxx yyy", changing them to "xxx.yyy", and this actually fixed a few crashes I was having.One place to look ...

[Vulcan 14]

Ian, you're a star That was the pointer I needed to cure EGCC.When I looked in the scenedb folder I found I had eurnwils.bgl and copy of eurnwils.bgl, deleted the copy and the ILS for EGCC is now correct.I seem to recall some add-on scenery had an *ils.bgl file to add so that may be where the copy came from.What I don't understand is why my normal naming convention fell apart.If I replace a file with a new one, as in this case,I normally rename the original as *.bg# or *.org depending on which makes sense. as the file extension is changed there is no danger of FS trying to load the file.JS, hope this fix helps you also.Again thanks a million Ian, and at least it proves it has nothing to do with how you approach the runway, sorry Michael ;-) j/k.

[Guest]

Glad to be of service, guess I'll treat myself to a beer!!!