Anyone experiencing the skewed ND - read!

[tf51d 284]

I'm beginning to think we may have some how gotten a bad install file. I just tried installing it on my Vista boot disk with FSX SP2/Acceleration and got exactly the same results. This is without installing updated navdata, so the theory the updated navdata is causing it doesn't seem to bear out! The time stamp on my install file is 11/2/2007 7:24PM File size =108,682kb Packed size = 106,971kb. According to the Readme and my receipt the version number is 2.00.0031. Can anyone you does not see this issue verify this info, and those that do, if they have the same.

[Tabs 2,790]

Steve,By "debugging software" I mean watching our code run using the Microsoft Visual Studio tools we use to make our products. It's unfortunately not something we can give out, I was mistaken earlier and thought we had some sort of custom made thing that we could do that with.

[Guest Oz_Animal]

Hummm....You

[tf51d 284]

Ryan is there someway we can arrange to have a new download, on the chance somehow we got a bad download the first time? I think it may be worth a shot, since I tried to install on my Vista SP2/Acceleration system (same system dual boot, which I normally don't use) and got the same results. That seems to point to the install file as the culprit!

[Tabs 2,790]

Tom,What's the date on your installer file and the size in bytes shown when you right click it and hit properties?

[tf51d 284]

Thanks Ryan!Size 111,290,361 bytesSize on Disk 111,292,416 bytesCreated November 02, 2007, 8:24:48 PMMidified November 02, 2007, 8:24:48 PMThat's the PMDG747_400_FSX.exe file.

[Guest bibic711]

Will FS2004 with 737NG in XP SP2 fits in this situation too?If so I will go home and find out the above information.

[Jet Tech 31]

Tom,Can you drop me a note at support(at)precisionmanuals.com and I will try to arrange a fresh download.RegardsPaul Gollnick :-cool Technical Operations/Customer Operational SupportPrecision Manuals Development Groupwww.precisionmanuals.comhttp://www.precisionmanuals.com/priv/img/forum/sig_pmdg.jpg

[Guest Oz_Animal]

Hi Paul. My install program is the same as Toms but it

[jordanal 70]

Ryan,As I read these "skewed ND" posts and as some people figure out that their default FS aircraft exhibit identical behavior, is this not the same 'ol corrupted AFCAD issue identified back in the early to mid FS9 days? The step by step procedures for identifying and removing even a single AFCAD has been posted in this forum numerous times over the years so I don't understand the seamingly different troubleshooting path.Just curious is all...Regards,

[tf51d 284]

My default aircraft and my other addon aircraft doesn't have this issue, and I have provided Ryan examples of such.

[Guest Oz_Animal]

AlWasn't that regarding "Add-on" or non compliant AFCAD's? If so most of the trouble shooting I have done is on "Clean installs" No extras whatsoever.If you are talking about the standard AFCAD's then please tell me more?RegardsSteve

[jordanal 70]

Hi Tom,Yea, I see that you seem to have a different issue all together and I wish you the best in getting it quickly resolved. You and I both know PMDG will get you going, one way or another.My point or curosity was, that as I read through several of these the "skewed" threads over the past couple of months, it seems like most of the posts are of the corrupted AFCAD nature, mixed in with some unusual circumstances like you have.Just hope folks take the time to identify AFCAD issues before calling it a PMDG issue.Regards,

[jordanal 70]

Hi Steve, no I'm with 'ya now; I was referring to any AFCAD installed with an add-on scenery package or copied into place manually. I really do wish someone would bring ScanAFD up to FSX so we could easily identify all AFCAD type bgl files like we could in FS9.

[tf51d 284]

I've tried disabling all 3rd party scenery and all 3rd party afcads, and still see this issue. Do me a favor, and do my test above Set yourself up on JFK Runway 13R which has a Magnetic Heading of 135. Setup your ND to maximum zoom 10 miles, and display waypoint info. The intersection MEALS should be located at roughly the the same bearing as the Runway Magnetic 135 degrees at the beginning of the ILS for Runway 31L, but I'm seeing it at a bearing on what would be Runway 13R's true heading of 121 degrees. (Verified by Defaults afcad reported 14 degree deviation and also when switching the 744X to True heading.) Can you post a screenshot to show what you are seeing? Here's mine