Climb Performance Problems

[jordanal 70]

We all (including Ryan) need to clear the air up a bit about "calibrating in FSUIPC." What really matters here is how you have your Axis assigned in FSUIPC, not the calibration itself in FSUIPC. You should have every axis used with any PMDG product set to "Send to FS as Normal AXIS", NOT "send direct to FSUIPC calibraion. That is a big no-no for any advanced aicraft addon used in FS, especially PMDG products. When viewed with a text editor, each axis associated with a PMDG aicraft should be of type 'F' in the FSUIPC.ini file (not 'D'). Also, you still need to calibrate each device/axis in the Control Panel Game devices options and make sure to set full resolution there first. Second, do not assign a AXIS in FS or FSUIPC to the spoilers lever. In the case of the NGX, set various key commands in the PMDG Keys options page to operate the 5 positions of the spoilers (down, arm, 50%, FLT, and UP). Then in FSUIPC, assign 'Ranges' on a given axis lever and have it output those key commands when entering and exiting a range. In my case, Saitek Yoke lever Z - all the way foward issues a / (slash) key, which is set to 'Spoilers Down' in the PMDG Key settings. Lever all the way back, issues a Ctrl-Shft-/ key sequence with is set as "Spoilers Up" in the PMDG Options. You can also do the same thing for gear up/off/down - use the PMDG keys options and then set a FSUIPC axis with 'Ranges' to ouput key commands; or assign them to real controller buttons. Refering to the FSUIPC4 Users Guide, your Axis types should be set simlar to those found at the top of page 45, "Send to FS as Normal Axis." Finally, for instructions for setting up axis ranges to produce key sequences; refering to the same guide, see the bottom half of page 46 and the entire list of key sequences found in the "FSUIPC4 for Advanced Users" guide.

[B777ER 2,487]

I have axis going through fsuipc, calibrated in fsuipc as well for my gear lever and spoiler handle and both work flawlessly. This is with PFC hardware.

[JRBarrett 3,086]

Second, do not assign a AXIS in FS or FSUIPC to the spoilers lever.…

I have the CH yoke, pedals and throttle quadrant. I have used FSUIPC in the past for calibration and axis assignment, but at the moment I am running the NGX with FSUIPC.DLL completely removed from the modules folder, with all axis assignments going direct to FSX as per the installation guide.Since I use the first two levers of the TQ for the engine throttles, I assigned the single throttle on the yoke as the spoiler axis within FSX, with the "reverse" button enabled to change the directional sense.It works absolutely perfect in-game. The spoiler lever in the NGX tracks the movement of the yoke lever as smooth as silk. If I pull it back a short distance, it clicks into the "armed" detent... pull it back farther and it sets the spoilers to any position from barely deployed to fully up. It makes precise spoiler control very easy.

[Guest Turboblower]

I have the CH yoke, pedals and throttle quadrant. I have used FSUIPC in the past for calibration and axis assignment, but at the moment I am running the NGX with FSUIPC.DLL completely removed from the modules folder, with all axis assignments going direct to FSX as per the installation guide. Since I use the first two levers of the TQ for the engine throttles, I assigned the single throttle on the yoke as the spoiler axis within FSX, with the "reverse" button enabled to change the directional sense. It works absolutely perfect in-game. The spoiler lever in the NGX tracks the movement of the yoke lever as smooth as silk. If I pull it back a short distance, it clicks into the "armed" detent... pull it back farther and it sets the spoilers to any position from barely deployed to fully up. It makes precise spoiler control very easy.

Thanks for the tip Jim, have the same set up as you, sounds good.

[Heron 0]

What is most irritating is the fact that until yesterday night I didn't have this glitch of performance climb, before and after NGX (no hot fix) was installed. Now something comes from the weather and we cannot fly over FL270. I didn't even changed my FSUIPC version nor ASE. Actually, for ages I'm not having ANY weather issues. Repeating what I posted last night, I made 6 perfect flights with NGX using FL350, 360, 370 and 380 at the same US NW region. Also, I cannot believe my FSUIPC weather settings are conspiring against the FS since yesterday, providing I don't touch it since I cannot remember when... Regards

[ual1819 1]

