Hi Tim,What was the OAT being reported in ASA and the TAT in FSX?Thanks,

I haven't experienced this problem. I have ASA, FSX SP2, XP 32 bit SP3, PMDG MD-11 and several other similar addons. Weird. Wish I could be of more help.

Hi All,So as the devil's friend: How come this user has never experienced this even with some of the same planes listed in this thread??Remember now, I am just getting ready for Halloween here!!

g'day jim...maybe a better question is in two parts '(a) have we enough here to conclude we have a problem with asa and ( b ) that it can be fixed?'speaking as a non-developer, the evidence seems persuasive for (a) - many have reported fsx above, i have reported fs9 above, not limited to pmdg add-ons, the latest report above is also with a default aircraft, restarting asa is one method reported as a work around. is this still too circumstantial or do we have the smoking gun here?!what does this mean then for ( b )?

Hi,maybe it depends on the Speed? I always fly 20 knots under Overspeed -> example: Overspeed begins at 280 Knots (Standard FSX B737) and my actual Speed is 260 Knots. This failue does not alway happens! I recognized it over China and Spain on a 2 hour trip. Maybe this helps...My Spec: FSX with SP 2, ASA, PMDG 747-400Q9550 @ 3,4 GHz, 8GB Ram, GeForce GTX260

It is definitely an intermittent fault - I certainly don't get it every time I fly. Also, it took me quite a while to spot that when it did happen, TAT was up at + 50 degrees.Therefore, I don't think you can read much into why certain people do or don't report it or how & when it crops up. There definitely is something going on: whether it's coming from the raw weather data, some aspect of FS processing or ASA, I don't know. I do know that switching back to FS weather and then refreshing ASA clears it but I don't know which components overlap and therefore whether that's significant. Just refreshing ASA doesn't clear it. I am surprised the stock aircraft react to TAT in this way: obviously they are a bit more sophisticated than I thought.I repeat again that I seem to get this on restarting saved flights. I don't think I ever had it in a flight which I have started & concluded in one session. Is there any possibility that weather data points are somehow not being cleared & overwritten properly so that erroneous or incomplete data are being left?

OK, I completed my saved flight today and was able to induce the high TAT.I loaded ASA & let the weather refresh, loaded & processed the flightplan and then loaded a new snapshot (which is based on XGrahics). I then closed ASA.I then defragged and loaded ASA & FSX and loaded the saved flight. Everything was fine.After a short while (unfortunately I didn't record how long) I went out & refreshed ASA and then refreshed AI - I may be mistaken but this seems to avoid the possibility getting instructed to do a tailwind landing on arrival.Immediately I went back to the flight I had a high positive TAT and as usual thrust dropped to next to nothing. I don't see any alternative to this having been created by the ASA refresh.I selected FS weather, allowed it to download and then reselected User Defined weather (i.e. ASA) and everything's fine.

Hi Chris,a. no, because it also can happen with FSX weather so it could be due to something in FSX.b. maybe or maybe not. It could turn into something that can be looked into but never fixed.One strange thing is that not once during our beta testing this was ever seen.Thanks,

We understand what you say.It seems to me that ASA is triggering the problem if not causing it, although of course I'm willing to be corrected. As I posted yesterday, I induced the problem directly by refreshing ASA into a saved flight and cured it by exiting to MS weather. That seems compelling to me but I'm no expert for sure.All we need I think is a statement from you that you've looked at as thoroughly as is practical for you and have found nothing on your side.I will re-run my saved flight and do the same thing again and let you know if the problems re-occurs.

Hi Chris,a. no, because it also can happen with FSX weather so it could be due to something in FSX.b. maybe or maybe not. It could turn into something that can be looked into but never fixed.One strange thing is that not once during our beta testing this was ever seen.Thanks,

Hello,have the problem ...It never occurred with FSX Online weather.It never occurred to ASv6.5.Since the change in ASA, but almost every flight over the mountains.TAT:FSX + MD-11 + Online weather -> OKFSX + MD-11 + ASv6.5 -> OKFSX + MD-11 + ASA -> problemGru

It may be helpful to know at what altitudes this occurs. I only have ASA for FSX, I do not use it for FS9, for that I have AS6.5.I have never experienced such TAT shifts in FS9 and AS6.5, both on- and offline with the MD-11, in around 200 hours of it, all above FL310, mostly FL350-390.I sue ASA on a separate PC, using simconnect to interface with FSX. I have no major issues recorded with ASA weather with respect to TAT in the JS41, though I don't go above FL250 in that...Perhaps it is a rogue METAR string or incorrect altitude weather data getting in every now and then? We need to look into when the problems occur (FL, IAS...) to give HiFi a little more to work with, particularly as it would appear that they cannot reproduce...Andrew

Hello- FSX - MD-11 - Windows XP - ASA - So far only in the mountains! Here also views the picturesOK -> TAT -18few seconds laterOK -> TAT -18few seconds later??? -> TAT +13few seconds later??? -> TAT +43if ASA does not run the same flight is OK...Gru

Hi All,After reading through this entire post, I wanted to weigh in and say I too suspect that ASA may be the culprit. It is very frustrating experiencing this serveral time during a long-haul flight. However if certain data components are filtered by FSX causing these temperature discrepancies, I can understand why Jskorna is being careful and trying to gather as much information as possible before making any admissions.Ailchim, thank you for starting this post and keeping it focused on the issue: FSX & ASA weather. I'm not looking for workarounds, logging in and out, saving and reloading, checking and editing logs, or any combination of afore mentioned. A fix and PATCH would be great!I too use PMDGs MD11 and purchased ASA because I was totally dissatisfied with FSXs default weather engine. In general, I am very pleased with ASA with the exception of the tempurature fluctuation issue and ATC directing tailwind landings due to incorrect or changing wind data once within range of destination airport. (However, I will search the forums for a post on that particular issue).Come on ASA! Don't let us down!

- So far only in the mountains!

I think this is a very interesting observation; come to think of it, I have noticed this too. The reason why I have experienced this so many times may then have been caused by the fact that my departure airport is LSZH rather often. The problem seems to be very persistent over Switzerland. A few days ago, I flew from EHAM to LEMD (WOODY UN872 KOVIN UY317 RESMI UN857 PPN UN10 VASUM BAN), and I only had the problem once and this was near the Pyrenees in the North of Spain / South of France. Flying over the flat areas in the Netherlands and France, the problem did not seem to come up. If I find the time, I will do some more testing tomorrow or over next week..

Hey Jim,I would like to report that this happended to me as well last night and only now do I realize that it is TAT related. I've had the PMDG MD-11 lose power in the past, but never noted the TAT. Last night I was eastbound, FL350 just west of the MEM VOR, on a route from KLAS to KATL. I started the flight with historical ASA weather starting with the 10/27/09-1900GMT dataset. FSX was started at KLAS, around noon local time on the 27th (fligthsim time). A couple hours out of Las Vegas, over MEM, my engine power started dying and the temp was high. My saving grace from the flight was the fact that I reached my TOD before hitting the stall-bars.My point is, maybe the issue can be replicated with historical ASA datasets. From my example above, try FL350 eastbound over the MEM VOR with the MD-11 using a historical set from 10/27/09 - around 2100GMT?You know how I like my long-haul flights Jim, and I routinely walk away from the flightdeck (family and kids make it hard not to). :( :( I got lucky last night in the fact that I just happened to be on-deck when I experienced this TAT issue.FSXsp2FSUIPC latest verson (reg'd) w/smoothingPMDG MD-11ASA 435 (beta) WDC = offSimconnect client