• 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

JP

You should not have to edit using the XML. Those NDB's are not ADE stock since ADE does not compile the NDB. You should be able to just highlite the NDB and hit the delete key. Save the ADE project file for future use and compile for MTX.
 
Vernon

Can you find the BR2_EDDI.bgl file in MTX. If so can you attach to a post so I can get it.
 
Jvile i'll try do it today when i'm home and got time!

As for NDB can i not just compile it in ADE then copy and paste the bgl to MTX scenery folder?
 
jvile said:
JP

You should not have to edit using the XML. Those NDB's are not ADE stock since ADE does not compile the NDB. You should be able to just highlite the NDB and hit the delete key. Save the ADE project file for future use and compile for MTX.
Click to expand...
Lol, that actually works. Thanks Jim!

I once had an airport that had some stock navaids orphaned, in that case I couldn't use ADE to remove the navaids so I opted for editing the XML; reckon the method "stuck" with me because it works always. ;)

But you're right, if the navaid you want removed isn't stock, it's definitely easier, and faster, to do it in ADE. My apologies to Vernon for making that part more complicated than need be.

The non-trivial part of removing erroneous NDBs is actually not so much editing the BGL (one way or another) but rather finding out which file contains the wrong navaid. In case of My Traffic, there are more than 2,500 BGLs in the \Scenery directory. Even if you narrow your focus to airports with "EG" as first two ICAO code letters there are still more than 150.
 
Last edited:
Vernon howells said:
JP

EGNX has fixed did you send a file in one of those 3?
Click to expand...
Yep, the EGNX NDBs were among those navaids "trapped" by those 3 BGLs. So if you overwrite the MyTraffic ones with the ones I posted, they should be "released" back to stock, in effect fixing the wrong frequencies.

Specifically, EME was contained in the BR2_EGCD.BGL and EMW in both BR2_EGCD.BGL and BR2_EGGP.BGL.
 
Last edited:
Vernon howells said:
guys how come if i open EGNX as a bgl in ADE the NDB don't show? and when i open it through stock airport the NDB show?
Click to expand...

What JP said

ADE list the stock navads such as NDB's VOR's within a set radius of the airport. These navaids are used to help in drawing the approach code in Approach mode. It is important to always save your ADE project file and work from it.

When ADE compiles your work there are many parts that do not get compiled such as some NAVAIDS. FS is smart enough to know to use the stock Navaids so if you open a bgl you won't see them. If you open someone elses bgl with ADE we had no control over what they may have added to there airport such as navaids like NDB's with the wrong freq.

The current MTX EDDI airport is using compiled duplicate approaches. This was probably another mistake which was overlooked when changing the parking spots from 18 Meter to 14 Meter. When someone works a airport using XML it is very easy to do something to the airport which breaks how it works.

In this case the DeleteAllApproaches in the XML is coded FALSE (that is what AFX has to do). That tells FS9/X to fallback on the stock approaches in the stock bgl because they will not be added to the newer EDDI with the gate changes. However what did happen. The approach code was also placed into the addon BR2_EDDI and now FS is listing them twice in the GPS reciever. This can also cause GPS corruption in the line draw and no vectors to final for the ILS's.

In this picture you can see no line draw for vectors to final.

fsscr008.jpg


In this picture we see VORDME 09 is 1st on the list and then the approaches repeat themselfs further down the list starting again with VORDME 09. You have to use the scroll down knob to see the rest of the repeat list.

fsscr011.jpg


The developer responded to the issue with NDB freq's saying, and I quote

so if you think something should be changed please do so and provide us with an updated version of the airport.
Click to expand...

I have no desire to look through 2500 airports and fix what I see wrong and then provide them an update of my version so a payware addon can use it. However for EDDI it is a closed airport so I would not spend anytime on it.
 
Last edited:
Well I would say that it is up to the developer of the product to fix it, and it is up to the users of that product to complain to the developer and report any anomalies they come across. To be honest we have had issues for years with airports modified for use with AI traffic.
 
Thanks for the response! The developer said hes going to fix it on the next release.

Can one of you's help me? If i find another airport with the wrong freq, can someone please send me the bgl with the correct freq? I'm just not sure how to do it. Many thanks.
 
Can one of you's help me? If i find another airport with the wrong freq, can someone please send me the bgl with the correct freq? I'm just not sure how to do it. Many thanks.
Click to expand...

Please try to do this yourself first.

First open the bgl file in ADE and try to delete the offending navaid. Then compile your version. Rename the original with something like dnu instead of the bgl extension. don't add dnu at the end so you end up with .bgl.dnu. FS seems only to read the first extension and not the last.. Now put your revised bgl in place of the existing one. As already mentioned this has the effect of forcing FS to use the stock navaid instead of an updated one. Removing it is better than changing the frequency on it since there should not be any compiled stock navaids in addon bgl files in any case.

If the above does not work then 'phone home' and we will see what else can be done.
 
Ok i'll try that later on!

What i done yesterday is, just open it through stock airport and compile it then copy and paste to MTX
 
What i done yesterday is, just open it through stock airport and compile it then copy and paste to MTX
Click to expand...

Well you can do that but that will also mess up the parking spots since you will go back to stock parking spots again.
 
You must log in or register to reply here.
Back
Top