Help! The 747 FSX doesn't track the ILS.

[Guest UlfB]

Hi,I've got a problem with the 747 FSX. It doesn't track the ILS beam correctly. I first thought is was caused by the navdata, that differs from the FSX airport data. But this seems not to be the case.Facts: Airport ESMS, runway 35. ILS freq 108.10, heading in FSX: 353.First two pictures from flying an autopilot approach with the default Cessna:http://forums.avsim.net/user_files/189429.jpghttp://forums.avsim.net/user_files/189430.jpgAs you can see, the Cessna is dead on the center line of the runway.This is two similar pictures with the 747. Navigation radio is set manually to 108.10/353.http://forums.avsim.net/user_files/189431.jpghttp://forums.avsim.net/user_files/189432.jpgNote that the 747 was in a stable configuration with flaps 10 and wheels down when intercepting the glidscope at 3000 feet.Also note that the aircraft isn't tracking the horisontal ILS beam correctly.What am I doing wrong? I flewn the PMDG 747 for years now and have never had any problems with the autoland before. Any help very much appreciated.Ulf B

[downscc 1,327]

I just gave it a try with the 747X at ESMS, and verified the approach with the eurocontrol charts. It does work very well for me.The only difference I note is that I didn't manually set the radio, I let the FMS do it. I had 25 flaps, but it looks like you've got more than 10 hanging out there in your pic....

[Guest UlfB]

Hi Dan,>The only difference I note is that I didn't >manually set the radio, I let the FMS do it.Normally I let the FMS set the freq and course, but now I set the course manually to 353, which is the same as the runway heading. As you can see the 747 is perfectly parallell to the rw, but offset.This is probably not a scenery error, since the Cessna lands spot on.This is probably not a pilot error, since he has made many, many ILS approaches on this same airport with the 744.I'll a reinstall after a complete uninstall of the 744. I'll make a test with the unpatched version first.Ulf B

[Guest UlfB]

Hi PMDG support,I made a complete uninstall of the 744 and then a complete install. Still the 774 won't land on center, as the default Cessna do.I've got no idea what to do now. Why won't the 744 track the ILS beam?Edited: My hard- and software specs:FSX Acc/SP2, Vista 32.Asus P5W DH Deluxe, X6800, 4GB RamBFG 8800GTXUlf B

[Mats_J 2]

Ulf,Have you checked the other thread about the skewed ND? There seems to be some kind of FS registry error that might cause stuff like this to happen. One of my regular test flights is ESSA-SID-NOSLI-UN851-RASMU-STAR-ESMS or back, and landing on ESMS I've never seen what you experience.Cheers,

[Tabs 2,790]

Yep,Use the Flight1 registry repair tool and see if that fixes it.

[Guest UlfB]

What does the Registry repair do? What Registry item might be wrong? I would like to check the Registry and confirm an error befor running that tool.Did the PMDG installer damage the Registry?Ulf B

[downscc 1,327]

The common error discussed here is something registers a pathfilename with a slash on the end where there shouldn't be one. Many have ran this utility without complaint.

[Guest UlfB]

Thanks Dan,If you could provide the registry key for that path I would be very happy. The Registry contains a lot of paths.Ulf BCore2Duo X6800 3.3GHz4GB RAM Corsair XMS2-8500C5BFG 8800GTX, Creative SB X-FiFSX Acc/SP2, Vista 32

[rsrandazzo 6,353]

Ulf-I just flew this approach to see what might be causing your problem.Here is an image of my approach:http://www.precisionmanuals.com/images/forum/747400/ESMS.jpgI allowed the ILS to autotune (because i'm a lazy airline pilot and thats what lazy airline pilots do...) and noted immediately that I see a final approach course of 351 degrees.I'm betting the /353 is causing you the headache.I found that the airplane tracked the centerline, landed approapriately and rolled out correctly.

[Guest UlfB]

Thanks for the info,But I'm totally lost on this one. Why does the default Cessna land dead on the center of the runway, while the PMDG 744 doesn't???I'll try another go around and will be using the default FMS settings.Ulf B

[Tabs 2,790]

Ulf,http://www.flight1software.com/files/FS_Registry_Repair.exeDownload this and run it - it makes sure all the FSX registry entries are correct. There's an issue that can happen with one of them that causes the plane to not load magnetic variation data for the ND and FMC. We've seen it cause issues like this one you're seeing before.No, the PMDG insaller doesn't cause the registry error, we're not sure what does, only a handful of customers have seen the issue.

[Guest UlfB]

Ryan,Thanks for the explanation. I did run the Registry Repair Utility and guess what? I did work :-)Dead on center of the runway:http://forums.avsim.net/user_files/189472.jpghttp://forums.avsim.net/user_files/189473.jpgStrange thing. If registry was damaged, why did the default Cessna land right on center? I wonder what the cause of this issue really is.Thanks everybody for helping me out :-)Ulf B

[downscc 1,327]

Hurray! Glad you found the problem.<>PMDG's modules are much more complex than the default airplane. Their implementation allows much more realism, such as being able to track either true or magnetic, etc. In order to do this, I assume they have many more external calls to information than the default aircraft and so they rely on such things as registry entries to be consistent. My guess is the default aircraft are simple extensions of the MSFS air and graphics engines, the gps.dll is mostly eye-candy. Such a difference between those and these high-quality add-ons. Anyway, that's my uninformed opinion and guess.Still, glad you got it sorted out.