Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 19, 2018 14:00:30 GMT
I found AIE very helpful at fixing the magvar in individual airport BLG files, for example, those shipped with Orbx NA SoCal. Does anyone here know how to automate the magvar fix for all BGL files in a folder? Even if it can be down with command line, I can write a DOS BAT file to achieve it.
Thank you!
|
|
|
Post by Herve Sors on Dec 19, 2018 16:41:05 GMT
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Dec 20, 2018 15:49:38 GMT
Thank you, Hervé.
I understand your point -- runways and their ILS are defined in BGL files using physical coordinates, so their locations and true heading are clearly not affected by magvar. I think you are right.
What still puzzles me was: after each navaid/magvar file update, FsiPanel complains I land too left or too right of the runway centerline even if I land exactly on the centerline graphically. It was not a problem before the update, and after update, the problem happens to Orbx runways. Technically, the centerline deviation should not happen because the runways are not affected by updating either the magdec.bgl file or other navaids. I assume FsiPanel computes centerline deviation by comparing coordinates, which do not involve either magvar or fixes. Strangely, I noticed I can solve the centerline deviation problem by fixing the magvar values in the Orbx airport BGL files and letting FsiPanel re-run Makerunways. (The problem is that I have to this do for each airport I am going to land at.) According to you, fixing magvar in runway BGL files does absolutely nothing. Perhaps, my solution was just my illusion. I will try on Orbx airports that I haven't fixed their magvar values yet. Thanks again!
|
|
|
Post by Herve Sors on Dec 20, 2018 16:14:07 GMT
Sorting it out may require you know how FsiPanel (I don't know) evaluates deviation from runway centerline. May be you could ask them If airport magvar has an effect, I suspect they are calculating and using somehow runways magnetic headings from it and this is incorrect. In the simulator, runway magnetic heading should be calculated from its true heading + current local magnetic variation at runway position from the magdec.bgl file. Indeed each airport (not runway) has a magnetic variation value in its BGL record (fixed part, offset 0x24). It is this one that can be changed in AIE but it does nothing in the sim AFAIK The situation is different on airport charts since, usually, the published airport magnetic variation is applied to all runways so as to indicate their magnetic orientation
Regards
Hervé
|
|