After not having used FS2002 in several months I tried to take a short flight from Riverside Muni (RAL) to Big Bear Airport. After taking off I swung around to a heading of due north. My flight skills are a tad bit rusty and I had my hands full just keeping my plane airborne. It wasn't until a few minutes later that I happened to look up and discovered I was heading toward the coast! A quick glance at the VOR1 showed my heading to still suppose to be due north. I brought up the magnetic compass and it too said I was heading due north!I reloaded FS2002 and noticed that the VOR1 and magnetic compass on my start up aircraft situated at ONT both gave the correct heading. As soon as I change planes and/or airports though they both start giving readouts 180 degrees off!I've installed a whole bunch of addons lately (incuding FDC, 737NG, USA and World Extreme Lanscapes, Ativesky, Emma Field, and Ultimate Traffic), but I have no idea which, if any, of these are responsible for this problem or if it was caused by something completely unrelated (like corrupted files). The question is how to fix the problem? Would reinstalling FS2002 over itself correct the problem or something simpler do the trick (like editiing a cfg file of some kind)?If anyone has encountered this problem (which does NOT exist in FS2004) and can help me out of his weird situation with FS2002 I'd love to hear from you!

Scott,I still use FS2002 and have had this problem more than once. It has always been due to recently installed 'addon' scenery. When I removed the offending scenery, the problem went away.I think I have maxed out my addon scenery, because now, when I add any more scenery, the sim starts doing strange things. When I remove it, or remove some old scenery that I don't really care about anymore, the problems stop.Hope this helps.Cheers,Bob

Hello Guys!I ran into the same problem with FS2004 recently. Take a look at a thread I posted a couple of days ago that talks about the SUMU addon scenery and a corrupted file within it that causes this.http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchHope this helps!Sincerely,Dennis D. Mullert

FS9 Afcad files aren't compatible with FS2002.

I use FS2002, and I installed a FISD scenery for FS2004. The magnetic headings went crazy and I installed it straight away. Make sure you don't have an FS2004 scenery installed ;)

FS9 Afcad files aren't compatible with FS2002Search for AF2.bgl files in all addon sceneries.

Bob,Do you happen to recall which addon scenery which caused the problem for you? In addition to Abacus USA and World Extreme Landscape scenery addons I have all the MegaScenery and MegaCity scenery addons. I recently moved the MegaScenery and MegaCity addons to an external hard drive. The thousands of files that make up these addons was giving my backup software a major case of heart burn (I haven't been able to complete a "disaster" recovery backup since installing them all)! When I reinstalled them to the extermal drive I had the installer install them into both FS2002 and FS2004. Could this have caused the problem? Originally, I installed the Northern California, Southern California and New York addons to FS2002 onlyand the PNW and Mid-Atlantic addons to FS2004 only. All the MegaCity addons were installed to FS2004 (only the latest Atlanta addon gave me a choice anyway). I guess I'll try uninstalling the Megascenery and Abacus addons one by one to see if the problem goes away somewhere along the way...Thanks!Scott

>I use FS2002, and I installed a FISD scenery for FS2004. The>magnetic headings went crazy and I installed it straight away.> Make sure you don't have an FS2004 scenery installed ;)And about the FISD sceneries... it should be noted in the File Library for which version (FS2002/FS2004) the scenery is. Some of the older ones work in FS2002 too. And then you can always ask about specific problems in the forum as mentioned in the readme files.Afcad file as noted twice before is most likely the reason, there is not much difference in other parts of scenery files between FS2002 and FS2004. TatuA member of FISD ;-)

The problem was caused by a scenery addon alright. After uninstalling MegaScenery's Pacific Northwest (which is technically suppose to be compatiable with FS2002) the amount the compass/VOR was off dropped from 180 degrees to "only" 50 degrees. Removing the MegaScenery for Southern California and reinstalling it without the upgrade patch, cured the problem completely. I'm wondering, too, if trying to run the MegaScenery stuff from an external hard drive may have contributed to the problem as well. To be on the safe side I reinstalled all the MegaScenery stuff back onto the internal hard drive I have FS2002/2004 installed on. In addition, I installed MegaScenery vol. 1, 2, & 3 on FS2002 only and vols. 4 & 5 on FS2004 only. FS2002 seems a lot happier with this arrangement!