Aircraft Banking at climb and Cruise and new problems.

[Joe D]

Hello Forum,

I posted yesterday about my aircraft banking and straying off course and then straining to get back on course. I flew KORD-KSTL last night without my Active Sky engine on and still I have the same problem. Again, recently I have purchased the PMDG 747-400, Q Sim 757, and Level D 767 software as well as the new IS Delhi scenery.

Also, I tried to update my FSIUPC (Registered) and now my headings are all off. For example my default airport is KSEA and starting out on runway 34R the heading is 341 but my instruments say 240. Not sure what happened there.

I really do not want to strip my SIM I have three years of software and hours of tweeking planes and panels. Any help would be great.

Running: FS9
System: Jet Line System
Weather Software: Active Sky 6.5 and REX

Joe
****

[NikeHerk67]

Hi Joe,

Not being a computer guru I'm the King of Undo.
I'd think about what I'd done recently then check the easiest files first and so on to more difficult uninstalls if necesary....

First, I'd check the scenery file by going to the scenery library and simply removing the check mark in the box for the IS Delhi scenery.
It doesn't remove or change the add-on scenery, it simply won't load at FS9 startup until place the check mark in the box again.....a very simple procedure.

Then perhaps, read again, the FSIUPC update text file and make sure it's installed correctly. It has been a long time since I've upgraded.

When upgrading FSUIPC I believe you need remove or delete the old DLL file.....again not positive of this.
You should only have one FSIUPC.DLL file in the Modules folder with the recent date.

It is much too early to think about uninstalling and reloading FS9

Not with all the expertise we have (not me) here in the forums.

[Joe D]

Hi Herk,

Thanks. I will keep trying. I actually remembered I downloaded some freeware scenery as well.

[ronzie]

Some scenery add-ons modify the magdec.bgl in FS9\scenery\BASE\scenery with one at higher priority. Try setting up a new folder such as prioritybgls\scenery and copy the original version in the BASE folder to there and place that new folder at the top (number 1 position) of your scenery library. The original magdec.bgl should have a date of 2003 on it.

Run the flight1 free registry checker I noted in your other post. FSUIPC full versions now use the FS9 path in the registry first in their .exe installers. Then for interim versions you just replace the .dll overwriting it from the .zip. You do not have to delete the FSUIPC.dll first. Settings in FSUIPC.ini are maintained. For a further test of FSUIPC do this carefully. Make a safe copy of FSUIPC.ini in your modules folder in a folder totally outside of your FS9 folder such as in your My Documents folder. In your modules folder rename fsuipc.ini fsuixxx.xxx. FSUIPC should create a new .ini file. I tghink it still w ill detect your paid .key file and if not perform the registration procedure in the FSUIPC tab when running FS. The new .ini file will not have any of your controller mapping nor AS settings in it but it will detect AS. See if this corrects anything.

The jetline suites from some years ago that I have do not use FSUIPC. That leaves the magdec.bgl or your FSUIPC settings (probably control mappings and sensitivities) as suspect. By using a virgin fsuipc.ini that will be your FSUIPC test.

I have more details in your AVSIM post.

Hope this helps.

[joedav]

Hi Guys,

Guess what? It wasn't the IS Delhi scenery it was the new KSTL I bought that was messing up my headings. Question, the KSTL is payware so how do I get the scenery to work without it causing havoc on my headings.

I did the flight 1 Registry so we will see if that takes care of the off course issue.

Thanks All

JD

[ronzie]

Look in the scenery folder of your KSTL add-on. Is there a magdec.bgl in there? I think if you follow the procedure of creating a new top priority folder with the copy of the original magdec.bgl in it, your STL add-on will use its own first and then the other airports will use the default. See how this works.

Sometimes developers change magdec.bgl to work with new or modified ILS, VOR, or NDB or other navaids in the area. Another reason is for dealing with runway renumbering. navaids in design use specified headings but pull in the mag variation offset from magdec.bgl.

Now an ILS/LOC does not use the same principle in the navcomms as VOR. An ILS sends out two fixed beams one left and one right of the defined center line for those (which may be offset from the runway center line) and in LOC/ILS mode those two fixed beams are compared with a null indicating you are between them. Magdec should not affect them but it might affect how an RMI indicator might point to them. VORs are a different technique where a fixed broadcast reference is sent out along with a sweeped beam in all directions. The phase difference of those two indicates where you are in relation to your chosen course on the VOR indicator or as pointed to by an RMI indicator.

So that is why a developer might change the magdec.bgl file.

[joedav]

Ronzie / Herk,

All is good. I looked in the Scenery folder for KSTL and there was no magdec.bgl I I downloaded this file from AVSIM and placed it in the KSTL scenery folder. All Runway headings work and my aircraft stay on course with no banking.

Thanks for all your help on this.

Joe
****

[ronzie]

Which file did you download? Was it a restoration of the original or something else. Does it work OK with other airports?

[Joe D]

Ronzie,

I just googled it and downloaded a copy of it and placed in the KSTL scenery folder. Seems to be working fine I've done two flights since then (KORD-KSTL & KSEA - RJAA) using PA A320 and PMDG 747 it's working just fine.