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

Navigation Aid Database Update

W

wilevi93

Messages
58
Country
us-alaska
Hello, I am looking for people with FS9 or FSX to test a project that I am in the process of finishing up. It is a database update for the default FS navigation aids. What it does is updates the station's compass variation, and the navaid position. This would allow the use of current aeronautical charts for VOR navigation in Flight Simulator without becoming off course(Which I've noticed to be a problem). There is only data available for the USA. Along side it I might put out an update of waypoints and intersections.

Anyone interested should PM me, And I will inform you of the project's status, and E-mail you a limited version of the package, along with installation instructions, and what VOR's and airways you should fly along.
 
I guess you are aware that it is generally not possible to move Navaids in FSX without either causing duplication or potentially a CTD. Also that moving any navaid that is part of a route without also moving the associated route waypoint will most likely cause a CTD if you move the navaid more than a short distance of some other unexpected results in the GPS etc.

The only way around is to replace the stock NV files - Generally we discourage that of course.
 
Well, that's why I wanted someone other than me to test it out. So I could either confirm or disprove that my update could be used without causing crash to desktop, or other undesirable results. I have tested it with very good results in relation the the VOR compass variation, although I don't think I've encountered a situation where the navaid has moved to a different place.
It is my experience that scenery in the Addon Scenery folder takes precedence over the stock data in the case where a duplicate exists, ( I could be wrong)
 
Changing MagVar should not cause any problems. The real issue comes in trying to move them. You are right that Addon Scenery Takes precedence over stock in most cases. However there is generally an 'exclusion' in the addon scenery file telling FS to not use the default. No such thing seems to be available for navaids/waypoints (other than terminal). So we get erratic results. Our research (done by Jim Vile) indicates that you can usually move such things a few miles without a problem. After that you will get duplication and two of the same navaid - not desirable. Worse you may cause a CTD if there is a route associated with the navaid (there will be a waypoint co-located with the navaid). Finally the safe move distance is not consistent and in the end became so small we just don't think it safe to move them at all...

That is not to say that things will work in some circumstances so you or others will certainly be able to show cases that disprove the above but generally it is a dangerous thing to do.
 
scruffyduck said:
Changing MagVar should not cause any problems. The real issue comes in trying to move them. You are right that Addon Scenery Takes precedence over stock in most cases. However there is generally an 'exclusion' in the addon scenery file telling FS to not use the default. No such thing seems to be available for navaids/waypoints (other than terminal). So we get erratic results. Our research (done by Jim Vile) indicates that you can usually move such things a few miles without a problem. After that you will get duplication and two of the same navaid - not desirable. Worse you may cause a CTD if there is a route associated with the navaid (there will be a waypoint co-located with the navaid). Finally the safe move distance is not consistent and in the end became so small we just don't think it safe to move them at all...

That is not to say that things will work in some circumstances so you or others will certainly be able to show cases that disprove the above but generally it is a dangerous thing to do.
Click to expand...

Even Changing "Magnetic Variation:, is opeing up Pandora's Box.

You will find that many CURRENT "REAL WORLD" Charts are still using really OLD values of Magnetic Variation.

For Example KOSH OSHKOSH

REAL WORD CHARTS: Magnetic Variation from 1975 is 1° East

Chart shows ILS 36 heading to be 359 degrees. ( based on that 1975 Variation)

But Today, when you fly the ILS, you will be on a Magnetic Heading of about 4.5 degrees, because the Magnetic variation has changed significantly from 1975 ( Big Surprise)

But in FSX, MS took current Magnetic Variations at the time of FS8 / FSX, so in FSX, the magnetic Variation is BOTH, not the same as Current Real World Charts, and also not the same as the current REAL World variations.

So, what are you intending to set the Variation to ? Chart, FSX or Current 2011 Real world.

Yes, in case you are wondering, OSHKOSH's Approach Plates are way due for a Real World Update to the correct Magnetic Variation. Current Chart value is now more than 5 degrees in error !!! (Your tax dollar NOT at work ? )

Interesting stuff !!

Geoff
 
Well, scruffyduck was right. I tested moving a VOR a few miles. The sim loaded just fine, however upon opening the map, the sim crashed to desktop. That's not quite the level of reliability that I was looking for:(. Magnetic variation is able to be changed with good results however.

In reference to Geoff's question, In the real world, VOR stations are set to approximate magnetic variation at the time of the re-setting. That variation is on file at the FAA and is what appears on the headings of victor and J airways on En-route charts. This may over time skew away from actual compass variation in the area of the station.

My update sets the simulator navaids variation more closely aligned with what the real stations are set to.

This is probably more important in farther north areas where the magnetic variation moves faster and the VOR stations are re-set more often.
 
Maybe MS Flight will give us some extra tools for navaids...........
 
Magnetic variation is able to be changed with good results however.
Click to expand...

Only for the VOR's not the airport or the ILS's.

The Mag Var listed in the properties of the VOR is a stand alone value and can be updated. However as Geoff points out updated to what.

If you do a state like Alaska then you have to do the entire world so all VOR's outside that state read To/From properly between VOR's.

Now comes the problem with all the VOR Approaches and associated Transitions. The MagDec.bgl controls all the world MagVar except the VOR's so there is no way to update the airport, runways, ILS's etc.

We can only hope newer versions will allows us more flexibility.
 
It's done!

I'm Finished with the database for North America. That includes USA, Canada, part of Greenland, and part of Mexico, among other countries. The final version replaces the default files. I have done preliminary testing with good results.

I still need volunteers to test out a few different parts of the database.

I will give a free version of the final program to anyone who helps out.
 
I'd be happy to take a look at the files
 
You must log in or register to reply here.
Back
Top