Departure WX at Destination

[JRBarrett 3,046]

Greetings,I posted a few weeks ago about the main issue I am having with ASA. I recently installed the 355 Beta update, and see no change.I run ASA networked with FSX. I also have ASX on the same machine as ASA, and have run some side-by-side comparisons, which I'll get to in a moment.I have run extensive tests to verify what I am seeing. Briefly, after ASA connects to FSX, and injects the initial weather at the departure airport, it seems to stop working. The weather displayed in FSX remains the same throughout my flight - whether the flight is 15 minutes long, or 8 hours. When I land at my destination, the weather is EXACTLY THE SAME as the weather that was in effect at my departure - same wind, temperature and barometric pressure. I have verified this with the program "WeatherSet" which comes with FSUIPC, and which displays the current weather at the aircraft's current position, both at the surface, and aloft. During a recent 2 hour flight, the weather shown in WeatherSet never changed.Despite this, there is no indication within ASA that there is any problem. The program continues to download updates at my selected interval of 20 minutes, and the "depiction output active message" is on most of the time. Examining the simconnect and ASA logs shows no errors - and no loss of connectivity with FSX.ASA always "knows" the current location of my aircraft - the present aircraft position shows correctly on the ASA map screen, as does the "closest station" on the report screen.I have tried many things... Using FSUICP (4.418) to control the wind shift, or turning FSUIPC weather options "off" and letting ASA control the wind and visbility directly (global mode). I have tried "force destination weather" on... and off. I have tried flights using an imported flight plan - and using no flight plan at all. I have tried starting ASA first, then FSX - and also the other way around.I have tried refreshing the weather both on the ground and aloft, but nothing works. ASA does NOT update the FSX weather after the initial load.ASX, using the very same setup, works perfectly.I believe that this problem - at least in my particular setup, has something to do with very slow TCP/IP throughput from ASA to FSX. I tried an experiment. I Started FSX and then ASA and timed how long it took between the message: "ASA is starting initial weather depiction" and the message: "Initial weather depiction complete" that appear on the FSX screen. On average, it takes over 25 minutes (!) for the initial depiction to be fully transmitted to FSX. This, with the default Cessna, sitting on the ground, engine off, and NO other programs running. I can repeat this slow throughput many times, and it makes no difference if the startrup sequence is ASA the FSX, or FSX, then ASA.It is as if the TCP/IP communication channel between ASA and FSX (via Simconnect) has dropped down to the speed of a 300-baud modem.ASX, which works perfectly, takes no more than 4 minutes (tops) to load its depiction.I do NOT use the option in ASA for virtual stations.There is no problem with the TCP/IP connectivity between the two computers... I can transfer a 100 megabyte file between the two machines, in either direction, in less than 20 seconds. I run no antivirus software, or firewall on either machine when I am using FSX. And, again, ASX - (which uses the very same Simconnect interface, between the very same computers), shows no such problem. ASX throughput is very quick, and when I do a flight with ASX, the destination weather is always correct.Also, ASA induces a stutter in FSX whenever it is active.... a two-to-three second pause that happens approximately every 45 seconds. ASX does not cause this. The stutter was present in the RTM ASA, and also in B355.Jim Barrett

[JSkorna 137]

Hi,I will mark this as a TCP issue and we'll take a look.Thanks,

[JRBarrett 3,046]

Hi,I will mark this as a TCP issue and we'll take a look.Thanks,

Thanks. I believe the extremely long weather-injection times from ASA into FSX may be the main cause of the other problems I'm seeing. (Initial weather never changes from departure conditions despite time and distance.)By the way, the upper winds and temps DO change as I climb. Unfortunately they are the upper winds forecast for the departure airport and remain constant no matter how far I fly. It certainly DOES eliminate wind-shift problems! :)One thing I noted for what it's worth. Looking at the logs for ASA vs. ASX, it appears that ASA is injecting weather from stations over a much broader geographical area than ASX... which is to say that there appear to be many more discrete weather reports in the depiction "package" sent to FSX by ASA, (as opposed to ASX.) I'm sure this has some bearing on why it takes so much longer. This appears to hold true whether or not I load a flight plan into ASA.Jim Barrett