I don't know why, but all of a sudden I have no climb power once I reach FL210. I have re-installed the FSUIPC4.dll file, thinking that it was corrupted. But still no luck. Anyone else come across this issue? I also did a "repair" using the "repair option" in the installer. Still no luck.

 

 

 

 

I don't know why, but all of a sudden I have no climb power once I reach FL210. I have re-installed the FSUIPC4.dll file, thinking that it was corrupted. But still no luck. Anyone else come across this issue? I also did a "repair" using the "repair option" in the installer. Still no luck.

Are you using VATSIM weather?

Andrew,

 

Thanks for the response. With or without Vatsim weather, the issue still exists.

By "Climb power" do you mean the engines are rolling back towards flight idle?

what is the TAT showing? Anything weird like +40 or 50 degrees?

Ryan posted something about changing the rate of change in fs weather (whether an external weather addon is used or not).

 

Reducing this to zero could help.

Are you using VATSIM weather?

 

 

Andrew,

 

Thanks for the response. With or without Vatsim weather, the issue still exists.

 

Just to be sure, VATSIM weather isn't the problem, it's FSInn weather.

 

The VATSIM weather option in ActiveSky only makes sure it syncs the weather with VATSIM (which pulls its weather from the FAA, but with a slightly offset timing).  It's more there to be sure you're seeing the same weather the controllers see at that time.

 

FSInn is where the unusual temp problem lies, and it is a setting within FSInn itself.  It will override whatever other add-ons you're using (or at the very least, conflict).  So ensure that, if you're using FSInn, the weather feature of the program is turned off.  I don't use FSInn, though, so I couldn't tell you how to do that.

 

 

 

Additionally, when it comes to repairing and uninstalling, those should be saved for the last possible action.  As much as people think it's a cure-all, it can cause more problems if not done properly.  Try isolating the issue first:

What's it like with ActiveSky?

What's it like if I'm not logged into VATSIM/IVAO?

What's it like if I have no additional programs at all (ActiveSky, online clients, and so on)?

What's it like if I do the above and set the FSX weather to clear skies?

 

Doing this will likely cause the aircraft to "magically" work just fine.  Once it works just fine, you can then nail it down to the change you made.  Troubleshooting 101, folks.  You're not going to call any help desk and get them to say "oh, just reinstall it" for most programs, unlike what it seems too many do here.

This is how you do it ...

 

https://www.dropbox.com/s/r387c4cwb981vxu/FSInnWeatherDisable.jpg

 

1.  Launch FSInn

2.  In the Control Panel press the Set button (right side all the way down)

3.  In the General section select Weather

4.  Check the "Disable Weather by default" check box

5.  Check the "Disable All Precipitations" check box

 

In FSX for each flight I make certain the Weather Themes option is Clear Skies (clears all weather)

 

In FSX Settings ... Customize ... Weather option ... make sure the "Rate at which weather changes over time:" is set to "No change".

 

I use REX ... but also have used Active Sky 2012 and OPUS ... all problems went away when I made these changes.  Prior to making these changes I could never reach cruise altitude after around 18,000 to FL210.

 

C. T.

 

PS:  This was a lesson hard won

Problem solved

Problem solved

 

...by...?

 

It's always helpful to post what you ended up doing to solve the issue in case anyone happens to search and find your thread.