Hi,

 

I am currently flying between VOHS and VOBL at FL220. The weather depicted right now at 1840UTC is OAT 18°C and TAT 53°C !!!!!!! I think there may have a problem with the weather here.

I had 3 engines overheat in my PMDG MD11.

I just installed the latest version 2.6.

GRIB DATA is enable.

 

Stephane

I am having similar issues with 2.60.8. Two flights so far, one with the Level D 767(YSSY_PHNL) and one with the NGX (EHAM-LPPT); during the climb I got soaring OATs with the corresponding reduction/inability of the aircraft to climb.

 

I will be doing another flight tomorrow and will note when the temps start acting weird and maybe try to figure out what is making that happen (perhaps a wrong setting in my weather tab?). The inflight Report window correctly identified the OAT as -24 but the display in the aircraft was showing 38C and climbing. I was offline at the time.

 

Investigation ongoing...

A good check is to expect more or less -56c at around 36000ft

In most cases, at FL200, with an OAT around -1deg C, the TAT should be around +15deg C +20deg C, not +37deg C

The inflight Report window correctly identified the OAT as -24 but the display in the aircraft was showing 38C and climbing.

 

The TAT calculated by FSX can be monitored within our spy window, which stays open for 5 minutes at a time. Certain aircraft sims calculate their own temps.

 

Regards

Cheryl

I made another test between VABB and VAID. After take off, without doing anything, at about FL100, the TAT was 51deg C, again with an high EGT with the engines.

I click on update weather, and immediately the values were more coherent, about 19deg C at FL180.

If you could try beta 2.60.9 just posted, see our Flight1 Announcements topic for details. In our tests the SAT (monitored in the Spy window during climbs and descents) was much lower than the targets during the climb and held to the targets (as displayed in the Upper Atmosphere weather report window) much better during the descent. But its all really down to FSX, especially the TAT calculation, unless the aircraft sim undertakes its own TAT calculations.

 

Regards

Stephen

OpusFSX Beta Version 2.60.10 is now available for download on our website.

 

This beta greatly improves the GRIB SAT temperature control within the flight simulator, extends the improvements to the upper wind control for simulated (non-GRIB) winds, and corrects a slight problem with the automated wind stabilisation control.

I am currently in flight with the new BETA 2.60.10. After take off, things seems to be normal, the TAT was around 27deg decreasing slowly when climbing like the OAT. But I think there is still something with the temperature. When reaching my cruise level of FL290, at around 27000 ft, I had a sudden change in the temperature, the TAT going from around 15deg down to 5deg, and so, I had an overspeed warning in the MD11, and a change of speed and profile mode (like described in another topic). Unfortunately, I couldn't see the OAT values in the SPY window as it was closed during the event.

I had a problem wiith the J41 engines similar to yours, the cure was to remove the PMDG dll and guage security lines from fsx.cfg in notepad and start a flight and OK the plane to start the guages and dlls again.

It would be interesting to know if SteveW's suggestion cures your problem.

 

OpusFSX Beta Version 2.70.0 is now available for download on our website. If there is room, the Local Weather, Destination Weather, and all Alternate Weather report windows now display the targets for the upper (above FL200) ambient temperature (SAT), ambient wind direction and speed, also the current ambient air temperature and TAT inside the simulator. The idea being, you can now use these report windows to monitor the temeratures and ablove FL200 compare the target temperatures and winds with the actual.

 

Regards

Cheryl