Anyone experiencing the skewed ND - read!

[Guest Oz_Animal]

Hi RyanSorry Ryan I didn

[tf51d 284]

Steve, did you actually run the utility? My registry looked ok too, and I wasn't going to run it, but decided to give it a try, and it made the difference.

[Guest Oz_Animal]

Sorry Tom, of-course I did...lol...I would put it in the microwave if I thought it would help...lol Mate I am willing to try anything to fix this thing...It's become personal now :(I still think my issue (even though it looks 99% the same as yours) is a different problem.. I really don't know anymore, just about ran out of energy doing all this stuff.Thanks anyway Tom and great to here yours is ok..PS, can you post a picture of your complete registry entry

[tf51d 284]

>Sorry Tom, of-course I did...lol...I would put it in the>microwave if I thought it would help...lol Mate I am willing>to try anything to fix this thing...It's become personal now>:(>>I still think my issue (even though it looks 99% the same as>yours) is a different problem.. I really don't know anymore,>just about ran out of energy doing all this stuff.>>Thanks anyway Tom and great to here yours is ok..>>PS, can you post a picture of your complete registry entry

[tf51d 284]

I had a hypothesis on why even though registry path looked ok before it didn't work til after running the registry fix. So I checked it, and sure enough there was a at the end of the path. So I now believe his backslash wasn't there before, so to test this, I edited the registry path and took it out, and again the problem returned, which I think confirms my theory. I put it back and all is well again. So check your registry path again, make sure it's pointing to the right drive and that there is a backslash at the end of it, and the rest of it is formatted correctly.

[Tabs 2,790]

Guys,I just reproduced the problem using Tom's method of deleting the trailing backslash. This is the first time anyone from PMDG's been able to see this in action - we're talking it over and trying to figure out exactly what's going on.Steve,Can you try the following:Start/Run - type regedit and press enter.Navigate to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft GamesFlight Simulator10.0At the bottom inside this registry key you should see an entry "SetupPath"1. What is the value of that entry?2. Is there a trailing backslash after it?3. If not, add one (ensure it's a backslash, not a forward slash - it's the key above Enter)4. Post a screenshot of that registry key if you can - we don't have any security data in that key, it's fine if you post it.We're really close to nipping this guys, I know it.

[jordanal 70]

Dang Tom! Looks like you're on a roll this week my friend...

[tf51d 284]

4. Post a screenshot of that registry key if you can - we don't have any security data in that key, it's fine if you post it.Ryan, PMDG don't have security data in that key, but this is Aces entry isn't it? Do you know that they don't?

[Tabs 2,790]

>4. Post a screenshot of that registry key if you can - we>don't have any security data in that key, it's fine if you>post it.>>Ryan, PMDG don't have security data in that key, but this is>Aces entry isn't it? Do you know that they don't?There's a product ID that is generated by the CD Key when you install, you can't go backwards from that to installing the sim. ACES wouldn't just put information right there in plain view that would allow piracy... Blank the number out with Paint or something if you really want.

[Guest Oz_Animal]

Hi RyanJust for the testing purposes I deleted the program and made sure the keys were also deleted and started again.The first key is of current usersThe second is the local keyThe third is of the data in current users. It has 3 dots after the slash but in the data field it hasn't. I deleted them and tried again no change.http://forums.avsim.net/user_files/188272.jpghttp://forums.avsim.net/user_files/188274.jpghttp://forums.avsim.net/user_files/188275.jpgI also did a repair on the install just to see what happens but no change.I even ran the FS9 reg fix and it put that entry in there but that made no difference.PS, did you get the e-mail with my latest tests without the Mag file? Different...PSS. I am currently uninstalling and reinstalling everything again as with all the changes and tests I thought this would be best. Ready for round 2986775 lolRegardsSteve

[Tabs 2,790]

Edit: see below post...

[tf51d 284]

