OK. A I begin using this fine simulation I am running into some problems with the FMC. First of all it was originally loaded from a disc. The AIRAC cycle is 0904, old. The FMC OP PROGRAM is 549849-011. When I select an arrival, say the ILS34R at KSEA, when I go to the legs page it says in the scratch pad "disco inserted after KLEWS. The fixes are KLEWS 4000A then BUCKK 2200 then the runway. I cannot bring BUCKK up to close the disco. It won't let me. KLEWS is part of the approach not a transitional way point on a SID. The fact that I can't delete KLEWS (INVALID DELETE) proves that. Also, and stranger, on every airport that I've tried (KPDX, KDEN) the final fix, in this case BUCKK, is offset to the left of course (centerline) probably 1/4 mile or so. The intercept leg from KLEWS to BUCKK to the runway is 360. So the magenta line comes in as a dogleg from the left. It should be 342 and lined up with the runway centerline (duh). I guess that it still qualifies as a straight in approach (less than 30 degree offset). SOMETHING ISN'T RIGHT. Since we don't really initialize the IRUs in this simulation it's hard to tell what's going on. I believe that as soon as I put KSEA on the route page as the departure point the IRUs are initialized, unlike the 747 or Level D 767 where you actually have to turn on the IRUs, and initialize with a position and system countdown.One obvious possible solution is a new AIRAC cycle. All of my add ons are running on old AIRAC cycles and I didn't want to ante up if there is anther solution.THANKS IN ADVANCE FOR ANY HELP.Boeingflir

You've got enought posts to know that you should sign them in this forum.I am having a hard time following your problem statement(s), are there more than one? Have you tried the registry repair tool from Flight1? Also, make sure your sidstar files are the same cycle as the airac data.

I reread my post and realize that I did go on a bit. Basically, when I select an approach, in this case the ILS 34R at KSEA, it isn't lined up with the runway centerline. The magenta line should be lined up with the rwy center line, but it is off set about 20 degrees to the left. It is a line heading 360 degrees from KLEWS to the runway threshold instead of 342 degrees from KLEWS to the runway threshold on the runway centerline like every straight in ILS in the world is. I can't make sense of it. I am not using any STARS, just setting up to fly the pattern to the ILS. I am unfamiliar with the registry repair tool.Bruce Jacobs

Download FSX/FS9 Registry Repair Tool (36KB) from here:http://www.flight1.com/view.asp?page=libraryYou should (for FS9) also be using the current FS9 version of FSUIPC from here:http://www.schiratti.com/dowson.htmlCheck the registry first as FSUIPC installs now use the registry entry I believe to find FS9 and the modules folder it installs into.

Ron, Thanks for the info and suggestions. Tomorrow I will bring my setup into my expert and we'll take a look at it. It is definitely a PMDG problem since the same AIRAC cycle (0904) is in my LDS 767 in FS9 and is fine. All of my PMDG 737NGs (600-900) also have 0904 and are all 20 degrees off on the ILS course and it wasn't always thus. I am stalling on downloading a new AIRAC cycle because I have the KAI TAK IGS13 on my 747 and since I am lost in this PC world (Mac user) I didn't want to start from scratch getting that classic approach back into the data base. We'll work it out. I'll keep you posted on the outcome of the registry tool. It just seems odd for all of this to happen at once to just my PMDGs.Thanks.Bruce Jacobs

OK, I just did another test. I fired up my PMDG 747 at Fly Tampa Kai Tak, which as you probably know, isn't in the AIRAC database since it is a closed airport (X). I had to install the file myself with the careful, steady, step by step guidance of "vonmar" on this forum over a year ago. EVERYTHING LINES UP PERFECTLY. Afterwards I tried KPDX (Portland) again. 28L. HANNAH to ADDUM is 299 degrees. ADDUM to the runway is 299 degrees. It should be 280 degrees. So I would have to say that this is an AIRAC issue, but specific to my PMDG fleet not a database problem since it is consistently 20 degrees off at any airport that I try in the database.We'll get to the bottom of this sooner or later.Bruce Jacobs

The navdata cannot give you these symptoms. It's just a bunch of text files and the fixes in particular is just fix names and lat/lon info. That's all. Have you tried the registry repair tool?

There are certain functions of FSUIPC that the FS9 PMDG models use for navigation including magnetic deviation and the location of your aircraft. There was one very old FSUIC version that incorrectly broke down wind data to furnish crosswind and head/tail wind components to the PMDG FMC. That is why I suggested you update to FSUIPC 3.96 from the link I provided.Have you tried that?

Guys, I am treading water busily right now, but will follow your suggestions this weekend. I will come clean on one issue which supports your theory. I had a mother board give up the ghost a couple of months ago and at the same time replaced the processor. AFTER IT WAS BACK TOGETHER I HAD A LOT OF TROBLE GETTING KEYBOARD BUTTONS AND SWITCHES PROGRAMED. IT ALL POINTS TO FSUIPC AS THE CULPRIT.Thanks again.Bruce Jacobs

OK! I downloaded the Registry Tool from Flight 1 and that solved the magnetic course problem. Thanks for your help and patience. I got all my switches and buttons programed and just flew a fine, fully automated pattern to the ILS 34R and a dual channel autoland @ KSEA. Works fine, lasts a long time.Bruce Jacobs