Just got the new Beta. I'm flying in California right now, struggling to climb because it is showing +21 at FL270. It stayed around +19 all the way from about 10000ft. I sent an email earlier about the same problem in the 2.60.9 version. Checking the upper atmosphere weather report, I should be around -30 at this altitude. I have the download GRIB forcast checked.

 

Using PMDG NGX if that helps anything.

Try clearing your GRIB folder (but NOT the degrib.exe file) and then start Opus and allow it to repopulate it with fresh data.

It may be a bug in the aircraft sim, SteveW on another topic has suggested removing 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.

 

http://forum.avsim.net/topic/392959-high-oat-and-tat-over-india/#entry2537185

 

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

Got the latest Beta, and deleted the PMDG dll as described. Worked out well. The TAT was around -25 at cruise.

It may be a bug in the aircraft sim, SteveW on another topic has suggested removing the PMDG dll

I'm not too sure since I got the high TAT issue on a flight using the Level D 767 as well. Unless that PMDG .dll is active every time FSX fires up...

Besides, if it WAS the .dll wouldn't the issue be cropping up every time one used the NGX? On both flights (and panels - NGX and Level D -) I had the issue, after shutting down Opus and firing up AS2012 the high TAT vanished and normal temps were reported on both those flights.

 

One last thing. I noticed the high TAT only after I started using Opus so I honestly very much doubt it is the .dll that is the culprit unless that particular .dll interacts in some unusual way with the Opus engine. A real head-scratcher this... :Thinking:

OK, thanks for the feedback Tony.

 

Cheryl