I've created the flightplan below by selecting CAU4 as the starting airport, creating Batnuni Airstrip as a user waypoint and adding it to the flight plan, then used the "Edit" button to create three VFR waypoints in between (wpt01, wpt02, wpt03):



Note that the flight plan is more or less a straight line on a true track of 186 degrees. There is no wind. I'm using the ORBX Pacific Fjords addon scenery.

If I mouse over CAU4, I can see that the magnetic variation is 24.0 degrees East. This is correctly subtracted to give me a magnetic track of 162 degrees to wpt01.

Mousing over wpt01, the magnetic variation here is 20.67 degrees East. However, in this case the magnetic deviation appears to be added rather than subtracted, giving an incorrect magnetic track of 207 degrees to wpt02. Something similar appears to happen at wpt02 (magvar is 20.59 degrees East) and wpt03 (magvar 20.51 degrees East).

I'm no expert, but it does look like the waypoints that are added using the "Edit" button and moved around using the little square do not handle magnetic variation correctly?

Tom

Quote from: Skynet on November 26, 2010, 05:28:56 PM
In Windows, Open the Control Panel. Then select Region And Language. You'll see a drop down called 'Format'. Make a note of its current setting. Change this to English (there are several verieties of English listed, it doesn't matter which one you pick) and click 'Apply'. Now build the database. Once it is finished, switch back to this dialog and change the Format back to its original setting.

For those (like myself) who need everything spelled out in detail, make sure you restart Plan-G after changing region settings to "English" and before you rebuild the database.

Check the number formats used in Plan-G, e.g. the lat/lon in the bottom left corner of the window. If the decimal separator is "." (period) you are good to rebuild.

Great update - at an unbeatable price  :laugh:
Thanks!
Tom

Sounds like the problem I'm having - this is a zoomed in view of PAKT:



I see in another thread that using "," for the decimal point is causing problems, so that's probably it (in my case at least).