jakef

It seems to appear with any livery.

It does appear that the windows have been fixed, except the windows on the L3, R3 doors (777-200LR only) are still not transparent, not a show stopper though...

Both American and Delta do have the HGS on their 737NGs.

Thanks Kyle, that's good enough for me.

You cant really see it if the sun is shining directly on it, but it is there. Not a huge deal but it defiantly wasn't there prior to the update. I'm just trying to figure out whether it was done on purpose, or is a bug. The fact that you can see it from the VC, and not outside is what makes me think it might be a bug, but not sure.

Can anyone confirm that the inner portion of the winglets is showing the night lighting splash during the daytime when looking back at them from the VC. It doesn't show from outside in spot plane view, but when in the VC they appear to be lit up as they are in darkness. This is with the newest version (build 1.10.6436). It seems to be present on all the winglet models, -700, -800, and -900.

Kyle, It was a clean install per the pinned thread. I have since, uninstalled and reinstalled, again per the pinned thread, but the error remains for me in FSX. as Ryan said it looks like you guys are working on it , and I'm sure you'll figure it out.

Kyle, The panel states issue seems to be present in FSX as well. I did a clean install with the update with a default FSX setup and used the PMDG short panel state as a starting point. The fuel, and anti ice is on all the time. I'll submit a ticket.

Amen to that!!!

Actually the warning reads "Stabilizer Configuration" on the EICAS display. And I have not yet been able to reproduce it, so far it has just happened that one time...weird! The trim was set properly in the green band.

I had this problem yesterday, and the trim was set properly.

I have seen this as well, and it happens with or without weather. I can fly in FSX with the weather cleared, and fuel prediction still drops. I believe they are looking into this.

What a terrible loss, his work was outstanding and he will be missed by the community, deepest sympathies.

Interesting because on my machine (XP 32bit) the latest update has made the ops center fully functional. This seems to have become a real head scratcher...on all three OS's (XP, Windows7, and Windows8) we have a mixed bag of working, partially working, hummmm....weird!

Hi Ryan, I run XP and the update to Version 1.5 has fixed everything for me as far as I can tell.

I have also seen this issue...

Interesting, I have yet to find a 777 flightdeck picture on the net with the inop. stickers...granted I haven't looked at every single one.

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.