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

Extend NDB Range? How To ?

apollomaker

apollomaker

Messages
123
Country
unitedstates
Hello All --- Was wondering if there is a relatively easy way to extend NDB range beyond the maximum imposed by ADE?

Anyone done this yet? Any help appreciated.

Thanks for any comments!!!! Regards, Bob :D
 
Along with some folks at Sim Outhouse we did extensive testing of NDB ranges when preparing for a rerun of the MacRobertson Race (EGUN-YMEN) a few years ago - trying to replacate the long range NDB available back in 1934.

We found it basically impossible to create a workable NDB signal in FS out to the 200nm target we were seeking. We could sometimes get a signal out to about 125nm, but not reliably farther than the default HH type NDB range of 112nm. The four types of NDB appear to be coded to an approximate range for each type.

We tried with both AFCAD and hand coded XML.

If anyone has had better luck, let me know.
 
You can over ride the 'maximum' (that is the range specified in the SDK) in ADE if you have a ProKey and use the Raw Data View.
 
scruffyduck said:
You can over ride the 'maximum' (that is the range specified in the SDK) in ADE if you have a ProKey and use the Raw Data View.
Click to expand...

Hello Jon and All ---- thanks for the input and comments. Jon, I tried exactly what you mentioned using ProKey which I have installed. Maybe I was not in the right location (the right XML code) but I did bring up the RAW DATA of the NDB and tried the VOR as well and nothing would stick. The values would always change back.

Not sure what I might have been doing wrong if this is possible. Any pointers?

Also, I am trying to modify these values at a custom airport of my own design, not a stock airport. Second, everything is unlocked before I try and edit the XML code which I locate for both the VOR and the NDB in ADE.
No trouble locating the code and parameters for each, but maybe that is the point at which I am going wrong. (?)

Many Thanks --- Bob ;)
 
Last edited:
Make sure you are saving and reopening the airport to/from the AD2 file, never reopen it from the BGL file.
 
Well I loaded an airport. Added a user NDB. Went into RDV. Set the Range to 200 and it sticks. However if you then open it in the regular Property Dialog you will see a lower value (100 in my case). If you want to try a high value then work only with RDV and do not try to edit it again with the regular property grid.

I test compiled it and read back the Bgl file - it had a range set to 200.05Nm. Whether FS will honor this value I don't know
 
scruffyduck said:
Well I loaded an airport. Added a user NDB. Went into RDV. Set the Range to 200 and it sticks. However if you then open it in the regular Property Dialog you will see a lower value (100 in my case). If you want to try a high value then work only with RDV and do not try to edit it again with the regular property grid.

I test compiled it and read back the Bgl file - it had a range set to 200.05Nm. Whether FS will honor this value I don't know
Click to expand...

Hello Jon --- well, we gave it the good ole college try. But it did not work. While I did get a bit more range out of the NDB, it was about half of where I set it. Looks to me as if FSX is making some kind of "decision" about how to use the range number. We tried --- guess I will just stick with the default maximums and let it go at that. If you ever do figure out what is controlling the range, it would sure be a nice feature to allow the user to set value without restriction when ProKey is present.

Thanks Again --- Bob :D
 
tgibson said:
Make sure you are saving and reopening the airport to/from the AD2 file, never reopen it from the BGL file.
Click to expand...

Hello Tom --- been a while since we chatted here. Nice to hear from you.

As it turns out, I do all my project manipulation (compile, open, save, etc) from the ad2 files. So no problem there. Too bad I could not get it to work, even with everyone's help. Would be a nice feature to have if implemented cleanly such that your desired range for VOR or NDB effective range could be specified at design time or later, if needed.

Another one for the wish list. Thanks for your help!!!! ---- Bob :)
 
It is not mentioned anywhere in the SDK, but NDB, VOR and DME have defined ranges in the real world today.

The type of navaid (NDB - Compass Locator, MH, H and HH; VOR High and Low) - defines the target range in the real world. FS appears to use those ranges in the basic definition of the navaid.

While the real world has some variation due to atmospherics, FS doesn't seem to do that.

It has been my perception that the Range variable in the NDB definition is more a reflection of the Type variable, rather than a variable we can adjust to suit our desires.
 
You must log in or register to reply here.
Back
Top