When you say Local Key, I assume you mean HKey_Local_Machine right? Also it looks like you are missing a few entries in there. The CDpath, LangID, and PID. Don't know what efeect it would have though, and this will seem like a real stupid question, but FSX is on your C: drive right?

[Tabs 2,790]

To the best of my knowledge this is what the registry entries should look like on a correct FSX install (I have Acceleration installed as well) Mine matches the other PMDG devs' who I had look earlier.HKEY_LOCAL_MACHINE/Software/Microsoft/microsoft games/flight simulator/10.0: (yes those are all lower case for the last two)http://www.progressivetranscriptions.com/744/hklm.jpgHKEY_CURRENT_USER/Software/Microsoft/Microsoft Games/Flight Simulator/10.0http://www.progressivetranscriptions.com/744/hkcu.jpgSteve,If you've installed FSX, run it, patched it to either Acceleration or SP2, and then run it again, and you still see what you posted in those images, then something is going very wrong in the process of setting up FSX and/or Windows. You're missing 6 and possibly 7 of the entries that should be there between the two FSX registry keys.Do you by chance have a plain retail XP Home or Pro and not XP MCE? I don't see how that could be causing it though. (MCE is a modified XP Pro with the Media Center app and a different theme)Regarding the other theories you have - we know what's causing this as far as the mechanism - our PMDGOptions.dll file cannot find the magdec.bgl file because the registry keys it uses to locate the proper folder are missing or modified. I really don't think file corruption or any of that is at play here, I was able to exactly reproduce this skewed ND situation earlier today by modifying that registry entry.Sending us a bunch of files isn't going to do anything in our best judgment.

[Tabs 2,790]

Ok listen up folks:I need EVERYONE who is experiencing these ND/magenta skewing issues from the other thread to provide me with the following information, emailed to rmaziarz@precisionmanuals.com1. Where do you live in the world and are your versions of Windows and FSX region specific? (ie, not the US version) If so, which regional versions are they exactly?2. Is your FS install in the default location or did you put it in a different folder?3. Take the default Cessna 172 and load yourself onto KJFK Runway 31R. Press Shift Z, what is the magnetic heading shown?Go to KSEA runway 34L and write down the magnetic heading shown as well.4. Now repeat the above using the PMDG 747 - take screenshots if you see a discrepancy. Try creating a route as well and take screens of what you see if it looks skewed, keep the Shift-Z heading info visible.5. Please attach your FSXSceneryBASEScenerymagdec.bgl file to the email.Thanks, hopefully we can figure out what's going on here.

[Guest Oz_Animal]

RyanAfter completing yet another install of everything I have now got these registry entries, (See below)HKEY_LOCAL_MACHINE/Software/Microsoft/microsoft games/flight simulator/10.0http://forums.avsim.net/user_files/188278.jpgHKEY_CURRENT_USER/Software/Microsoft/Microsoft Games/Flight Simulator/10.0http://forums.avsim.net/user_files/188279.jpgIt would appear that they are correct as you have extra ones in your set-up for Acceleration or something else? Please explain what ones are missing; what they do and can I manually input them? I am running SP1 & 2 only? Could you please confirm if these are now correct or if anything else can be or needs to be manually added etc?Also as stated earlier I am defiantly running XP MCE and can send you any details re the version etc, just let me know. See pichttp://forums.avsim.net/user_files/188277.jpgDuring the crash course you have given me about the operation of the model I understand what you are saying but one thing still confuses me. With the mag file removed the system works correctly (except for the runway position drawing) on all true headings and tracking, ILS etc is fine (see my e-mail to you and Paul)With the file reinstalled it refers back to the magnetic headings and is out of position. The only thing being right is the runway.Therefore just logically speaking the PMDGOptions file IS seeing the magdec file and is just not interpreting it correctly, or, it's a different issue.Hey remember I'm just guessing here and just providing alternative thoughts to help. I am just a bit confused how it can still be as you suggested.As far as sending the files is concerned I am actually more interested in getting hold of yours...as they work...you can understand why. :)EDIT... She is still doing the same things. RegardsSteve