Ok, I think I figured this out. It seems to be some bad juju with FSUIPC and throttle override "In hold/arm mode only", but nothing to do with calibration, since I'm not calibrating throttles in FSUIPC. Throttle axes for my Saitek Pro Flight Throttle Panel are assigned in FSUPIC. The assignment is "Send to FS as normal axis" as "Axis Throttle1 Set" and "Axis Throttle2 Set". Note: no calibration here, just straight assignment. My last flight that was set up this way went just fine. However, on this flight I changed the "A/T Manual Override" setting from "Never" to "In hold/arm mode only". As I originally reported, in LNAV/VNAV above acceleration height, thrust gets sluggish. By 3000 feet AGL I am stuck at 97% N1 but only moving 160 knots IAS, and not accelerating, with a 5 degrees nose down attitude. Gear is up, but flaps can't be retracted yet because of the low speed. I open up FSUIPC and un-assign the throttle axes, close the FSUIPC window. Boom ... everything instantly works as it should: the aircraft rapidly accelerates, nose up 10 degrees or so, accelerates through flap retraction speeds, and proceeds on CLB as normal. So ... now what?

[ual1819 1]

After doing this, I reassigned the throttle axes again in FSUIPC. Things proceeded fine until around FL250 or so, then climb performance became pretty anemic, fluctuating between +0 and +400 fpm. In this case, changing A/T Manual Override to "Never" immediately made the plane happy and it started climbing at 1000+ FPM. So I'm suspecting the thrust problems/conflicts with FSUIPC (at least in my case) are primarily caused by having A/T Manual Override set to "In hold/arm mode only". I haven't seen any of these problems when it's set to "Never". Unfortunately in the "Never" mode I can't really use A/T with a coupled ILS approach all the way to touchdown, which is supported by the NGX and is Boeing recommended procedure for the best speed protection from gusts/wind shear. So I'll summarize what I've found. The symptoms in the NGX are: - Lack of acceleration above acceleration height: N1% indicates normal, but IAS is stuck around V2, VNAV commands 5 degrees nose down pitch, but still no acceleration.- Anemic climb performance: N1% indicating normal, but struggling to maintain CLB speed, vertical speed bouncing between 0 and +400 FPM- Problems slowing down on approach: flaps full, thrust idle, on glideslope, but unable to decelerate down to VREF. In all these cases I've confirmed that weather is normal ISA, reasonable winds, typical fuel & passenger load, proper cost index, etc. This all seems to happen when FSUIPC assigns the throttle axes, and A/T Manual Override is set to "In hold/arm mode only". (It may even happen without FSUIPC: a friend of mine reported at least one of these problems with throttle axes assigned in FSX.) Turning off the FSUIPC assignments and/or changing the A/T Manual Override to "Never" will immediately clear up the misbehavior.

[hornplayer 1]

After reading all the post, and some experimenting with the following procedure, I think I have solved my problem...I will attempt to be concise.. Using the latest updated version of Fsupic....No add on...registered program....I have REX weather, but haven't tested it yet... MD-11...No climb passed FL200 and the aircraft acts very erratic. flopping left and right...737-800-900ngx....basically slow climb...The ground temperature was +15 degrees C Now, the problem...as I was climbing I noticed the temp kept climbing until at around Fl200 each would reach +45 degree C....I talked to a "real" pilot friend and he stated simply that as you got higher the temps get lower...Well, that makes sense. Now, what I did was open FSUPIC at the top of the screen and Pressed the button "clear all weather." I noticed instantly the temp dropped from +45 degrees C to about minus something I believe around -5 degrees C and the engine started responding and was able to climb to the set altitude.... I am not a computer expert, just a novice, but could this be the answer to my problem...At least so far it as worked for me..This happen on vatsim with FSINN running with the weather turned off and also off Vatsim not running FSINN, of course.So I am hoping someone with expert advise would straighten me out on this subject...If this is causing the problem, should I turn off FSUPIC or I suppose you have to have this running to run copilot and so forth...Little confused about the subject...Thanks in advance for any help...

[nrcrate 40]

This is simply a FSINN problem. If you load FSINN and connect to VATSIM or another network, it will overrule whatever weather you have loaded in already. If you disconnect from VATSIM, the weather will stick in FS until you clear all the weather with FSUIPC and command a refresh of your weather program. This has nothing whatsoever to do with PMDG. FSINN has a problem where it thinks the higher you go, the hotter it should be. Therefore making it impossible to climb past FL210. We must remember, FSINN is an abandoned project, and is a beta program. Not everything works as it should. The solution is to disable FSINN weather completely.

[hornplayer 1]

