I have that problem also. I've been ignoring it till now. My guages look exactly the same. Its really screwed up when attempting a CAT III landing.Chuck

>That was a 90nm stretch and the airplane couldnt track>a straight line with a 90kt crosswind. Do you see the correct crosswind vector reported on the MFD? That would at least point whether the problem is in wind calculation or in applying the needed heading correction. If you knew your TAS at any given moment and the wind you could go and calculate the required heading correction and see if the 744 is doing it right.Michael J.http://img142.imageshack.us/img142/9320/apollo17vf7.jpg

>>That was a 90nm stretch and the airplane couldnt track>>a straight line with a 90kt crosswind. >>Do you see the correct crosswind vector reported on the MFD?>That would at least point whether the problem is in wind>calculation or in applying the needed heading correction. If>you knew your TAS at any given moment and the wind you could>go and calculate the required heading correction and see if>the 744 is doing it right.>>Michael J.If you look at the picture i posted it doesnt seem to apply the correction in the right direction. Its crabbing to the right when the wind is coming from the left. But the airplane is drifting to the left. Anyone else agree with that? Hopefully someone from support can have a look.Kevin H

I have posted a another scenario with both pics of MFD/PFD and the FS Map. I flew the Mcoy9 from MCO and this was between VIYOP and SAV which is a 55nm stretch. The last pic i just added it was suppose to be following J55 from SAV-CHS, as you can see its homing to the point and not follwing the airway at all. Kevin H

I'm having the tracking problem also. I noticed it on my first flight with the 400X on a flight from KSFO to PANC. Here's the scenario:B747-400XFFlight plan entered manuallyWeather set to clear (no wind)The aircraft flew over every fix and then started to turn. After initiating the turn it continued to diverge from the course line (sometimes as far as 8.8 nautical miles) than it slowly began to converge and reached the course line at the next fix where the whole process started over again.It seems to me that the FMC commands the aircraft to fly-by a fix instead of fly-over a fix. After the fly-by the logic appears wrong in that it does not command the aircraft to intercept the course and/or airway.I haven't done the same flight in FS9 but will in the near future.Don B.

Hmmm... Are you guys who are having this problem running Windows in a non-US English locale?I seem to recall, in the past, math bugs related to locale (due to differences in decimal place character).- Bill

>Hmmm... >>Are you guys who are having this problem running Windows in a>non-US English locale?>>I seem to recall, in the past, math bugs related to locale>(due to differences in decimal place character).>>- Bill>No - US English without a doubt here.

>Hmmm... >>Are you guys who are having this problem running Windows in a>non-US English locale?>>I seem to recall, in the past, math bugs related to locale>(due to differences in decimal place character).>>- Bill>Nope, i dont think that is the problem. FS9 version works like a charm. Kevin

Interesting. I just flew KLAS to EGKK and was dead-on the magenta line the entire way including the TRALR RNAV SID and the oceanic segments from 4130N to 4120N etc, with ActiveSky X running. It'll be interesting to see if someone can diagnose a common denominator for those who are reporting this behaviour.

Hopefully support can have a look at this issue ASAP. Since im not the only one witht his problem now.Kevin H

Is this an issue on supports list of things to fix yet? Please help.Kevin H

My God! I thought I was the only one with this problem and was figuring out a way to tell you guys in a topic, but after a quick search I found this one which describes ...MY EXACT SAME PROBLEM!The big question is that it was working just perfect, and ITS IS working perfectly in the Fs9 but suddenly I got this problem to, which screws the use of LNAV mode for navegation.I

Well, I'm sad to hear that some of you are experiencing this problem, couple of days ago I tried a medium range trip between Paris and Dakar using a hand input routing found over at "Routefinder" but LNAV worked perfectly from the beginning, also at 8x acceleration I still got the plane following the magenta line like a Ferrari on a race track. The only problem I had was the great wind shifts due to the fact that I'm still using Active Sky X with FSUIPC unregistered.My set up is:VISTA Home edition 32bitFSX SP1Active Sky XFSUIPC unregisteredHope you can sort it out.Lorenzo

I am also having exactly the same problem. I use FSBuild and then FSX real weather. Don't get it with FS9 version.Rob

Gents : By looking at the picture above and reading your posts it appears that :YOUR MAGNETIC DEVIATION IS ZEROLoad up the default Cessna and go to a place associated with a high mag dev. Say JFK 31L. Your magnetic heading (you can also press Shift-Z to check) should read 315. If it does not you have a problem. Best,VangelisPS. Instead of guessing what the x-track error is, just check PROG page 2. Also flip the MAG/TRU heading switch from NORM (magnetic usually) to TRU. Does the compass rose rotate ?===================================== E. M. V. Precision Manuals Development Group www.precisionmanuals.com=====================================