After loading Shez' KLGB2010, I noticed that the headings in the sim and in the aircraft were off by 18*. For example, setting up at KLGB on RWY 21, the correct mag hdg is 121*, but the sim showed 139* as well as the nav display on the aircraft. This occured at other airports as well. Removing the scenery corrects the problem.I contacted Shez about the problem and he tested it out and has no such issue on his system. He mentioned that this may have been a subject here at AVSIM and that I should post here to see if anyone had the same problem and was able to find a correction for it.So does anyone remember a discussion about this problem and if there was a solution?Thanks,Jim D.

After loading Shez' KLGB2010, I noticed that the headings in the sim and in the aircraft were off by 18*. For example, setting up at KLGB on RWY 21, the correct mag hdg is 121*, but the sim showed 139* as well as the nav display on the aircraft. This occured at other airports as well. Removing the scenery corrects the problem.I contacted Shez about the problem and he tested it out and has no such issue on his system. He mentioned that this may have been a subject here at AVSIM and that I should post here to see if anyone had the same problem and was able to find a correction for it.So does anyone remember a discussion about this problem and if there was a solution?Thanks,Jim D.

I just checked my installation of Long Beach by Shez (and the SP 1 for it) - found no runway 21 at all - but the compass setting was correct on the other runways I checked.No clue why yours should display differently. Have you installed a replacement magdec.bgl file perhaps?

After loading Shez' KLGB2010, I noticed that the headings in the sim and in the aircraft were off by 18*. For example, setting up at KLGB on RWY 21, the correct mag hdg is 121*, but the sim showed 139* as well as the nav display on the aircraft. This occured at other airports as well. Removing the scenery corrects the problem.I contacted Shez about the problem and he tested it out and has no such issue on his system. He mentioned that this may have been a subject here at AVSIM and that I should post here to see if anyone had the same problem and was able to find a correction for it.So does anyone remember a discussion about this problem and if there was a solution?

Absolutely. This has come up time and time again. It is caused by add-on sceneries modifying your default arrangements and it is very hard to find the culprit.As far as I am concerned, the best solution is to take a copy of your default magdec.bgl file and place it in a scenery folder that loads after all other sceneries. This ensures it over-rides any wrong files. I'm pretty sure this will resolve your issue.For more information, search this forum for magedec.bgl.John

I just checked my installation of Long Beach by Shez (and the SP 1 for it) - found no runway 21 at all - but the compass setting was correct on the other runways I checked.No clue why yours should display differently. Have you installed a replacement magdec.bgl file perhaps?

My error Dave, meant to say RWY 12. Correct hdg is 121*, mine read 139*. No, I didnt install a new magdec.bgl, but I'll search the forums and give the next poster's suggestion a try.Jim D.

Absolutely. This has come up time and time again. It is caused by add-on sceneries modifying your default arrangements and it is very hard to find the culprit.As far as I am concerned, the best solution is to take a copy of your default magdec.bgl file and place it in a scenery folder that loads after all other sceneries. This ensures it over-rides any wrong files. I'm pretty sure this will resolve your issue.For more information, search this forum for magedec.bgl.John

Thanks John, I'll do a search and give it a try.Jim D.

My error Dave, meant to say RWY 12. Correct hdg is 121*, mine read 139*. No, I didnt install a new magdec.bgl, but I'll search the forums and give the next poster's suggestion a try.Jim D.Thanks John, I'll do a search and give it a try.Jim D.

Well I downloaded the latest MAGDEC file and placed it in the folder FS9/Scenery/Base/Secenry and reactivated Shez's KLGB2010, but was still wrong. It did not correct. After a few more attempts using one older MAGDEC file which didn't solve the problem, I created a new folder named MAGDEC with a subfolder called scenery, placed the newest magdec.bgl in there and put it in the scenery library, top entry. Now problem is solved. I'll see how it works with the new mag variations that were updated. If it doesn't work correctly, I'll reinstall the original one from the disks.Thanks for the help.Jim D.