This is my FSUIPC4.log related to my post above....Is there anything wrong with this picture? My problem, I believe is/was related to temperature settings... ********* FSUIPC4, Version 4.719a by Pete Dowson *********Reading options from "C:\fsx\Modules\FSUIPC4.ini"Trying to connect to SimConnect Acc/SP2 Oct07 ...User Name="Robert Adams"User Addr="removed email address"FSUIPC4 Key is providedWIDEFS7 not user registered, or expiredRunning inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)Module base=61000000Wind smoothing fix is fully installedDebugStatus=15 93 System time = 17/08/2011 20:37:51 93 FLT path = "C:\Users\Robert\Documents\Flight Simulator X Files\" 93 FS path = "C:\fsx\" 561 LogOptions=00000000 00000001 561 SimConnect_Open succeeded: waiting to check version okay 2465 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 2465 Initialising SimConnect data requests now 2465 FSUIPC Menu entry added 2480 C:\Users\Robert\Documents\Flight Simulator X Files\Cold & Dark 737-900WL PMDG.FLT 2480 C:\fsx\SimObjects\Airplanes\PMDG 737-900NGX WL\B737-900WL.AIR 49374 System time = 17/08/2011 20:38:40, Simulator time = 20:37:53 (00:37Z) 49468 Aircraft="Boeing 737-900NGX PMDG House Winglets" 51402 Starting everything now ... 52557 Advanced Weather Interface Enabled 244906 Sim stopped: average frame rate for last 195 secs = 29.3 fps 2519385 Sim stopped: average frame rate for last 2230 secs = 25.3 fps 2521538 ClearWeather Button Pressed 2521538 Weather cleared by user action 2521538 External weather discarded 2523472 Weather Mode now = Theme 2523472 Weather Mode now = Custom 9966342 Sim stopped: average frame rate for last 7443 secs = 28.1 fps10330636 Sim stopped: average frame rate for last 59 secs = 29.0 fps10387420 System time = 17/08/2011 23:30:58, Simulator time = 15:21:26 (20:21Z)10387420 *** FSUIPC log file being closedAverage frame rate for running time of 9952 secs = 27.5 fpsMemory managed: 4411 Allocs, 4411 Freed********* FSUIPC Log file closed ***********

[hornplayer 1]

This is simply a FSINN problem. If you load FSINN and connect to VATSIM or another network, it will overrule whatever weather you have loaded in already. If you disconnect from VATSIM, the weather will stick in FS until you clear all the weather with FSUIPC and command a refresh of your weather program. This has nothing whatsoever to do with PMDG. FSINN has a problem where it thinks the higher you go, the hotter it should be. Therefore making it impossible to climb past FL210. We must remember, FSINN is an abandoned project, and is a beta program. Not everything works as it should. The solution is to disable FSINN weather completely.

OK, this might have been the problem when I was flying on VATSIM in the MD-11 using FSINN, but not with the pmdg 737ngx...I haven't had the nerve to put this on Vatsim yet :) so I wasn't using FSINN, of course...For example last night flying from KCLT to KDFW in the 737NGX for another company, (not on Vatsim) (not using FSINN) I noticed my take-off temp was +15degrees C...after climbing up to around FL210 I noticed the temp was +45 degrees C and the engines started slowing down and almost went into a stall, and the AP red light appeared and all navigation was turned off...After clicking the FSUPIC panel "Clear all weather" as I mentioned in my previous post, the temp dropped drastically in the negative areas, the engine came alive, picked up speed, and was able to gain control of the aircraft...

[nrcrate 40]

What are you using for weather?

[ual1819 1]

OK, this might have been the problem when I was flying on VATSIM in the MD-11 using FSINN .... After clicking the FSUPIC panel "Clear all weather" as I mentioned in my previous post, the temp dropped drastically in the negative areas, the engine came alive, picked up speed, and was able to gain control of the aircraft...

Bad weather data (air temps in particular) will always wreak havoc with climb performance. This problem is not limited to the NGX, but because of the accuracy of the simulation, the NGX is more susceptible to this problem than other add-ons. You need to see a negative value for TAT at cruise flight levels in the 300s (-10c or lower) if you don't want your aircraft to fall out of the sky. I've also noticed that even with a reliable source of weather data (REX), if FSUIPC has "weather smoothing" turned on (dampening the rate of temp, pressure, and wind changes) similar climb performance problems can happen until the pressure/temps catch up.

[Heron 0]

Things here back to normal again. I reset FSUIPC to Normal Defaults and reassign the smooth weather settings (temp and pressure). It is still a mystery why this happened after ages without touching FSUIPC and just after NGX installation. Regards

[hornplayer 1]

What are you using for weather?

I wasn't using any add-on programs at all...Before I purchased NGX from PMDG I was flying the pmdg md11 and the pmdg 747-400F and 8I models with no problems with REX2...Anyway, I will attempt to use the suggestions by resetting FSUIPC to Normal Degaults and reassign the smooth weather settings (temp and pressure) as suggested by Heron, and detect what happens....Today, I was on teamspeak with Nick and he suggested I load the Trik kill the engine then reload ngx...That appeared to work...The flight from KDFW to KPHX was uneventful to say the least except on approach the engine wouldn't slow down according to the FMS settings and hit the RWY to hard and cracked the front wheel off...