Peter, FSUIPC is a useful utility if used within constraints and for certain purposes, I know Pete and spoke to Pete a few times and have a hell of a lot of respect for Pete and his work. However : make sure you calibrate your axes OUTSIDE FSUIPC please using native driver/software. The plane is driven by software and it is very important that any control input comes pure and unfiltered to simconnect and thence to us. You also need to make sure that you don't get density altitude 6000000000000 at FL270, say, because something is injecting ground temperature (e.g. 25 Celsius) at this altitude. Thank you.

I had similar problem Gawick-Cork. In the 747X could get to FL380 easy, on this flight I noticed T/C & T/D were almost together & I only managed FL250 before descent. ASE weather engine with REX textures-Gatwick & Cork Extreme-ENB-Ezdok.With same set up, Dublin-Edinburgh, no issues. Edinburgh Extreme also.On another flight I got unable next altitude, only needed 8000ft climb with 56miles to go from FL260. Empty aircraft load & light fuel 10000lbs! Ground temp at departure 12c/54F, Gatwick 200above sea level. TST at FL260 -25. Tried de ice just in case but made no difference.Sim running very smooth with good frames 25-28 much better than 747x so it beats me!Also getting the same issue with mouse & after saving flight FSX crashes, every time. Not had that before ever.Intoduction read, Loaed all pop ups during install + added files to cfg. Sent cfg to be adjusted as per intro!Also had some serious trouble with contollers for some reason & I'm still working on that. Everything worked great on the 747x. Well it's bedtime now so I'll try again tomoorow. System is i7 Windows 7 Pro. 8gig ram, 1.8gig Nvidia 360gtx.

Peter, FSUIPC is a useful utility if used within constraints and for certain purposes, I know Pete and spoke to Pete a few times and have a hell of a lot of respect for Pete and his work. However : make sure you calibrate your axes OUTSIDE FSUIPC please using native driver/software. The plane is driven by software and it is very important that any control input comes pure and unfiltered to simconnect and thence to us. You also need to make sure that you don't get density altitude 6000000000000 at FL270, say, because something is injecting ground temperature (e.g. 25 Celsius) at this altitude. Thank you.

Wow. That will suck. I have everything (and I mean everything) assigned through FSUIPC and I also calibrate all axis through it as well. I would imagine this has the potential to effect a LOT of users. Would this also require the removal of STICK_SENSITIVTY_MODE=0 from the cfg? Pete recommends this if calibrating in FSUIPC.

Axis calibration at your own risk. In general my experience using and programming on a lot of operating systems (plus a lot of applications) is : if a job can be properly done using a system's native utility then do it through the system's native utility and do not mess around too much. The rest require expertise, experimentation and knowledge as to what exactly one is doing. My 2 cents. PS. If you ask Pete who happens to be a knowledgeable guy will tell you the same.

I would normally agree, however it is generally accepted that FS internal calibration and axis assignment options are both limited and less than precise. I think anyone who has FSUIPC installed is likely to be using at least the calibration function if not the axis assignments. Its one of the major features and bonus of using FSUIPC. However, I understand your position in terms of an addon product. The fact that FSUIPC is not recommended for joystick assignment and calibration should at least be mentioned somewhere officially. (if its not already)

It's hard to say which of my FSUIPC settings were messing things up, since I've used it for so many things for so long. I don't think any of the axes were being calibrated for this aircraft. (And the thrust problem occurred with autothrust/autoflight, with no throttle axes in use...) I'm restoring with a clean FSUIPC install and INI, then going to carefully add back settings from the old INI to try to isolate the source of the conflict.

I experienced this also and posted in another thread, but try reducing your center fuel to 0 while in the condition. One of my UA virtual pilots did this last night at my suggestion while unable to climb past 9,000' and 200 kts and the aircraft immediatley began to climb normally. I also experienced this.

However, I understand your position in terms of an addon product. The fact that FSUIPC is not recommended for joystick assignment and calibration should at least be mentioned somewhere officially. (if its not already)

It's in the intro manual...

I would normally agree, however it is generally accepted that FS internal calibration and axis assignment options are both limited and less than precise.

Glenn, you're absolutely right -- it is indeed generally accepted that FS internal calibration needs some help. One of the many ways in which the NGX is groundbreaking is that it changes the paradigm on controller calibration. You see, EV is neither limited nor less than precise.

G'day everyone, I have had this problem too...aircraft seems to run out of thrust and therefore airspeed begins to bleed off...usually above fl200...even disabling A/T and manually advancing thrust levers makes no diff...i have to pitch down to build up airspeed.....funny thing i have notice....i have another addon, the LevelD Boeing 767, it also happens on this....now the Boeing 737....i don't know if it is something i am doing wrong with the Boeing product because I have never had this problem with the PMDG MD-11...regards John

John, PROG Page 2. What is the ISA deviation reported ? Both the LDS 767 and this one are good examples of proper performance modelling. If something injects sea level temperature at altitude (particularly high altitude) your virtual engines will run out of breath. No climb. Have a look.

Thanks for quick reply, I will check next time i fly!regards John

I'm experiencing this problem, seem to be having strange temperatures at high altitude.Alt FL290, I have TAT of +44C with ISA DEV of 60C. I'm using Active Sky X and FSInn (weather disabled). Any suggestions how to correct this?

I am also seeing thrust problems on landing (even at idle thrust and full flaps, can't slow down enough). It all seems to relate to a mismatch between indicated N1% and the actual thrust being produced. I'm going to start process of elimination with other addons (most significantly FSUIPC).

I've had a number of problems climbing the 737-800WL. It seems like the actual (virtual) thrust output of the engines isn't matching the indicated N1, and the autoflight system gets confused struggling to keep the plane in the air. On one flight, I was at about 12000', 98% or so N1. The FD had the plane pitched 5 degrees nose *down* and it was unable to accelerate much above 200 knots. Fuel was lightly loaded (wing tanks only) and reasonable passenger load. This flight was so out of whack I had to abort, I couldn't even maintain clean speed. My current flight started to have problems above FL200. Similar problem, trying to maintain mach .79, 98% N1 (CLB thrust), nose down and V/S of basically 0. Around 13000 lbs of fuel in the wing tanks only, and a 70% passenger load. This time, I was slowly able to resume climbing by turning off autothrottle and manually selecting 102% N1, setting the CLB speed a bit lower to mach .70. The plane struggled between 0 and +500fpm and I finally got it up to FL340. I've seen similar issues before related to OAT/TAT being out of whack, but in this case the temp appears to be reasonable. (-24c at FL340) Anyone see this and know why it might be happening? Peter Vanags

It's hard to say which of my FSUIPC settings were messing things up, since I've used it for so many things for so long. I don't think any of the axes were being calibrated for this aircraft. (And the thrust problem occurred with autothrust/autoflight, with no throttle axes in use...) I'm restoring with a clean FSUIPC install and INI, then going to carefully add back settings from the old INI to try to isolate the source of the conflict.

Hmmm.... added to this is the PFC.dll which controls the PFC hardware that Pete also developed. Some of these problems are similar to mine. Guess I need to investigate further....

However : make sure you calibrate your axes OUTSIDE FSUIPC please using native driver/software. The plane is driven by software and it is very important that any control input comes pure and unfiltered to simconnect...

Well I guess this means PFC hardware users are hosed. Are hardware goes from pfc.dll to fsx with I believe some interface with fsuipc. No simconnect though..... Dang.