• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Same ILS Freq at either end of runway causes problem

Messages
4
Country
us-georgia
Just started using ADE in my P3D version 3.4. Mostly using it for taxiways that are missing and it works great. I downloaded an update for KFLL today, installed it, fixed the taxiways and it looks great. Only problem I had was the ILS for runway 10R did not work. On approach, no indication of the localizer needle until I actually crossed the runway threshold, and then the needle moved. I flew a traffic pattern, and going upwind, as soon as I got past the threshold of 10R at 1000 feet, the needle went dead again. It was like the ILS beam stopped at the approach end of the runway. I then check the BGL file in ADE and there was an ILS at either end of this runway 10R -28L. I then deleted the 28L ILS because Skyvector did not list it for that runway. Then the ILS for 10R worked perfectly.

Now my question is, in the sim, does having the same ILS freq on either end of a runway cause a problem like this? I will upload the file after I deleted the 28L ILS.
 

Attachments

So you are saying that you have made no changes to your simulator beyond updating KFLL? It seems like you would have had to add a KFLL to update and it seems unlikely Ft Lauderdale is the only addon you have added to your P3D. Over the course of the linked thread the user found two addons that were causing an issue that appears to be identical to yours and your most recent post implies you have explored these conditions and there is no connection. Understand that the same frequency at both ends of a runway does not cause a locator issue. However, a condition arises that affects runways in that configuration. For this user, the condition arises when he "toggles the glideslope/ILS capture," a setting that is available in several of his addon product configurators, apparently. I have no solid idea why someone would want to switch it off, maybe to discourage AI traffic and maybe that does not apply to your situation at all.
At this point, however, there simply is not enough information to go on. You'd probably want to give some background, what you've done, did this ever not happen, what addons you've applied, etc.
 
So you are saying that you have made no changes to your simulator beyond updating KFLL? It seems like you would have had to add a KFLL to update and it seems unlikely Ft Lauderdale is the only addon you have added to your P3D. Over the course of the linked thread the user found two addons that were causing an issue that appears to be identical to yours and your most recent post implies you have explored these conditions and there is no connection. Understand that the same frequency at both ends of a runway does not cause a locator issue. However, a condition arises that affects runways in that configuration. For this user, the condition arises when he "toggles the glideslope/ILS capture," a setting that is available in several of his addon product configurators, apparently. I have no solid idea why someone would want to switch it off, maybe to discourage AI traffic and maybe that does not apply to your situation at all.
At this point, however, there simply is not enough information to go on. You'd probably want to give some background, what you've done, did this ever not happen, what addons you've applied, etc.


OK. I tried it again this morning, loading the original BGL with the twoIls approaches 10R-28L and now everything works properly... Didn't change anything else...... Go figure.. Thanks for your help anyway. :)
 
Great. Might have been a transitional state from activating the scenery without restarting the sim or something.
 
Great. Might have been a transitional state from activating the scenery without restarting the sim or something.

Spent some more time with this today, as yesterday I was juggling so many files around, I lost track of what I had at the end of the day. When I flew today, as I already stated both ILS's worked. After I landed, I had a chance to look at the BGL, and I had thought that I had reinstalled the BGL with the two ILS's, 10R and 28L. What I had in fact done, is reinstalled the BGL with the one ILS deleted, 28L. This is the one, by the way, that I submitted with my original post. I had thought at the time, that deleting 28L, was what got 10R to work, which it did. I also thought that I no longer had a functioning ILS 28L. This turned out not to be true. I know have both ILS's working 10R and 28L, along with their glide slopes. You can examine the KFLL_ADEP3_BC.bgl and try it in the sim, and you will see only one ILS for 28-10, but they both work from either approach. I do see, that on that runway according to ADE, there are two glide slopes, one on each end of the runway.
 
Back
Top