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

MSFS20 Problem with Navigraph and MSFS default Navdata differences

A

Amorisia

Messages
22
Country
france
Hi everyone,

I just bought Navigraph to try it for the first time and have been very impressed with the updates for most airports navaids around the world. But because AIRAC cycle is different between Navigraph and MSFS, how to make an airport SID and STAR available for people who have Navigraph and those who do not at the same time ?

As an exemple, I am working on ZUTF airport, and waypoint regions are different for same VOR. Best exemple in my case is the VOR WFX near Chengdu in china.
Navigraph defines it in the ZU region but MSFS defines it in the ZP region (was ZU also before SU4).

MSFS code
XML: 
<Next waypointRegion="ZP" waypointIdent="WFX" waypointType="VOR" altitudeMinimum="5443.0F" />

Navigraph code
XML: 
<Next waypointRegion="ZU" waypointIdent="WFX" waypointType="VOR" />

Source from file ATX09020.bgl in both versions.

Should I declare waypoints and SID/STARS two times to work in both AIRAC ? If I only use one system, people using the other system will get CTD...

Many thanks for your advices,
 
Hi, well you touched a very sensible area but the solution is right in front of you. You need to exclude all the local waypoints/departures/approaches/... but have to redefine them in your own region. You can call it "X1" i.e. That makes the waypoint to your waypoint that's used by all MSFS users that have your mod in their community folder. I hope I made myself clear.
Best regards Guido
 
GuidoH said:
Hi, well you touched a very sensible area but the solution is right in front of you. You need to exclude all the local waypoints/departures/approaches/... but have to redefine them in your own region. You can call it "X1" i.e. That makes the waypoint to your waypoint that's used by all MSFS users that have your mod in their community folder. I hope I made myself clear.
Best regards Guido
Click to expand...
Thanks for your reply, I will try. But what if the waypoint is used by many airports around? If I delete it to use it for mine, does other default airports that are using it will find it? Because for other airports msfs code should find the waypoint in its real region, so my airport will work but other will crash ?
 
Hi, my experience was similar. Me adding Navigraph data upset the users so I simply did the following:
1. Left the existing Waypoints/Approaches etc as per the MSFS - Don't set the delete statements in the airport
2. Added my own approaches and waypoints making sure that mine were unique
3. Did nothing for Navigraph as it seems to want to do it's own thing

Having done that, I no longer have had anyone using Navigraph complain (assuming they still use my airports), nor "plain" MSFS users.

As stated by navigraph:

"the issue is the addon scenery because the developer deleted all terminal procedures in his scenery and had created his own terminal procedures and the addon sceneries have a higher priority as the navdata package (which is ok so far) and therefore the scenery overrule our data. This is generally a bad design and should be avoid from the scenery developer because when something changed in the AIRAC the developer must add it and you must update the scenery. Therefore it makes sense to split the navdata from the scenery. Means the scenery contains only scenery elements and the navdata come from the sim or our navdata package. I have posted the recommended settings in the FAQ FAQ - Double scenery elements (point #1) possible you can forward these settings to the developer. After that and when the terminal procedures are excluded in the scenery you can use the scenery with our navdata package or with the default navdata in the sim."

Hope this helps.
 
Well Ironpot is absolutely right and yes the deletion of the waypoint will also make any use of it no longer working. I was talking about the exclusive use of waypoints for approaches etc. for one airport.
So inventing your own nac data is the only general solution to your project.
 
Ironpot said:
Hi, my experience was similar. Me adding Navigraph data upset the users so I simply did the following:
1. Left the existing Waypoints/Approaches etc as per the MSFS - Don't set the delete statements in the airport
2. Added my own approaches and waypoints making sure that mine were unique
3. Did nothing for Navigraph as it seems to want to do it's own thing

Having done that, I no longer have had anyone using Navigraph complain (assuming they still use my airports), nor "plain" MSFS users.

As stated by navigraph:

"the issue is the addon scenery because the developer deleted all terminal procedures in his scenery and had created his own terminal procedures and the addon sceneries have a higher priority as the navdata package (which is ok so far) and therefore the scenery overrule our data. This is generally a bad design and should be avoid from the scenery developer because when something changed in the AIRAC the developer must add it and you must update the scenery. Therefore it makes sense to split the navdata from the scenery. Means the scenery contains only scenery elements and the navdata come from the sim or our navdata package. I have posted the recommended settings in the FAQ FAQ - Double scenery elements (point #1) possible you can forward these settings to the developer. After that and when the terminal procedures are excluded in the scenery you can use the scenery with our navdata package or with the default navdata in the sim."

Hope this helps.
Click to expand...
Thank you for your reply. And yes my problem? is the second point as I use some existing VOR that have different region in msfs and Navigraph, so I should declare it in a new region to make it unique and use my own. Yesterday I just created two packages, one for Navigraph and one for MSFS. The Navigraph one just do not have any nav data and I do not delete existing ones so my airport use Navigraph nav data for my airport and? this is great.

Thank you
 
Great, although you don’t need a different region. Just make sure your waypoints etc have a unique name. I actually use the same and prefix with an x or something to make them unique
 
You must log in or register to reply here.
Back
Top