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

FS2004 Adding stock NavAids to user-created Airport?

Leo2789

Leo2789

Resource contributor
Messages
222
Country
portugal
Hello all!

I had messaged Jon with this question, to which he replied that it isn't something people had asked him before and so he had no fix for it 'on-hand'.
What I need is to add surrounding stock navaids to an airport I created myself which represents an actual real-life airport missing from the default scenery; I need this so I can create the relevant approaches for it accurately, but as expected the option to 'Load Stock Data' is greyed out.
So I was wondering if anyone has ever had this issue and if you ever fixed it or found a workaround, and if so how? :)

Thank you
 
I add a navaid like VOR/DME in ADE Approach mode with position, frequency, range as found in the docs.
Is that wrong?
Here is an example:
AIP2.jpg
 
Last edited:
hgschnell said:
I add a navaid like VOR/DME in ADE Approach mode with position, frequency, range as found in the docs.
Is that wrong?
Click to expand...

Yes I do that too for Navaids or Waypoints that aren't in the stock scenery. My question is how to include stock navaids in user created airports?
Simply creating a navaid with the exact same data as the stock one would generate a duplicate no? :confused:
 
You are right, my 'Load Stock Data' is greyed out too.
But if I go in "Approach mode", I can see these navaids and they are in the list too.
I dont remember if I imported them once. Perhaps this could not be done twice? :scratchch
Which version of ADE9 do you use?
 
hgschnell said:
You are right, my 'Load Stock Data' is greyed out too.
But if I go in "Approach mode", I can see these navaids and they are in the list too.
I dont remember if I imported them once. Perhaps this could not be done twice? :scratchch
Which version of ADE9 do you use?
Click to expand...

I see no navaids of any sort except those I have added myself (where applicable) in my projects :/
I'm using 1.67 currently but in the process of updating to the latest!
 
As stated above, you might try adding the navaids yourself (matching the stock ones), and then create your approaches from them. Then compile to FS and check if everything is OK. If FS is confused, you might try deleting your versions of the stock navaids, leaving only the stock ones behind.
 
tgibson said:
As stated above, you might try adding the navaids yourself (matching the stock ones), and then create your approaches from them. Then compile to FS and check if everything is OK. If FS is confused, you might try deleting your versions of the stock navaids, leaving only the stock ones behind.
Click to expand...

I considered that, but all info I've read so far regarding having duplicate stuff = bad juju :/
For now I have created a fictional Terminal WPT with the same ident at the exact location of the VOR in question, the likes of which exists as well in stock scenery and in the real word. If no solution exists to import the stock navaids into user generated airports, then I'll probably have to live with it :laughing: . Flying the published approach by hand (for non VNAV/LNAV aircraft) will still be possible anyways since the VOR will still be there so..

Thnx for all your inputs though @hgschnell & @tgibson !
 
Did you update ADE to 01.78.7298?
Otherwise further discussion is not useful.
I created ZBAD Daxing, no stock airport, and got the Navaids of the stock files

navaids1.jpg
 
Hey @hgschnell
I have indeed installed version 1.78 already and its running exactly like my previous version, including the fact I still have 'Load Stock data' greyed out under Tools :/
At this point I'm thinking about just living with it, since I replaced the VOR fix with a WPT for AI purposes as mentioned before, and the simmer can still make the published approach using the VOR as it is also there from the stock files.
Fixing this was really more of a nitpicking issue than it actually 'breaking' my airport, as I sometimes get so annoyed by these little nuisances that I lock onto them until they're fixed :laughing: but since its not really that much of a big deal, and the fact that this is the only airport in my entire project faced with this issue I'm moving on for now :)

If someone comes up with a solution in the future though, please share with us all! :D

Thanks for all your inputs and help @tgibson & @hgschnell !
 
I have investigated this a bit and there seems no reason not to allow the import of some items. I have therefore changed ADE so it will allow users to import (or remove) the following element types when working on a user defined non stock airport
  • Comms
  • Nearby Airports
  • Navaids and Waypoints.
I can't say when this change will be available to the public but it will be in the next development build whenever that might be
 
You must log in or register to reply here.
Back
Top