boeingflir

Thanks. Bruce

Thanks. I haven't updated the AIRAC for awhile. Definitely out of date. What do you think about the GRND PROX issue? Is that connected? Bruce Jacobs

Sorry, forgot to sign. Bruce Jacobs

I have tried it flying a full route, my usual test flight is EDDF-EGLL and I also have tried it with a full route and diversion back to Frankfurt. Since you ask, it makes me think of an unusual occurrence when I divert back. I select an ILS, usually 25L. The freq. and course show up in the upper left coroner of the PDF as it should, but no GS or LOC pointer and it won't it won't arm when I select APP. I have never had this occur with any of my PMDG add ons including the 737NGX or Level D 767. I end up selecting the 25L GLS and use LNAV/VNAV. Thanks for your help. It's annoying. Not your help, the GRND PROX.

Yes, beside the climb performance issue I also get a terrain warning 600agl. Mike had suggested that if I deleted the ARPT_RWY.dat file that would fix the GRND PROX issue. I just tried it again after deleting the file, loaded a new flight since I thought there was a possibility that loading a saved flight might be an issue, and no joy. It still gives me a PULL UP TERRAIN warning.

OK, it worked. She's flying like the real thing. I deleted the ARPT_RWY.dat file, restarted and I still get the Terrain Pull Up warning at about 600 agl. The only way to silence it is Terrain Override, or a go around. Tried it at both EGLL and EDDF. Frustrating. Bruce

OK, it worked. She's flying like the real thing. I have deleted the ARPT_RNWY.dat file, but won't know if that worked until I fire it up tomorrow. I ran out of time before I could fly an approach and see if the GPWS warning went away. Bruce

OK, I'm back and my "expert" is coming over tomorrow to fix this. I'll let you know. It sounds easy. That said, to Mike 777, funny! I've tried to expose my weaknesses and still maintain some self respect. I am a Mac user in my "real" life and I consider anything beyond the desktop to be plunging into the bowels of the computer. I remember being walked through installing Kai Tak in the PMDG 747 and I couldn't believe it when I was instructed to actually delete 5 lines of text in a file and replace it with text he had provided. Thanks for all the help. I'll report a, hopefully, happy ending. Bruce

OOPS! Forgot to sign. Bruce Jacobs

Thanks again. Unfortunately I have to leave town before I can get the guy who knows what he's doing over. I'll give an update in a couple of weeks.

OK, I have not gone into FSUIPC yet. I thought that I'd make one last desperate attempt to solve it without digging in. I am not too conversant with the bowels of the PC as in my real life I'm a mac user, but I have an expert on hand. I have all my settings so getting my few a/c back up will not be too hard. I have 737NG, the 777 and a Level D 767 all set aircraft specific and I'm working with the 777 now. I know what I'm doing with FSUIPC in programing the a/c. Thanks again for all the help and I'll give a progress report. I don't have time to work on it right now.😎 I thank everyone for their input. Bruce Jacobs

No joy. I deleted all flap setting from FSUIPC and programed flaps through FSX options. worked fine mechanically, but still stalls at 0 flap man. speed. That's on all versions, all departures.

I'll check the flaps first. It is logical since it does seem to happen around 1 degree flap maneuvering speed which would be just the LEDs, but the brains of the system won't let it go above that speed if it thinks they're down. Even the old 757/767 did that. Hard to believe those are "old." Of course the 727 you could keep accelerating until you tore the LEDs and trailing edge flaps off the airframe. Those were the days.

Thanks to both of you. I'll get under the hood soon. I know the introduction makes the case for not using FSUIPC but rather programing everything through FSX. Is that true?

I am having a perplexing problem. During departure the aircraft just kinda dies performance wise around 3400'. This happens with no altitude restrictions and 12000' or 310 in the altitude window. I have the thrust reduction altitude at 1500' and acceleration altitude at 3000' for a close in noise abatement departure procedure. The climb is normal until acceleration altitude (I'm in Climb 1 at 1500'). At 3000' I go to flaps 5, after a 15 degree flap TO at 550 thousand lbs. and it just won't accelerate the way it should and rate of climb goes down to 500'/min. It will get to 0 flap maneuvering speed (about 230Kts) after an inordinate amount of time and distance. When I get to 0 flap man spd, bring the flaps up, it's in THR REF, Roll is LNAV and Pitch is VNAV SPD as it should be. Thrust is Climb 1 at about 89%. It does the same thing at Max Climb so that isn't the issue. It will not accelerate above about 230 Kts and won't climb. By accident I discovered that opening FSUIPC and them canceling it gets rid of the issue and the aircraft starts accelerating (thrust remains the same) to 250Kts and then starts climbing at 3000+/FPM. I have checked for conflicts between FSUIPC and FSX EXTENSIVELY. I have looked at it from the external view and the flaps are physically up and indicated up. No speed or altitude restrictions in the FMC. Everything else in this simulation works perfectly except, occasionally, on a coupled ILS to 9L at Heathrow I will get a continuous GPWS pull up terrain warning. The terrain is flat on final. Any thoughts, suggestions, or solutions? Any help is appreciated. Thanks you in advance. Bruce Jacobs