I don't understand why this plane will not climb and is nose heavy. I just tried a flight with these specs.

 

PMDG 737-700WL

GW - 139.8

ZFW - 117.8

126 pax at 21, 275 lbs.

Cargo - Front 5,736 lbs, Rear 7,053 lbs for a total of 12,789 lbs.

Fuel - 22,000 lbs

92.9% Full load.

 

Takeoff seems normal as I am rotating where I should but the climb out performance is horrible. N1 was 91.2% only climbing at 800 fpm at 186 kias. If I raised the nose at all my speed would drop quick. The flight director was actually in the brown below the horizon.

 

Any help would be great.

 

Thanks

 

Angelo

I'm going to guess that you mapped and/or calibrated your flaps axis through FSUIPC?

 

 

Sent from my iPhone...typing errors imminent

Use any weather software?

Yes I calibrated my flaps through FSUIPC. I use REX.

 

I used to fly the PMDG often when it first came out but haven't flown it in over a year. I just installed it but didn't notice any performance issues before. I use FS2Crew and just the other day bought Topcat.

 

 

Angelo Corredino

Mext time you perform a flight, check your temperatures as you climb, if your temperatures remain constant or even rise while climbing, then it is a weather generator related issue. Climb performance is degraded during high temps

Yes I calibrated my flaps through FSUIPC.

 

That's your problem. I did the same thing a while back and had the same issues, including the plane flying level with the nose below the horizon.

 

FSUIPC is coded to predetermine where each flap tick is on the flaps axis.

Whether the aircraft has 5 or 15 flap positions FSUIPC spaces them out evenly over the range of the axis.

 

He NGX was coded differently, and the result was even if flaps show zero in the cockpit or any 3rd party logging software, the flaps are still partially deployed in a weird state that drastically changes the flight envelope of the aircraft.

 

I also had the same problem with the JS41 and I suspect it's the same with the MD-11.

 

Disable the calibration of the flaps through FSUIPC and also the mapping, remap the flaps through fsx directly and retest the plane on a test flight.

 

I'm 100% sure you will see things return back to normal.

 

 

Sent from my iPhone...typing errors imminent

That's your problem. I did the same thing a while back and had the same issues, including the plane flying level with the nose below the horizon.

 

FSUIPC is coded to predetermine where each flap tick is on the flaps axis.

Whether the aircraft has 5 or 15 flap positions FSUIPC spaces them out evenly over the range of the axis.

 

He NGX was coded differently, and the result was even if flaps show zero in the cockpit or any 3rd party logging software, the flaps are still partially deployed in a weird state that drastically changes the flight envelope of the aircraft.

 

I also had the same problem with the JS41 and I suspect it's the same with the MD-11.

 

Disable the calibration of the flaps through FSUIPC and also the mapping, remap the flaps through fsx directly and retest the plane on a test flight.

 

I'm 100% sure you will see things return back to normal.

 

 

Sent from my iPhone...typing errors imminent

 

I'm not so sure about this--especially the assignment part. That would indeed be bad news for people who use more than just the NGX and rely on FSUIPC to provide different throttle quadrant mappings for different airplanes. I have had problems with A/T kicking off due to using FSUIPC calibration of the throttle levers, but never with simply the mapping through FSUIPC. That is good, because if I couldn't map those particular levers through FSUIPC, use of the NGX would be a pain in the neck, as it would require too much work to use other aircraft such as twins because of the different throttle quadrant arrangement. I certainly wouldn't want to have to go into the FSX keyboard mappings and change the arrangement every time I switch from a single or twin with the first one or two levers being throttles followed by prop and mixtured versus a jet where the first lever is always spoilers followed by the throttles, followed by flaps. Maybe I'm alone in feeling that way, don't know.

 

Unlike the throttle, my Flaps, actually do use FSUIPC calibration insofar as they have a max and min defined on the Flaps Calibration page (-16384, and 16384). Just not curves. Doing this causes no problems whatsoever.

 

It is impossible to rule out if the OP is uniquely affected by what you say, but I just wanted to weigh in that at least one person (me) and probably many more, are using FSUIPC in the way I described above, and suffer no ill consequences of the nature the OP describes. I do things exactly the same on the J-41 and MD-11 as well, and all work flawlessly.

Well I deleted the FSUIPC.ini then mapped my flaps back to the FSX controls. Restarted FSX and all is working now. Thanks AJ.

 

I'm not so sure about this--especially the assignment part. That would indeed be bad news for people who use more than just the NGX and rely on FSUIPC to provide different throttle quadrant mappings for different airplanes. I have had problems with A/T kicking off due to using FSUIPC calibration of the throttle levers, but never with simply the mapping through FSUIPC. That is good, because if I couldn't map those particular levers through FSUIPC, use of the NGX would be a pain in the neck, as it would require too much work to use other aircraft such as twins because of the different throttle quadrant arrangement. I certainly wouldn't want to have to go into the FSX keyboard mappings and change the arrangement every time I switch from a single or twin with the first one or two levers being throttles followed by prop and mixtured versus a jet where the first lever is always spoilers followed by the throttles, followed by flaps. Maybe I'm alone in feeling that way, don't know.

 

Unlike the throttle, my Flaps, actually do use FSUIPC calibration insofar as they have a max and min defined on the Flaps Calibration page (-16384, and 16384). Just not curves. Doing this causes no problems whatsoever.

 

It is impossible to rule out if the OP is uniquely affected by what you say, but I just wanted to weigh in that at least one person (me) and probably many more, are using FSUIPC in the way I described above, and suffer no ill consequences of the nature the OP describes. I do things exactly the same on the J-41 and MD-11 as well, and all work flawlessly.

 

Don't know what I tell you then.

After I took flaps calibration off of FSUIPC my problems were fixed, and now the OP has reported the same.

 

@OP: np!

 

 

Sent from my iPhone...typing errors imminent

Good to hear that the OP resolved his problem. I obviously agree that FSUIPC was the problem, but I think that there are some subtle things that can happen within the Fsuipc.ini file that don't necessarily show up on the fsuipc gui. I've had bad calibration curves remain behind, non-existant controllers, you name it! All I can say is that when I read in the manual that fsuipc was not recommended for the NGX, I had some serious concerns because I simply DEPEND on fsuipc to map my multiple saitek throttles (too many!!!), CH throttles and recently Warthog throttle quadrants to assign all the various airplanes to their unique lever arrangements. Luckily I found that except for the particular issue of A/T and throttle calibration, that concerns about problems with just mapping the axis was unfounded.

 

FWIW, my Spoilers and Flaps are mapped through FSUIPC as a "normal axis", both with calibration page settings defining max/min and with the Reverse Axis checkbox checked (did he forget to put a check in the Reverse Axis box and got full flaps instead of zero flaps?). My throttles are also mapped through FSUIPC as a normal axis, but with the calibration page showing Unprocessed for the reasons previously mentioned.

 

(As an aside, now recently with the purchase of another brand new (yet another, sigh) Saitek throttle quadrant which seems to have less noisiness than the old ones, I can also take full advantage of "Override in Thrust Hold mode Only" without fear of it screwing up my takeoffs, but that is barely relavent to this thread! It sounds pretty pathetic, but since I can't use FSUIPC calibration with the 2 throttle axes on the NGX, I simply had to find a throttle unit that didn't need it!!! Pathetic, I know...)

AJ, tks for the advice.

i have the same problem in climb mode, delete all fsuipc and all work perfect right now.

Tka mate.

Fher.

Regards from Costa Rica.