Magnetic Declination 

 

http://www.flaps2approach.com/journal/2013/1/16/magnetic-declination-fs9-fsx-navigation-datebase-update.html

Does any one know which BGL. file I will open to make Var correction. I utulized BGL Magnetic Variation Corrector "MVC" tool and opened one by one all BGL files and received the following messages: "This BGL file doesn't contain changeable record" Am I opening wrong BGL files other the outlined in bellow installation direction.

Thanks for your help

 

 

This is "Read me txt"

"Correction of other embedded BGL magnetic variation data (ILS, Airport, navaids, waypoints)

-------------------------------------------------------------------------------------------

Optionally, the "BGL Magnetic variation corrector" utility can update other magnetic variation data (that is airport, ILS, navaids and waypoint data) inside selected BGL files. I recommend you backup your original FS files before performing this operation (the program will propose it by default)."

 

 

 

http://img853.imageshack.us/img853/41/var2.jpg

http://img534.imageshack.us/img534/8813/var2j.jpg

Don't remember exactly what I did but I think I chose the ones in the scenery directory in your FSX folder. 

Guys,

 

there is no need to apply the Magnetic Variation Corrector to BGL Files. It has no influence on the navigation of the aircrafts.

 

It only changes the displayed courses on the map view (world/map) within the navaid list.

 

The indicated values on the aircraft instruments and SHIFT + Z have already been changed by the magdec.bgl

 

Jan-Paul

Ommi,

 

" scenery directory"

Which folder, scenery library or scenery,cfg file?

THX

 

Jan-Paul

 

"there is no need to apply the Magnetic Variation Corrector to BGL Files. It has no influence on the navigation of the aircrafts."

 

Please check the following screenshots.

 

http://img689.imageshack.us/img689/4015/747kewr2.jpg

 

 

How do you analyze  747 actions not intercepting  toward to ILS bar? 

 

THX

Russell Hi.

Md-11X and 747-400X has same problems. Almost all airports ILS landing must be done by hand flying. NG737X no problem.

Try my home base KEWR 22R with 747 and MD11.

Here is my 747X ILS auto landing RW22L at KEWR,yesterday night.

 

http://img818.imageshack.us/img818/4015/747kewr2.jpg

 

http://img208.imageshack.us/img208/7641/747kewr1.jpg

 

 

Pete Hi,

Thanks for your test flight.If you landed without any incident, then there is some thing going wrong in my FSX. May be I should get help from PMDG support..

 

Hi just noticed that you asked us to try 22R which I did with no problem but the pic is of 22L and you say that's the problem approach I'm sure you have the correct runways selected but I'm just checking as the localizer would look just like that if tuned for 22R as it looks way too far off track to be tracking 22L. The reason I thought of that is that the NG uses manual ILS tuning but the 747 and MD both auto tune. Are the frequencies definitely the correct ones?

Sorry I'm sure you have done everything right but wanted to make sure

Russ

 

Sent from my GT-P3113 using Tapatalk 2

 

Just did jfk to ewr with NGX and 747f and both landed correctly aligned on 22r

Wl try the md later I haven't applied the fix yet

 

Sent from my GT-P3113 using Tapatalk 2

 

Just to confirm I ran all the tests with 22R NOT 22L as requested but your pic and problem runway are posted as 22L

 

Sent from my GT-P3113 using Tapatalk 2

I just made another test flight KEWR RW22R ILS Freq 110.75 ILS ID IJWN

 

Please see the self explanatory events of flying

 

1-Taking of from RW22R ILS lineup

http://img5.imageshack.us/img5/4701/74740022r1.jpg

 

 

2-747 on Long final it looks like line up again RW22L not 22R

http://img703.imageshack.us/img703/8827/74740022r2.jpg

 

3-747 short final and turns right toward to middle taxiway

http://img856.imageshack.us/img856/236/74740022r3.jpg

 

4- 747 rudder turns left plane bank toward to RW22R

http://img835.imageshack.us/img835/6226/74740022r4.jpg

 

5-747 rudder still try to turn left but plane banks to right and touchdown edge of 22RW

