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

Excluding Navaids

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,912
Country
unitedkingdom
This seems to be a real shortcoming. We can exclude all sorts of things so that we can replace stock airport data, objects, land class and so on. however there is no mechanism to exclude the naviads that are in the default files. Thus we are stuck in the time frame when the stock data was compiled and cannot update to the current situation when ILS are changed or other naviads are de-commissioned
 
I agree with you there, Jon.

If only Flight Simulator had a built in check for navaid updates, based on the Navigraph - AIRAC system.
 
This seems to be a real shortcoming. We can exclude all sorts of things so that we can replace stock airport data, objects, land class and so on. however there is no mechanism to exclude the naviads that are in the default files. Thus we are stuck in the time frame when the stock data was compiled and cannot update to the current situation when ILS are changed or other naviads are de-commissioned

Does that also mean a misplaced ILS can' t be replaced? To be more precise: I' m pretty sure that the ILS centerline of LIMJ - Genoa Sestri is located some 50 to 60 meters too far to the south.


I' m aware of the fact that LIMJ has an offset ILS approach.

The RWY-centerline is at 284° whereas the glideslope-centerline is at 287°

I think that the localizer has to be placed further up to the north so that the 107° radial will intercept the RWY-centerline somewhere at the RWY 29 threshold.


Unfortunately I' m still a bloody beginner with FSX and still not really a FS-developer. So - at least for now - I can' t solve the problem myself. Or, according to what was posted before, is it impossible to adjust the ILS?

Regards from Bavaria

HF
 
Last edited:
Back
Top