• 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.

FSXA Problem with ILS

Messages
8
Country
sweden
I am trying to fix an add-on airport, the problem is that the ils is kind of broken or something, it captures the ILS and LOC, fly the LOC for a bit and then goes right out over the ocean, I did check it with AFX and did put the original values from stock airport in but that didn't help, I am new to this editing and don't know what to do, the developer did release this airport package over 1 year ago and said that their will be an fix for all the ILS that are not working and other stuff out soon, but still non and recently he did tell that he is putting all the modelling on the shelf, any tips, did try to fly in the stock airport, but only works for a short while, then I get run out of memory message...
 
Last edited:
If you post a file name and a link to wherever the add-on airport can be obtained, perhaps someone can take a look and advise you...
 
I cannot download that file.

When a ILS in FS2004 or FSX causes a plane to turn on a different heading (when on localizer) could be caused by using a BGLC FS2002 type runway that already has a ILS assigned to it.

Another problem could be 2 Localizers have the same frequency within 30 Nm's of each other.
 
I cannot download that file.

When a ILS in FS2004 or FSX causes a plane to turn on a different heading (when on localizer) could be caused by using a BGLC FS2002 type runway that already has a ILS assigned to it.

Another problem could be 2 Localizers have the same frequency within 30 Nm's of each other.

he have mowed the runway in sideway, could that be one of the problem?, but he have also movied the LOC and glidepath so they are with the runway , there is only ILS on the runway and that is rwy 14, that's a good point, going to check if there are any ILS nearby with same frequency.
 
Last edited:
he have mowed the runway in sideway, could that be one of the problem?, but he have also movied the LOC and glidepath so they are with the runway , there is only ILS on the runway and that is rwy 14, that's a good point, going to check if there are any ILS nearby with same frequency.

If he moved the runway and the localizer did he also fix any approach code?
 

Attachments

  • Untitled.png
    Untitled.png
    298.7 KB · Views: 492
  • Untitled2.png
    Untitled2.png
    250.3 KB · Views: 533
Go to Approach Mode (button at top right), and load any ILS approaches. Do they look correct in the map?
 
OK - Tom is referring to ADE. Since you are posting in the ADE support forum I guess it is natural to assume you have ADE.

AFX does not work with approaches. If the Bgl file you are working on was created with AFX then the default approaches will be passed through. If it was created with ADE then it may be that the developer modified or adusted the approaches to deal with the moved runmway.

If a runway has been moved then any stock approaches could become kinked. However this may just be a red herring in respect of your issues with the airport.
 
I did download Airport Design and did go approach mode, the ILS looks okay, it's just a small bit of to the left of the runway...
 

Attachments

  • ESTA ILS.png
    ESTA ILS.png
    157.4 KB · Views: 502
I did download Airport Design and did go approach mode, the ILS looks okay, it's just a small bit of to the left of the runway...

That is the localizer - that is not the approach code. You can see the localizer in normal mode. Are there any approaches listed when you go to Lists > Approaches in Approach Mode?
 
No, it's empty there, so what do I do?, add a new ILS?

Well I would first check the airport and its approaches in the FS GPS. If none are in the bgl file then I assume that either the stock ones are being used or there is another file somewhere with the approaches in.

If you check in the GPS then you can see if there are any bad doglegs in the approaches with respect to the moved runway. If it looks OK then I would ignore approaches in respect of your problems
 
sorry for late answer, have been busy with other things, I have now checked both the gps, no problems there, have checked the map and there is no airport nearby that have an ILS and non have same frequency....
 
I am trying to fix an add-on airport, the problem is that the ils is kind of broken or something, it captures the ILS and LOC, fly the LOC for a bit and then goes right out over the ocean, I did check it with AFX and did put the original values from stock airport in but that didn't help, I am new to this editing and don't know what to do, the developer did release this airport package over 1 year ago and said that their will be an fix for all the ILS that are not working and other stuff out soon, but still non and recently he did tell that he is putting all the modelling on the shelf, any tips, did try to fly in the stock airport, but only works for a short while, then I get run out of memory message...

I checked the airport that you attached (ESTA)

I can fly the ILS for runway 14 with no problems. However, there are some minor tweaks that could be made.

1. The Localizer is not center of the runway.
2. The GS is on the runway (small green triangle) and needs to move off the runway.

This airport was designed with AFX. That is not a problem but the runway 14/32 has been moved a small amount. The Localizer has been moved. AFX cannot rework the approach code and works with all default approaches. This causes the Approach to runway 14 to be off center as per the lines in the GPS.

The approach is not off that much and does not cause the airplane to go out over the ocean.

You only attached a small part of the total package. I am downloading the entire SWED package to see if something is effecting ESTA. It is a very slow download so it will take sometime to get it all.

Please check to be sure you do not have 2 or more ESTA airports running on FSX

Once I have it I will repost my findings.
 
Last edited:
Back
Top