Well I downloaded the latest MAGDEC file and placed it in the folder FS9/Scenery/Base/Secenry and reactivated Shez's KLGB2010, but was still wrong. It did not correct. After a few more attempts using one older MAGDEC file which didn't solve the problem, I created a new folder named MAGDEC with a subfolder called scenery, placed the newest magdec.bgl in there and put it in the scenery library, top entry. Now problem is solved. I'll see how it works with the new mag variations that were updated. If it doesn't work correctly, I'll reinstall the original one from the disks.

Jim - using an "updated" magdec.bgl may lead to all sorts of other problems - I highly recommend using a copy of your original FS one and placing it in that new scenery folder you have created. That should put everything back to normal.Best wishes,John

Jim - using an "updated" magdec.bgl may lead to all sorts of other problems - I highly recommend using a copy of your original FS one and placing it in that new scenery folder you have created. That should put everything back to normal.Best wishes,John

Thanks for the advice John. Jim D.

Well I reloaded the original magdec file from the disk, installed it in the new folder I created in the scenery library, and while the headings were correct, my PMDG 737 would not follow the FMC path correctly.Then I deactivated the KLGB2010 scernery and all was OK, until I reached cruise alt of 32000' taking off from Seattle to Ketchican,AK. Shorly after, the screen went black, but the sim seemed to be working as ATC was still yapping away. I've had this black screen occur before, not always, but a majority of time some where over Vancouver.I still don't know why I'm having these issues with the KLGB2010 scenery activated.Jim D.

Hello,Dunno if this can help .. but ...One week ago I had the same problem .. and seem's it was after the install of this scenery ....How I solved:I deleted (but for the sake of safety made a copy of) the files in the folder:C:\Documents and Settings\YOURNAME\Application Data\Microsoft\FS9\facilitiesI relaunched FS2004Note: I have also a custom default flight with a default aircraft.So when in the game (with default flight loaded) all was good (course and heading correct for the default airport I use SSR Mauritius)I stopped FS2004 and relaunched and the error was there again !So I redeleted the files and launched again FS2004So when in the game (with the default flight loaded again) all was good again !!But I go to select flights and selected the default flight I use and ticked the box for make it my default flight again.The flight loaded in the game and all was good !!I stopped and relaunched FS2004 the default flight loaded and all was good again !! and never had probs after ...Dunno if it's make sens for you but that worked :)Regards.Gus.

Well I reloaded the original magdec file from the disk, installed it in the new folder I created in the scenery library, and while the headings were correct, my PMDG 737 would not follow the FMC path correctly.Then I deactivated the KLGB2010 scernery and all was OK, until I reached cruise alt of 32000' taking off from Seattle to Ketchican,AK. Shorly after, the screen went black, but the sim seemed to be working as ATC was still yapping away. I've had this black screen occur before, not always, but a majority of time some where over Vancouver.I still don't know why I'm having these issues with the KLGB2010 scenery activated.Jim D.

Did another flight and this time no black screen. Made the flight to Ketchikan without incident. So maybe all is well there. Still have KLGB2010 deactivated.Jim D.

Hello,Dunno if this can help .. but ...One week ago I had the same problem .. and seem's it was after the install of this scenery ....How I solved:I deleted (but for the sake of safety made a copy of) the files in the folder:C:\Documents and Settings\YOURNAME\Application Data\Microsoft\FS9\facilitiesI relaunched FS2004Note: I have also a custom default flight with a default aircraft.So when in the game (with default flight loaded) all was good (course and heading correct for the default airport I use SSR Mauritius)I stopped FS2004 and relaunched and the error was there again !So I redeleted the files and launched again FS2004So when in the game (with the default flight loaded again) all was good again !!But I go to select flights and selected the default flight I use and ticked the box for make it my default flight again.The flight loaded in the game and all was good !!I stopped and relaunched FS2004 the default flight loaded and all was good again !! and never had probs after ...Dunno if it's make sens for you but that worked :)Regards.Gus.

Gus, I'll give this some consideration. Thanks.Jim D.