• 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

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.


I agree - I think they are collateral information and if their interest is in parking spots then they are probably not looking for navaid information and are not intentionally changing it
 
Right i have only found two airports that have changed NDB FREQ due to MTX that is EGNX and EGGP

EGNX ILS rwy 27 NDB in FSX with MTX disabled shows 353.5 with MTX ENABLED it then shows 353.0

EGNX ILS rwy 09 NDB is no change it remains as it is 393.0
 
oh great is that another airport changed due to MTX JP?
Yes, same thing as with EGGP, the BGL contains quite a number of VORs and NDBs, with wrongly rounded frequencies.
Once you "cut the fat" from those two BGLs you will see the EME NDB (EGNX RW 27) and LPL NDB (EGGP RW 27) with correct freq.
 
Last edited:
ok will i go in and delete them or something
Actually it's 3 BGLs: "BR2_EGCD.BGL", "BR2_EGGP.BGL" and "BR2_EGNM.BGL".
Don't delete them, just back them up (don't remove "BR2_EGGP_hf_CVX.bgl", you still need that one!) and use these instead. ;)

(I think I remembered to update draw flags on aprons and taxiways too, so they can be used in P3D as well.).
 

Attachments

Ok are these the ones i sha'll place in MTX scenery?

Also what about EGNX
Yes, these are the corrected ones to place in MyTraffic\Scenery.

The EGNX file, "BR2_EGNX.BGL" is fine as it is. The faulty NDB(s) was in the other BGLs.

(Also, please inform Burkhard, I'm sure he'd love to get an explanation so he can make an "official" fix.).
 
EHNX? Is that in the Netherlands? (If, by chance, you mean EGNX, I can assure you that the faulty EGNX NDB did not originate from the EGNX BGL but from one of the three I edited. Try for yourself).

I'm not changing any NDBs, I have only removed (faulty, duplicate) NDBs from the 3 BGLs. I do it by loading the BGL in ADE and save/compile (I have enabled the ADE option to keep the XML). Then I hand edit the XML to remove the faulty navaids, load the XML in ADE and save/compile again.
 
Last edited:
That sounds to complicated for me to do lol

Right i'm confused. Only thing i notice with EGNX NDB is with MTX enabled the NDB changes
 
Vernon, all you have to do to correct your NDBs is to copy the 3 files I posted to your MyTraffic\Scenery folder (backup the original 3 files first just to be on the safe side).

That can hardly be too complicated. :)
 
Yes i have done that mate but what i'm saying is what about other NDB i find will i just compile in ADE and copy and paste to MTX?
 
MTX has also changed EGNX NDB at rwy 27
Yes, like I already stated twice, that changed NDB was in (at least one, two if I recall correctly) of the 3 original BGLs I posted updated versions of. It is _not_ in "BR2_EGNX.BGL". Jon's screenshot on page two of this thread shows exactly that.

If you find other NDBs with wrong freq, you will have to do the full manoeuver. First, identify in which BGL the faulty navaid resides (as you can see it doesn't have to be in the BGL for the airport closest to the navaid!), then recompile/edit XML by hand/recompile. Alternatively, if you got the Prokey (I don't!), you can do the XML edit from within ADE (If I understand that aspect of "Prokey perks" correctly.).
 
Back
Top