jakef

That is correct, as far as I know there is no ETOPS decal in Alaska's cockpits.

Alaska uses SFP for the Hawaii routes more than anything, they wouldnt be able to fly in or out of LIH or OGG without it. It also comes into use on the BLI-HNL route. Im sure there are others her who can give more insight, but that was the first couple of things that came to mind.

All but seven of them.

There appears to have been a slight mix up with the .ini files, I have a PM in to Ryan, and hopefully we'll get it fixed soon. In the mean time anybody who would like the .ini file for N307AS that has the proper configuration PM me and I would be happy to share.

The .ini file for 307 is indeed wrong...not sure how that happened, but ill talk to Ryan.

Ok I'm going to take a stab at this. I think the real problem in this case is with the navdata. This is one of those rare occasions where real world data actually messes the NGX up. Lets take KSEA as an example. The wpnavapt text file in the navdata folder says:SEATTLE-TACOMA INTL KSEA16C09426163 47.463808-122.310986111.7016300430SEATTLE-TACOMA INTL KSEA16L11901163 47.463795-122.307750110.3016300433SEATTLE-TACOMA INTL KSEA16R08500163 47.463836-122.317858110.7516300415SEATTLE-TACOMA INTL KSEA34C09426343 47.437970-122.311211111.7034300363SEATTLE-TACOMA INTL KSEA34L08500343 47.440533-122.318058110.7534300356SEATTLE-TACOMA INTL KSEA34R11901343 47.431172-122.308039110.3034300347It should read:SEATTLE-TACOMA INTL KSEA16C09426163 47.463808-122.310986111.7016300433SEATTLE-TACOMA INTL KSEA16L11901163 47.463795-122.307750110.3016300433SEATTLE-TACOMA INTL KSEA16R08500163 47.463836-122.317858110.7516300433SEATTLE-TACOMA INTL KSEA34C09426343 47.437970-122.311211111.7034300433SEATTLE-TACOMA INTL KSEA34L08500343 47.440533-122.318058110.7534300433SEATTLE-TACOMA INTL KSEA34R11901343 47.431172-122.308039110.3034300433The red numbers at the end of each string are the threshold elevation in feet for that runway. The default airports in FSX do not have slopped runways, all runway thresholds will have the same elevation as the airport elevation. Without accurate numbers (accurate for FSX) the FMC will not calculate a proper E/D.

Actually, Ive just recently used the low visibility takeoff mode, and it is fully functional.

I've noticed this as well. In my case it does it with or without weather, I don't think its weather related. And it only happens when the autopilot is engaged.

The 737NGX will drift off course (slowly) on longer waypoint legs, it has been reported to PMDG and they are working on it for service pack 1.

I'm thinking it is as well.

In both cases the distance between waypoints was greater than 400nm (I dont remember the exact distance). This seems to only happen when there are large distances between waypoints. I think I had just past ARRIE on the BANGR departue out of KSEA an went direct LAIREon my way to PANC which if I remember correctly was 700 and something nm. Being cleared direct LAIRE often happens to flights out of KSEA going to PANC.

I will also confirm that this has happened to me twice, once eroute KSEA-PHNL, and KSEA-PANC, both flights were done in clear weather (so no wind), and the plane flew off course slowly (I was in LNAV) to the point where LNAV dissengaged.

Thank you very much Sean, I will give it a shot. In step one did you mean load the texture you want to resize into GIMP or is it into DXTbmp? Jacob Fuqua

Would someone be kind enough to explain this texture resizing process step by step...what programs I need to download (I already have Dxtbmp)...and how to manually extract the texture and alpha...stuff like that. If it is to much trouble, then I will just wait for PMDG. Any help would be greatly appreciated. Jacob Fuqua

Thanks mike, I'll give it a shot. Jacob Fuqua

After todays hotfix my CFG files are 800/900 non winglet are build 2916, and the 800/900 winglet are build 2888, I did not install the first hotfix. The 900 winglet model was the only one for me with the dome light problem wich I fixed myself. Jacob Fuqua

My system: Microsoft Windows XP 32 bit Home Edition, Service Pack 3Intel Core 2 Duo CPU E8600 @ 3.33GHz, 4.00GB RAM, Physical Address Extension (So it recognizes 3.00GB of RAM), GeForce GTX 260 896MB memory, Acer 24 Inch monitor at 1920x1200 resolution FS9, and FSX both installed on C disc. I get 25 to 45 FPS in the VC and 50 to 80 exterior depending where im at, no autogen, no water effects, no land or sea traffic, and no wildlife with clear weather. This is without Vsync if i turn Vsync on im limeted to my monitors refresh rate of 60 FPS exterior, so with Vsync i get 45 to 60 exterior and 25 to 35 in VC, however when im not testing settings I use the external FPS limiter, set at 30 FPS and it runs at 30 fine, unless i go to FPS hole area like seattle, where I get about 25 VC, and 30 exterior. I dont mind turning off all the eye candy in FSX becuase the only reason I got it was to fly the NGX! So you really dont need a super computer to run it. Jacob Fuqua

Just purchased the boxed version, and wondered if I need to install any of the updates on the PMDG website? Or should it already be the latest version?