Ok, I have confirmed this issue as well. I will be watching for a fix. I use FSUIPC for too many things to disconnect it.

Interesting. Pete actually recommends using FSUIPC to assign and calibrate such controllers as PFC instead of disabling or turning FSUIPC off. I think I am going tp try that route later. Joe

Interesting. Pete actually recommends using FSUIPC to assign and calibrate such controllers as PFC instead of disabling or turning FSUIPC off. I think I am going tp try that route later. Joe

Joe, that was me that was asking him that on his forum. Tomorrow morning I shall start working on that. I will let you know how it goes.

Thanks Eric . . . it is a real pain that such a sophisticated model AC would require that you dispatch FSUIPC that runs so many modules in go flight, PFC and other controllers. I am a home cockpit builder and I love this model. It IS the calibration of the elevator trim that is causing the problem. For some reason it struggles to be centered, at least in the initial climb. I have to go into FSUIPC and monitor the joystick calibration page and push/pull my yoke until it zero's out. Sometimes I have to do this a couple of times and then the AC start behaving normally. Interesting. I DO NOT want to dump FSUIPC. Thanks, I look forward to what you find. Joe

i have been getting these thrust problems and have no addons/vatsim/applets etc.

Peter,This is something only a few have encountered. I did during beta but we were unable to pin it down.Can you try to replicate this without any add-ons running. Move the FSUIPC directory temporarily etc? Secondly. Please try to post a screen shot of what the panel looks like when encountering this. State FMS setup including route, SID , STAR etc. And finally would be great if you could list any and all add-ons installed. We are trying to figure out a pattern here. Thanks in advance,

I have this issue on most every flight, it IS the FSUIPC centering or lack for the elevator (yoke and trim) axis. I have tested several way over the past few days and can get it to perform as it should by going into FSUIPC on the Calibration Page and just push/pull my yoke until it give a zero value. Sometimes I have to do this more than once or twice, but for now it is my 'work around' It can sometime be the throttle range but rarely. Hope that helps, we have Pete Dowson looking into this and a couple of others here to nail this issue.

Fix the FSUIPC problem? Easy: don't calibrate your controllers through FSUIPC. I'm not being glib or disrespectful. This aircraft does not need FSUIPC for controller calibration. (If you find that your other aircraft do work better with FSUIPC, fine, there's a checkbox in FSUIPC that allows you to set up an individual aircraft the way you want it.)

But many FSUIPC user dont even have controllers enabled in FSX because it is all handled through the FSUIPC assignment tab. Just saying 'dont calibrate' is not the full picture.

This has nothing to do with FSUIPC or the plane or the panel. Either your FSX settings are suspect or something injects very high temperature for any given altitude. Mats re-installed FSX and the problem magically disappeared.

i dont have FSUIPC nor a joystick and i am experiencing the same problem regarding thrust.

This has nothing to do with FSUIPC or the plane or the panel. Perhaps it was missed first time round so bold, italics, underlined and size 24. PS. General settings : using show IAS or TAS ?

This has nothing to do with FSUIPC or the plane or the panel. Perhaps it was missed first time round so bold, italics, underlined and size 24. PS. General settings : using show IAS or TAS ?

Which part? The throttles not going below 42%, the elevator issue Joe mentions above, the gear and spoilers not working with hardware or the climb issues. I think they are all somehow related to fsuipc. If what you are saying is all that stuff will not be an issue if set up properly and the ngx does in fact get along with fsuipc then ok, w need to try and help one another with our settings.

If we dispense with FSUIPC calibration, aren't we then forced to use the keyboard F2 for Reverse thrust?

Hi all, Did some 6 flights with NGX (no Hot Fix) + REX, online and offline, with everything working great. Until tonight when, flying an offline KPDX-KOAK, planned to FL390, she stopped climbing at 27900, N1 at 95%. There was nothing I could do from turning from VNAV to SPEED, on-off-on FDs, on-off-on A/T and A/P. I could gain some climbing via changing FMC CLB from ECON to RATE. But it went slowly to FL300 and stopped with the speed at 61,5 mach. The fuel was flowing quickly. I did not registered the OAT, sorry. Reaching TOD, things were back to normal and she descended the STAR RAIDR2 perfectly, crossing RAIDR at the published 7000. But, sadly, as the fuel was short, we tasted the salt of the bay, just before what would be a nice autoland at KOAK rwy 29. Tomorrow, I will repeat this flight, reporting here. Regards

I think this was mentioned already on this thread but I will say it again too as my experience on this current flight seems to prove it...it's the weather. I use ASE and when I fly, I usually set the computer clock to my scheduled departure time -20 minutes or so for preflight. Well, today, I started a flight early in the morning real time(8a) for a leg that was scheduled for an early afternoon departure(1235p). So, with my computer clock 'set in the future', ASE showed a message of certain items not being included due to the clock being in the future. One of these I would guess would be temps/winds at altitude. My TAT is reading +55C which I'm sure has to be why. I'm at FL210 for cruise from KJAX-KPHL because that's the best cruise altitude I can get. I can't get any higher. The engines just aren't getting enough air as the air density is so low with that high of a temp. I will try to confirm on the next flight as I will make sure to set my clock current or in the past so ASE has actual data to generate the weather at altitude. But, I don't think there is any need to be re-installing FSX or maybe even messing around with any FSUIPC stuff either(though I'm sure maybe somehow in there you can really mess things up too). I have FSUIPC registered version but it's basically at it's defaults with the exception of weather smoothing options. Just my two cents...

The newest version of FSUIPC (4.7 something), and ASE global mode should work in getting some cold air up in the higher alittudes. If you want exact winds and temps aloft, then the standard mode, the one that causes flashes in the sky when updating, should work, but the flashing sky gets annoying real fast. FSUIPC settings I have noticed can mess up ASEs weather implementation in the sim, but I have not had many problems since the new versions came out that play nice with ASE Global mode and Radar Contact. If the temps still aren't right, use FSUIPC to clear the weather, and force a refresh with ASE to get the weather re-injected and see if it comes back correctly, should only take a minute or so to do.

The newest version of FSUIPC (4.7 something), and ASE global mode should work in getting some cold air up in the higher alittudes. If you want exact winds and temps aloft, then the standard mode, the one that causes flashes in the sky when updating, should work, but the flashing sky gets annoying real fast. FSUIPC settings I have noticed can mess up ASEs weather implementation in the sim, but I have not had many problems since the new versions came out that play nice with ASE Global mode and Radar Contact. If the temps still aren't right, use FSUIPC to clear the weather, and force a refresh with ASE to get the weather re-injected and see if it comes back correctly, should only take a minute or so to do.

What changed with fsuipc in 4.7? As well what do you have on within fsuipc in regards to wx settings?