http://img834.imageshack.us/img834/1366/74740022r5.jpg

 

This is the end of the story. If you can identify what is causing this problem I will really appreciat.

I hope some memeber of PMDG team is monitoring this post

 

Thanks to all,

Going from memory of the 747 FMS could u post screenshots of your TO/App and Nav/Rad pages? Legs page too thx... Want to make sure I'm using same data exactly as you when on approach

 

Sent from my GT-P3113 using Tapatalk 2

Here is it:

 

TO with Flap 10

http://img199.imageshack.us/img199/7242/747fmc1.jpg

 

Nav/Rad

http://img59.imageshack.us/img59/4892/747fms2.jpg

 

APP with Flap30

http://img195.imageshack.us/img195/200/747fms3.jpg

One good and one bad news.

 

Good News, after 4 hours work I fixed the problem and 747-400X landed on the Numbers, Perfect lineup with ILS

 

Bad News: I went through many PMDG files, Dll, Scenery, Senery Cfg, Data files and One complete FSX uninstall/reinstall and acceleration at the end I fixed the problem IF YOU ASK me how did I fix the problem,possibly  I cannot answer the question. .

 

1-Perfect ILS

http://img585.imageshack.us/img585/8065/74740022r6.jpg

 

2-747 on TARGET

http://img853.imageshack.us/img853/5378/74740022r7.jpg

 

3- Queen's touch down

http://img194.imageshack.us/img194/310/74740022r8final.jpg

 

 

Case closed and thanks to all for theire help to me..

thanks for the info and yes I understand how you cant say HOW it was fixed but Im glad you have it sorted! Happy landings!

I have still one question to solve the last puzzle?

 

 

When I use Registry Repair Tool. 747 on target with ILS. Please look at number 2 circle ILS ID course 220 and Number 1 cirle ILS course 219 as per approach plate of KJFK RW22R.747 will on target.

http://img708.imageshack.us/img708/7852/74740022r61.jpg

 

 

If I don't use the Registry tool 747 does not align with ILS and will crash..

If you look at number 2 circled, ILS ID heading 206 and Number 1 circle ILS heading course 219 according the approach plate.747 will not go toward to 219 correct course , but will go to wrong course 206.

Do you have any idea where is Number 2 circle data is coming from as 206. Is it possible from Aircraft.cfg file or from where?

http://imageshack.us/a/img594/1715/74740022r21.jpg

The course displayed on the PFD (number 2 circled) is always the correct one, as this is the result of the FS TRUE Bearing + the variation stored in the magdec.bgl

 

All other courses have to be ignored. 

 

 

So always look what the PDF displays and set the NAV/RAD course according to that value. Otherwise you are going to fly an offset. 

 

The 206 is the correct "FS" course in your case. 

 

Updating the magvar.bgl helps to get that value closer to the real one. 

 

 

Jan-Paul 

Jan-Paul,

 

I  inserted 110.75/206 NAV/RAD and updated magvar.bgl , 747 was offset from ILS path.

Only way to correct the 206 course for KEWR 22R, I have to run FS Registry Repair tool. Then course changes to 219 from 206.

and 747 remains  on track with ILS path,

 

 It looks like If I want to fly with 747X and MD-11 X I have to run the Registry Repair Tool.

737NGX has no problems.

Thanks for your reply.

Yes, Registry repair tool will fix it. You only have to run it once (Always as admin) although you may need to run it any time you install new scenery files (AFCAD's too). 

 

My usuall way of doing things these days is

 

1: Install a new addon.

2: Run Registry repair tool

3: Run magvarfix (Magnetic variation fix) http://forum.avsim.net/topic/336155-magnetic-variation-updates-for-fs9-and-fsx/
4: Run registry repair tool a second time making absolutley sure it's being run as admin.

5: test fly the MD11 and/or 747 at KJFK (where I often get the issue) and at the newly added scenery. - This test flight can be as simple as setting up the FMS to have a departure runway of "the runway I spawn on" and checking that "runway centreline" matches the runway centreline on the NAV display in Map mode (With the departure runway set in the FMS).

 

Once this is confirmed, there's no reason to use the repair tool again till I install something new.