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

FSX NDB Problem

I

Ian P

Messages
105
Country
unitedkingdom
Hello again all.

Now I've disposed of the troublesome trees, tinkered with taxiways and bunged up a load of buildings, I decided to try and add an NDB to my second test scenery. After putting an NDB structure in place using F1's Instant Scenery, I marked the exact location and hand-coded the NDB into the XML file providing the general airport layout. It compiles perfectly, shows up on the FSX map function, but the needle on an ADF won't swing to point at it.

Has anyone encountered this before or have any idea what I'm doing wrong this time?

The code I am using is as follows - comments are added here, not in the XML...:

Code: 
<Ndb
   lat="48.9175335690379"
   lon="-119.642931818962"
   alt="1162.6F" //(have also tried this in metres as per the SDK)
   type="H" //(have tried several options here)
   frequency="0349.00" //(no local beacons on this)
   range="65.0M"
   magvar="0" //(need to check and change this)
   region="K1" //(checked and correct)
   ident="PBB"
   name="Bigger Base">
</Ndb>

As I said, it shows up fine in the map, with the correct identity and frequency, but setting 0349.0 on the ADF in any aircraft I have tried so far results in nothing being picked up at all.

I'm :confused: - does anyone have any suggestions?

Cheers,

Ian P.
 
Check the range. Currently it's set to 65.0M as meters. It should probably be 65.0N as nautical miles.
 
Paavo said:
Check the range. Currently it's set to 65.0M as meters. It should probably be 65.0N as nautical miles.
Click to expand...

That certainly looks like it - M is not miles but meters
 
I copied that from a decompiled default bgl, so presumably must have got some form of approach marker or an oddity rather than a navigational NDB. Will try changing to an "N" when I get home this evening. That's a classic example of being too close to a problem and not seeing the obvious.

Thanks, gents.

Ian P.
 
Ian P said:
I copied that from a decompiled default bgl, so presumably must have got some form of approach marker or an oddity rather than a navigational NDB. Will try changing to an "N" when I get home this evening. That's a classic example of being too close to a problem and not seeing the obvious.

Thanks, gents.

Ian P.
Click to expand...


If you leave the letter off then BglComp should treat it as Nautical Miles by default. Most attributes of this type have a default if there is no letter. The SDK should tell you.
 
Having checked the decompiled XML file that I copied the NDB section from before modifying it, it indeed does not have a letter after the "100" range figure, thus implying 100NM.

It looks like something I did while playing had put the M in. Not sure what, but considering how much time I spent arguing with it in different programs and using different methods (SDE, ADE, FSXPlanner, Windows Notepad, IE and the FSX Scenery Toolkit from the Avsim forums were all used at various times) I no longer have any idea what or when. A quick test last night proved that changing the "M" to an "N" or removing it altogether both worked, so that's definately a success.

I think this will be my last fictional test scenery for the moment and I'll go and try doing something "official" next.

Thanks for your help!

Ian P.
 
Off topic I know guys, but can I just ask if there is any way to add an ndb to scenery to use an an Epirb or PLB? I do not want it to show on the maps, as it is to be the distress marker in search and rescue missions. Teecee.
 
Last edited:
You must log in or register to reply here.
Back
Top