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

Adding waypoints to ADE

Thanks for sharing this with us - it is very helpful :)
 
wilevi93 said:
Hello all, I've created a tutorial on how to easily and quickly add waypoints to Airport Design Editor to be used for creating approaches. It's the first video tutorial I've made, so bear with me with all the "uh's and u'ms"
Click to expand...

wilevi93

This is for information purposes.

Any Waypoint that nest inside the airport data record will show as a Terminal_Waypoint (blue color in ADE and the GPS).

Any Waypoint that nest outside the airport data record will show as a Route type Waypoint (magenta color in ADE and the GPS).

When you import a xml such as your list of Waypoints, ADE does not have the ability to know if they belong in the airport record or outside the airport record. At present any waypoints that are imported get listed outside the airport record which causes them to become route type waypoints instead of Terminal_waypoints.

When watching your tutorial I got the feeling that you need to do further work on your waypoint code utility but the problem is more related to ADE.

What needs to be done in ADE is add a selection window prior to any importing of a VOR, NDB or Waypoint that will set the Navaid inside or outside the airport record. If we had the ability to select a box that ask do you want these Navaids inside or outside the airport record then your imported waypoints would all list as Terminal_Waypoints (blue in color) and those are for building on approaches.

I like your utility and it saves a lot of time when adding multiple waypoints for updating FSX.

I don't want you to think the flaw is in your script code but rather something ADE needs added.

I am asking Jon to add this feature to the list so ADE can be more precise on what type VOR, NDB or Waypoint is being added when someone uses importing.
 
I have logged this. The reference is 10286
 
Too bad it won't work that good in fs9. It will only import the waypoints near the airport and there's noway to set the distance to 60nm like fsx ver can. Maybe in a future update fs9 ver can import up to 60nm. Otherwise I'm stuck manual entries.
 
why not make a tool to add to ADE that allows just navaid and fix/waypoints to be added, in and outside the airport bgl? similar to the appch editor
 
Last edited:
johnk51 said:
Too bad it won't work that good in fs9. It will only import the waypoints near the airport and there's noway to set the distance to 60nm like fsx ver can. Maybe in a future update fs9 ver can import up to 60nm. Otherwise I'm stuck manual entries.
Click to expand...

I am not sure I understand. It is a while since I looked at this but I do not recall any difference in the way ADE works with FS9 to FSX. If there is an issue then it might be a bug in ADE. Some more information would help
 
I tried koma. When I imported the xml waypoints. It only added the ones that were up to about 9nm. Anything farther out I had to add manually i.e. howry. I had no duplicates farther out than 9nm. When I had watched the tutorial for his program in fsx, he changed the test area radius to 60000, and that's only in fsx.
 
johnk51 said:
I tried koma. When I imported the xml waypoints. It only added the ones that were up to about 9nm. Anything farther out I had to add manually i.e. howry. I had no duplicates farther out than 9nm. When I had watched the tutorial for his program in fsx, he changed the test area radius to 60000, and that's only in fsx.
Click to expand...

As faras I know there is no difference in the code. The airport test radius should not have any effect. I have added this to the issues list to check it out [10290]. If this is a problem then it is a bug so we will fix it.
 
There is a dead link to a utility the OP posted to create waypoints automatically.
 
Hello:

This thread OP's website is offline, but can be viewed at:

http://web.archive.org/web/20130125085028/http://precisionfsn.com/developers/



That website's downloads at Wayback Machine were never cached, so perhaps an alternative might be this utility, still here at FSDev: :idea:

https://www.fsdeveloper.com/forum/resources/fsx-and-fs9-navaid-bgl-updater-scripts.209/


Related links to topics on equivalent utility features for FSX:

https://www.google.com/search?q=htt...G6BgQIARgKkgcDMi4zoAffCw&sclient=gws-wiz-serp

GaryGB
 
Last edited:
You must log in or register to reply here.
Back
Top