Hi, I'm getting this weird problem when flying in the USA (Seattle): my VORS indications are offset by about 20 degrees, while ADFs point correctly, as well as my heading bug and GPS direction. It means that if I'm flying on GPS on a heading of 180 (course 180 on FSNav to a specific VOR), the couse of this VOR is misaligned by about 20 degrees. And this happens only in the US. In Europe everything is OKCan someone give a clue why this is happening now and how to correct it without reinstalling everything?(I have recently reinstalled everything on WinXP and before on Win2000 I didn't have anything like this - even with the same sceneries. )Thanx a lot in advanceRino

Sounds odd. You may want to check for a setting of magnetic or true heading.

How can I do that? I've even uninstalled everything regarding reality xp settings (you have to check americas/europe), but the problem persists. I have doublechecked with default planes - the same.thnx for your replyrinoEdit: ADF points correctly(!)GPS navigation is correct (!)Just the VOR tuning is misaligned (?)

This is almost always caused by FS2002 sceneries used in FS2004 that are incompatible with FS2004. I have made several posts on this topic, search on "netboyz" to find them.You need to disable or remove FS2002 sceneries you have installed, do a binary search among them to find the one(s) that cause the symptom. I have a tool I wrote to identify the sequence in which you installed them, if you find that you need such a thing.Luck -- Dick Bixler

Thanx, I will look into itBTW, How can I do a binary search?rino

First, just look through the sceneries you've installed recently and see if they say in the readme that they are for FS2004/FS9. If they only mention FS2002, they're suspect, disable them and see if you can narrow it down quickly that way. Otherwise...If it's just a few sceneries disabled that makes the problem go away, just re-enable one at a time until you find the one(s) that cause the problem (linear search).If it's a lot of sceneries and you're brave, a binary search will save a lot of time but is more complicated:A Disable enough sceneries most recently installed, to make the problem go away in the area where you have seen it. This is your starting "Test Group".B Successively re-enable diminishing halves of the disabled Test Group, and determine (do a flight) each time you re-enable some to see whether the problem shows up.C If the problem shows when you have just re-enabled a set of sceneries in the Test Group, then the problem scenery is contained in the set you just re-enabled, so redefine the Test Group to be that set just re-enabled, and successively search diminishing halves within that re-defined Test Group until you narrown it down to one or more scenery causing the problem. (The first time you do this, record the set of sceneries NOT re-enabled in this step as "Alternate Test Group")D When you have re-enabled half a group of sceneries in the Test Group and the problem does not show when you test it with a flight, then the problem scenery is contained in the set of sceneries you did NOT re-enable. Leave enabled the set you just re-enabled, re-define the Test Group to be the set of sceneries you did NOT re-enable, and search diminishing halves within the re-defined Test Group of sceneries.Repeat steps B-C-D until you have narrowed down to a scenery that causes the problem, and keep that one disabled or discard it.After that if you still have a problem, then you probably have multiple problem sceneries. So repeat the steps B-C-D using the Alternate Test Group recorded in step C. Depending on how many you have, you may have to do this multiple times, with a new Alternate Test Group each time.Dick Bixler

HeHe,I think you won't hear from me very soon ... - not an easy taskMaybe some aircraft can be the culprit?For example, F1 C177 was originally designed for fs2002, then upgraded for 2004, but I don't remember having such a problem in previous installations, and my sceneries in the USA are now very few. georender, in other words, and FSFreeware roads and waters. Same sceneries as in previous installationsThanx

Best of luck then!

BTW -- Don't think the offending scenery has to be in the USA to cause a problem in the USA. I have had scenery in New Zealand cause problems in Alaska. db

We need a sticky list of sceneries, repaints, etc that cause corruption, crashes, etc. so we all can be on the lookout.

Hi all,I've found the file!Some italian scenery messed up with magdec.dll in scenery/base/scenery.Installed the original file and the problem has been fixed.Hope this helps someone else (I suggest making a backup of this file, just in case)