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

Edit NDB

probably having his breakfast since he lives in the US ;)
 
How are you checking the frequency in the sim?

Are you using the map or an ADF receiver in a plane?

cheers,
Lane
 
You would be best to test your scenery with a default plane, using default gauges, to eliminate the possibility of the plane causing the problem.

I believe MTX (don't own it) provides a bunch of airport files to increase the amount of available parking. You might be able to look through the MTX folders and find files specific to your trouble airports. If so, you could disable those files by changing the extension. I use .zzz as this will move all disabled files to the end of the list.

cheers,
Lane
 
You can change the freq of your NDB as long as another NDB (based on type) does not have the same freq. within the range of your NDB. ADE allows you to change the NDB freq but you must have a Prokey and make the change using the Raw Data View.

But, none of this is your problem. It appears you have found the problem in the AI program MTX. Lane gives a good answer in finding the airport within MTX. However it would be of interest why MTX is changing NAVAID freq's when they add additional parking spots to airports.
 
Last edited:
Lane street i will look through files and see what i can find.

Thanks jvile this is MTX fault i wrote on the forums and they deny changing such navaids!
 
Look for the Folder MyTraffic\scenery\BR2_EGDX.bgl or EICK.bgl

The scenery folder should have all the airports MTX added. If you find one attach it to your post so I can look at it.
 
OK these are the navaids at EICK from that Bgl file:

ScreenShot00035.png



and these are the NDBs in the file for EGGP

ScreenShot00036.png
 
liverpool has two NDB the one thats showing has the correct freq
Click to expand...

No it does not.

I have taken a look at what Jon is showing and looking at some of the other NDB's in question.

Lets keep this simple and look at the Stock NDB LPL Liverpool which is 4.4 miles from the airport. The following picture is the stock Liverpool airport. It shows the LPL NDB is FREQ 349.50. When I fly the ILS 27 the NDB is active on 349.50

fsscr005.jpg


Now look at Jon's picture above which is the EGGP from MTX that you attached to your post. When you look down the list the 2nd NDB is LVL showing the stock freq has been changed to 349.0

I added the MTX EGGP bgl to my FSX scenery. When I fly the ILS 27 approach I now have to tune 349.0 to get the NDB to come alive.

fsscr004.jpg


What ever program MTX is using for airports is rounding down a NDB that has a .50 to .00 so 349.5 is now 349.0 i have check other NDB's and all are doing the same thing.
 
ScreenShot00037.png
OK - here are the navaids in that file:
 
It looks also like they are compiling navaids that should not be compiled since they are stock and should be read from the stock files
 
I see the same thing. There are no NDB's in the EGNX that you just posted so FSX is falling back on the stock NDB.
 
Last edited:
scruffyduck said:
It looks also like they are compiling navaids that should not be compiled since they are stock and should be read from the stock files
Click to expand...

I saw that to but MTX is saying they don't do anything with NAVAIDS. That may be true but the developer of there airports is not checking the work very closely.
 
You must log in or register to reply here.
Back
Top