Running FSX SP2 with ASA SP1. Trying to make ASA running without DWC, but seems a useless attempt, after the dozens I made. I usually have the same weather everywhere, and it is the wx I have at origin. I had already discussed about this, but today I found out something more. Initially the weather depicts fine, all around, looking at various stations in the radius of action, the wx is depicted accordingly. Problems begin after I take off and start moving away from the origin airport. Stations which weren't written initially because too far, start getting depicted, yes, but with the wx I had at the departure. I can move 100 like 5000 miles, and nothing changes. All the stations are reporting the same exact thing, same winds, clouds visibility pressure and temperature.So I made a desperate attempt (as I want to remind you that with DWC on I can't run Radar contact, and the AI go crazy for the reasons you already know, so I really need the NOT-DWC to work). I fooled ASA, and made it believe that FSX was FS9. I simply took the FSUIPC for FS9, put it in the modules folder, along with the FSUIPC4.INI modified as FSUIPC.INI. Loaded ASA per FS9, gave it the folders paths it asked for, and it started. Incredible, it was working! WX was being depicted accordingly, it just suffers a bit of stuttering, but I was expecting that. Now, apart the issues which may arise, my aim was different, seeing if the weather was updated. And it was! I can even load an historical weather after the real time was loaded, which is a mission impossible when ASA works normally in FSX (I have to start ASA, load the historical wx, then start FSX, or it will never load the historical). So, what's going on? Don't ask me to run ASA and set/unset options, move the sliders etc, because I tried every single possible solution, and the result has always been the same. There is something broken between what ASA sends and what FS receives when running via Simconnect, after the initial one. I don't know why it takes the origin wx as the "predefined". If I close ASA, restart it, the wx is depicted again, but I should do it every ten minutes, and I run it on my FS PC, not remote. I already tried to uninstall ASA, deactivate firewall, antivirus, deleted the remaining folders, reinstalled ASA, then the update. Nothing again.I'm short of options...please help me out here, or I'd have to use this hybrid version of ASA, the only way to use it right now.Thank youFederico

Hi,Even Pete will tell you that FSUIPC3 will not work in FSX. So what you did was disable FSUIPC in FSX and now ASA is communicating with SimConnect only.Thanks,

Hi Jim, so you say that ASA is working via Simconnect even that way? It says FSUIPC 3.8.5 found and initialized, it doesn't talk of Simconnect, and FSUIPC is not disabled, it's there in my menu, the V4 of course, proven by the fact that Radar Contact is working. ASA is started in FS9 mode, not FSX. CheersFederico

... so you say that ASA is working via Simconnect even that way? It says FSUIPC 3.8.5 found and initialized, it doesn't talk of Simconnect, and FSUIPC is not disabled, it's there in my menu, the V4 of course, proven by the fact that Radar Contact is working. ASA is started in FS9 mode, not FSX.

First off, Federico, the FSUIPC.DLL in your FSX modules folder is not being loaded, it is not running. It cannot run. FS9 modules are specially tailored to run in FS9 and before. FSX modules are loaded and run by SimConnect and the latter has to be configured to make it do so. If FSUIPC3 ever did get to run in FSX, it would certainly crash it or stop itself running if my checking is good enough.You can prove to yourself it isn't running, just delete it from the modules folder whilst FSX is running -- Windows wouldn't let you do that if it were active in any way.Second, it appears that ASA, in FS9 mode, checks for FSUIPC not by linking to it and reading its version number via the FSUIPC interface (like 99.9% of programs), but it seems it goes to the Modules folder, finds FSUIPC.DLL, and reads its version number there! If FSUIPC.DLL isn't there, or it's too old, it won't even try to connect even though there is a valid interface (the one provided by FSUIPC4) actually running.I find this way of doing things, er, quite quaint, if not actually strange ...Anyway:With FSUIPC.DLL copied into the FSX Modules folder, where it sits gormless, never doing anything (and therefore certainly not needing your FSUIPC INI file, Federico), I've just tried switching ASA from FSX mode to FS9 mode, even whilst it was running in FSX mode. You can do this and, after supplying the relevant paths, it will restart itself in FS9 mode instead of FSX mode. And in this mode is is using FSUIPC4 (not FSUIPC3 nor SimConnect). You can check this for yourself by looking in the FSUIPC4.LOG where you will see entries like this when ASA starts up:

   480110 NWI weather clear actioned   480110 External weather discarded   480157 Weather Mode now = Theme   480157 Weather Mode now = Custom

So, Jim -- you were half correct. FSUIPC3 won't run in FSX, but you CAN run ASA with FSX via FSUIPC4, using its FS9 mode, if it is fooled by putting FSUIPC3 into FSX's Modules folder!===========BUT what intrigues me even more is, how does ASA manage to provide correct weather at each station when in FS9 mode, using FSUIPC's interface to SimConnect, but not when it is using SimConnect directly? After all, all FSUIPC4 is really doing is interpreting the weather data being sent as binary data via the offsets in its interface, converting them to the extended METAR strings accepted by SimConnect, and sending them on to SimConnect. FSUIPC4 has no cleverer access into FSX to do this than ASA. It makes no sense. Maybe, just maybe, ASA's extended METAR strings sent to SimConnect are being rejected in some way, so the weather isn't getting set?Additionally, it evidently cannot be a common problem (this one of the same weather everywhere), else there'd surely be hell up, a lot more complaints than seem to be reported.I'm tied up (going away for a long weekend) at present, but if I get time next week I'll try some flights myself -- not long ones like Fede (an hour's tops for me, no patience with cruises), but I'll see if I can choose a route through varied weather. Meanwhile, Federico, since you seem to be getting the problem very reproducibly, perhaps you could choose a reasonably short flight where you can demonstrate the problem, but first, before starting FSX, enable SimConnect logging (instructions on how to do this are in the FSX Help announcement on my support forum). The file will become HUGE, and maybe even unviewable unless you have an advanced text editor, but I think looking at the weather setting events in that might be the only way to show HiFi Simulations what is happening.Meanwhile, Jim, is Damian around? Can he comment on this business for us do you think?Best RegardsPete

Thank you very much Pete! :)Be sure I'll follow your instructions, and report back.Thanks again for your time and patienceCheersFede

... but if I get time next week I'll try some flights myself -- not long ones like Fede (an hour's tops for me, no patience with cruises), but I'll see if I can choose a route through varied weather.

I've just done two half-flights -- Manchester to Bristol, but I aborted about half way after I'd gathered data for a total of 5 different WX stations (EGCC, EGCD, EGOE, EGWC, EGBO). I kept below 500 feet all the time to ensure I was reading ground weather. I did this twice, once with ASA in FS9 mode, and one in FSX mode. (Unfortunately the METARs it downloaded had been updated between the two, so the weathers weren't identical, but the results are still interesting and valid). I had WeatherSet2 reading weather at the same time (this is what RC and ATIS would get), and ASA's "report" display showing me the nearest WX station and its METAR.ASA in FS9 mode, using FSUIPC's interface for weather:* The winds weren't always correct, but usually within 5 degrees and 2-3 knots. The occasions they were a bit outside such a difference, they were changing in time as I passed nearer the WX station, so I put all the differences down to interpolation between stations. I followed a straight line, only passing WX stations at perhaps 8 miles closest.* The QNH was always within 1 hPa of the METAR value.* The temperatures and dewpoints were always within 2 degrees, usually 1.* The weather varied slightly all the way.ASA in FSX mode, using SimConnect directly* It started off at EGCC fine, everything agreeing quite precisely.* But 8 miles out of EGCC, the FSX QNH dropped from the METAR setting of 1011 down to 999, and continued decreasing as we moved!* At the same time, the temperatures dropped from 18/13 down to 12/8 ... !!!* The winds stayed almost correct, but more discrepancy than the FS9 mode trial -- 8 or 9 degrees difference being typical (and actually rather consistent, 8 or 9 degrees clockwise).* But the pressure and temperatures never went anywhere near correct again. QNH dropped to a low of 992 before rising to 997, whilst all along being reported by ASA as being 1011 to 1010. And the highest the temperatures ever go to again was 11/6, when ASA was reporting 19/13.ConclusionI don't get the same symptoms as Federico -- the weather in FSX is definitely changing. But it isn't right, and in fact it is very wrong especially for temperatures and QNH. I really cannot believe this! It seems so bad. It is far better, in fact, in FS9 mode! Astonishing!Note that I am currently using ASA Beta build 435. Before that I was in 433, but I'd not done enough flights to tell if I had a problem EXCEPT that I had noticed pressing wild QNH swings, with 990 reported one moment and 1013 or more the next.I've uses ASA since release and not noticed the problems before (though I'd not looked for any). So I'm wondering if these problems were introduced in SP1. No easy way to tell without uninstalling completely and reinstalling without the update I presume.Best RegardsPete

I've done some SimConnect logging, and comparing what FSUIPC4 sends to SimConnect when setting weather on behalf of ASA with what ASA sends for itself in FSX mode, there is one striking difference:FS9 mode, via FSUIPC:

WeatherSetObservation:Seconds=0, szMETAR="EGCD 201050Z 22502KT&D595NG 19530KT&A595NG 21034KT&A1281NG 21039KT&A2195NG 21250KT&A3109NG 21760KT&A4481NG 21361KT&A6310NG 20661KT&A8139NG 21059KT&A9663NG 20760KT&A11034NG 22051KT&A12558NG 22433KT&A14082NG 49KM&B-91&D21336 2CU049&CU016FLVN000N 4ST137&ST024FNVN000N 2CI389&CI002FNVN000T 17/14&A109 16/04&A1023 13/01&A1938 10/M02&A2852 01/M11&A3767 M11/M23&A5595 M22/M34&A7424 M36/M48&A9253 M47/M59&A10472 M57/M69&A11996 M57/M69&A13520 M54/M66&A15044 Q1008 "

FSX mode, direct from SimConnect (unfortunately, different METAR):

WeatherSetObservation:Seconds=30, szMETAR="EGCD 201331Z 23118KT&D457OG 190V270 18632KT&A823NG 20640KT&A1738OG 21045KT&A2652OG 20752KT&A3567LG 20764KT&A5395NG 20667KT&A7224OG 20471KT&A9053NG 19869KT&A10272NG 20168KT&A11796NG 20655KT&A13320NG 21235KT&A14844NG 56KM&B-2000&D4000 60SM&B2000&D28000 4CU074&CU000FNVN000N 19/11 16/04&A823 13/01&A1738 10/M02&A2652 01/M11&A3567 M11/M23&A5395 M23/M35&A7224 M38/M50&A9053 M47/M59&A10272 M55/M67&A11796 M56/M68&A13320 M54/M66&A14844 Q1007"

The only difference really worthy of note is that parameter "Seconds=". When ASA sends the request to FSUIPC, it is not setting the Seconds parameter (naturally, because it assumes it is talking to FS9, not FSX, and the Seconds parameter, whilst supported by FSUIPC4, wouldn't be in its remit for sending weather via FSUIPC3.I'm wondering if that 30 seconds delay in FSX "realising" the weather at the station is actually stopping it becoming effective, either totally, or until it is too late and we are passed.I couldn't find any SimConnect exceptions due to ASA in the log except for this one:

> 7683.54206 [127, 855]WeatherCreateThermal:RequestID=8, lat=53.325172, lon=-2.263944, alt=996.000000, radius=2.000000, height=-19.000000, coreRate=0.005081, coreTurbulence=0.100000, sinkRate=0.005081, sinkTurbulence=0.300000, coreSize=1.600000, coreTransitionSize=0.100000, sinkLayerSize=0.200000, sinkTransitionSize=0.100000< 7683.54214 [127] >>>>>  EXCEPTION=20, SendID=855, Index=6  <<<<<

where ASA, in FSX mode, is attempting to create a thermal and failing for some reason (negative height, perhaps?). This won't be relevant to the odd weather settings though.Still puzzled, but I do wonder if it would be possible to apply a patch to get the "Seconds" parameter set to 0, just to see if that makes an interesting difference.RegardsPete

I did what Pete suggested and made two logs, one from FSUIPC and the other from Simconnect.Departing from EGLL the wx from ASA screen was wind 240/16 210V280 vis 10+ SKC Q1014Simconnect shows : WeatherSetObservation:Seconds=0, szMETAR="EGLL 201607Z 24016KT&D457NG 210V280 22928KT&A890OG 23133KT&A1805NG 22939KT&A2719NG 21459KT&A3634NG 20486KT&A5462NG 19794KT&A7291NG 199100KT&A9120NG 196101KT&A10339NG 20181KT&A11863NG 21158KT&A13387NG 21738KT&A14911NG 47KM&B-2000&D4000 99SM&B2000&D28000 3CI272&CI000FNVN000N 2CI294&CI000FNVN000N 23/09 15/03&A890 07/M05&A1805 04/M08&A2719 M03/M15&A3634 M15/M27&A5462 M26/M38&A7291 M41/M53&A9120 M49/M61&A10339 M47/M59&A11863 M48/M60&A13387 M51/M63&A14911 Q1014"Note that here the weathersetobservation is at 0 seconds, this is the first line with EGLL; after that the value jumps to 30Then always from simconnect the global one:WeatherSetObservation:Seconds=0, szMETAR="GLOB 201607Z 24016KT&D457NG 210V280 22928KT&A890OG 23133KT&A1805NG 22939KT&A2719NG 21459KT&A3634NG 20486KT&A5462NG 19794KT&A7291NG 199100KT&A9120NG 196101KT&A10339NG 20181KT&A11863NG 21158KT&A13387NG 21738KT&A14911NG 47KM&B-2000&D4000 99SM&B2000&D28000 3CI272&CI000FNVN000N 2CI294&CI000FNVN000N 23/09 15/03&A890 07/M05&A1805 04/M08&A2719 M03/M15&A3634 M15/M27&A5462 M26/M38&A7291 M41/M53&A9120 M49/M61&A10339 M47/M59&A11863 M48/M60&A13387 M51/M63&A14911 Q1014"Pretty much similar to EGLL report, of course. FSX itself reported such values, the closest stations had their correct values, while the "outer" ones written had the same WX as EGLL, exactly the same one.I started moving northbound, and this is what I found (I am reporting just one station far from EGLL, as example):Simconnect: WeatherSetObservation:Seconds=30, szMETAR="EGNB 201608Z 23011KT&D457LG 22429KT&A910LG 22737KT&A1825NG 22039KT&A2739OG 20346KT&A3654OG 19680KT&A5482NG 186100KT&A7311NG 184101KT&A9140LG 182103KT&A10359NG 18881KT&A11883NG 20055KT&A13407NG 21237KT&A14931NG 48KM&B-2000&D4000 99SM&B2000&D28000 2CU077&CU000FOVN000N 6ST234&ST000FOVN000N 21/10 14/02&A910 07/M05&A1825 05/M07&A2739 M04/M16&A3654 M16/M28&A5482 M26/M38&A7311 M41/M53&A9140 M49/M61&A10359 M47/M59&A11883 M47/M59&A13407 M50/M62&A14931 Q1008"FSUIPC : "EGNB&A4 211147Z 24016KT&D457NG 205V275 25128KT&A886LG 25128KT&A910NG 23133KT&A1801NG 23133KT&A1825NG 23339KT&A2715NG 23339KT&A2739NG 24459KT&A3630NG 24459KT&A3654NG 22486KT&A5458NG 22486KT&A5482NG 21194KT&A7287NG 21194KT&A7311NG 199100KT&A9116NG 199100KT&A9140NG 202101KT&A10335NG 202100KT&A10359NG 20181KT&A11859NG 20180KT&A11883NG 21158KT&A13383NG 21157KT&A13407NG 21738KT&A14907NG 21738KT&A14931NG 47KM&B-1504&D3500 100KM&B1996&D28000 3CI271&CI000FNVN000N 2CI293&CI000FNVN000N 23/09 15/03&A886 14/02&A910 07/-5&A1801 06/-5&A1825 04/-8&A2715 03/-8&A2739 -3/-15&A3630 -3/-15&A3654 -15/-27&A5458 -15/-27&A5482 -26/-38&A7287 -26/-38&A7311 -41/-53&A9116 -41/-53&A9140 -49/-61&A10335 -48/-60&A10359 -47/-59&A11859 -47/-59&A11883 -48/-60&A13383 -48/-60&A13407 -51/-63&A14907 -51/-63&A14931 Q1014 @@@ 29 15 251 28 | 30 14 251 28 | 59 7 231 33 | 60 6 231 33 | 89 4 233 39 | 90 3 233 39 | 119 -3 244 59 | 120 -3 244 59 | 179 -15 224 86 | 180 -15 224 86 | 239 -26 211 94 | 240 -26 211 94 | 299 -41 199 100 | 300 -41 199 100 | 339 -49 202 101 | 340 -48 202 100 | 389 -47 201 81 | 390 -47 201 80 | 439 -48 211 58 | 440 -48 211 57 | 489 -51 217 38 | 490 -51 217 38 | "OrSimconnect: WeatherSetObservation:Seconds=30, szMETAR="EGXG 201450Z 23023KT&D457SM 23428KT&A905SM 23533KT&A1820NG 22835KT&A2734MG 20840KT&A3649NG 19972KT&A5477NG 185103KT&A7306NG 185103KT&A9135MG 183101KT&A10354NG 19077KT&A11878NG 20153KT&A13402NG 21236KT&A14926NG 48KM&B-2000&D2914 99SM&B914&D28000 1CU040&CU000FOVN000N 7CU274&CU000FLVN000N 20/09 13/01&A905 07/M05&A1820 04/M08&A2734 M06/M18&A3649 M18/M30&A5477 M27/M39&A7306 M42/M54&A9135 M48/M60&A10354 M45/M57&A11878 M46/M58&A13402 M50/M62&A14926 Q1007"FSUIPC : EGXG&A9 211147Z 24016KT&D457NG 205V275 25128KT&A881LG 25128KT&A905NG 23133KT&A1796NG 23133KT&A1820NG 23339KT&A2710NG 23339KT&A2734NG 24459KT&A3625NG 24459KT&A3649NG 22486KT&A5453NG 22486KT&A5477NG 21194KT&A7282NG 21194KT&A7306NG 199100KT&A9111NG 199100KT&A9135NG 202101KT&A10330NG 202100KT&A10354NG 20181KT&A11854NG 20180KT&A11878NG 21158KT&A13378NG 21157KT&A13402NG 21738KT&A14902NG 21738KT&A14926NG 47KM&B-1509&D3500 100KM&B1991&D28000 3CI271&CI000FNVN000N 2CI293&CI000FNVN000N 23/09 15/03&A881 14/02&A905 07/-5&A1796 06/-5&A1820 04/-8&A2710 03/-8&A2734 -3/-15&A3625 -3/-15&A3649 -15/-27&A5453 -15/-27&A5477 -26/-38&A7282 -26/-38&A7306 -41/-53&A9111 -41/-53&A9135 -49/-61&A10330 -48/-60&A10354 -47/-59&A11854 -47/-59&A11878 -48/-60&A13378 -48/-60&A13402 -51/-63&A14902 -51/-63&A14926 Q1014 @@@ 29 15 251 28 | 30 14 251 28 | 59 7 231 33 | 60 6 231 33 | 89 4 233 39 | 90 3 233 39 | 119 -3 244 59 | 120 -3 244 59 | 179 -15 224 86 | 180 -15 224 86 | 239 -26 211 94 | 240 -26 211 94 | 299 -41 199 100 | 300 -41 199 100 | 339 -49 202 101 | 340 -48 202 100 | 389 -47 201 81 | 390 -47 201 80 | 439 -48 211 58 | 440 -48 211 57 | 489 -51 217 38 | 490 -51 217 38 | "I can go on, but it's the same. Simconnect reports what ASA says, but FSUIPC reads what's set in FSX, and FSUIPC shows the wx doesn't change, I just bolded the wind.Clouds sometimes appeared, but didn't find any rain, and that was reported. QNH remained about 1014 all flight long, and reports were quite different. I kept the logs, in case you want them. Or can make others. CheersFede

I did what Pete suggested and made two logs, one from FSUIPC and the other from Simconnect.

Interesting results. Weren't there any other GLOB settings? Because what appears to happen is that the GLOB settings, being almost the same as the initial departure settings, then act as the default for all the other weather stations which don't seem to acquire the values sent to them -- assuming of course that the requisite 30 seconds had past since the "WeatherSetObservation" for them.Just to show this, taking only the two elements which bugged me -- the QNH and the Temperatures:GLOB 23/09 Q1014EGNB ASA set: 21/10 Q1008FSUIPC read: 23/09 Q1014, i.e same as GLOBEGXG ASA set: 20/09 Q1007FSUIPC read: 23/09 Q1014, i.e. same as GLOBNow, unfortunately, you removed the timestamps from the beginnings of the lines, so we cannot tell whether at least 30 seconds passed between ASA writing the different weather and FSUIPC reading those you showed. If 30 seconds hadn't passed then the default, the GLOB weather, would have prevailed, and that is what you are seeing.The other question is, were any of those "WeatherSetObservation" commands from ASA rejected by SimConnect with an exception? If so, the details of the exception should show what is wrong.One little thing seems slightly odd to me. In the WeatherSetObservation METARs from ASA there seems to be two overlapping visibility layers:e.g. 47KM&B-2000&D4000 99SM&B2000&D28000 for EGNB, and 47KM&B-2000&D4000 99SM&B2000&D28000 for GLOBI'm not sure what the intention is there, but I doubt it has any adverse effect, and the GLOB pair are reflected in what FSUIPC reads back in any case.Multiple visibility layers never worked properly in FS versions before FSX, and I couldn't do much with them even in FSX, so I'm not sure how these are doing. Maybe overlapping them was always the solution I missed! ;-)I'm away now till next Tuesday. Hopefully someone in HiFi will take this up, and also consider a test option to remove or change that 30 second parameter.Best RegardsPete

No, there aren't any other weatherset in glob mode, there are weatherrequestobservation and weatherobservation in glob, though.Timestamps : Simconnect says 237.80931 [ 6, 224] at first EGNB (the one I wrote), FSUIPC has its first entry for EGNB 1682393 (again, my example below), then it has this line 1682393 ***ICAOset = EGNB EGNE EGBN EGBG EGXT EGSF EGWZ EGTC EGWE. Second example says simconnect > 240.81404 [ 6, 234] FSUIPC 1752905 and again 1752905 ***ICAOset = EGXG EGNB EGNE EGBN EGBG EGXT EGSF EGWZ EGTCHope this was what you were referring to.As for the question Pete asked me about "WeatherSetObservation" commands from ASA were rejected by SimConnect with an exception, he replied to me via Email, I'll paste it here (my mail is blue, he replies black, easy :) ) >> so I have this:> 3.26170 [ 4, 1]Open: Version=0x00000004 Name="FSUIPC4"and> 146.06700 [ 6, 1]Open: Version=0x00000004 Name="ASA Managed Data Request"So I assume ASA is 6? And FSUIPC4 is 4 then? <<Yes, correct.>> the line before the exceptions are:> 146.06712 [ 4, 3677]WeatherRequestObservationAtNearestStation:RequestID=-805306354, lat=51.477489, lon=-0.488280< 146.06721 [4] >>>>> EXCEPTION=15, SendID=3677, Index=-1 <<Okay. Those are simply FSX saying there's no WX station near enough to that Lat/Lon. That's not a problem.>> and> 2142.42926 [ 4, 9988]RequestDataOnSimObject:RequestID=-536870912, DefineID=-86050082, ObjectID=1, Period=0, Flags=3, origin=0, interval=0, limit=0< 2142.42928 [4] >>>>> EXCEPTION=3, SendID=9988, Index=-1 <<So, if there is anything more I could do just ask me Jim, ok? I hope we gave you some details to sort something out. The problems I am expriencing so heavily, might be also the cause of frozen cruising winds, stations not updating, etc, that also other users are reporting.CheersFederico

Hi, I noticed another strange thing from the logs. The time. As you can see above, the simconnect shows a metar like GLOB 201607Z 24016KT&D457NG and EGLL 201607Z 24016KT&D457NG initially, and FSUIPC reads EGLL&A24 201607Z 24016KT and GLOB&A0 201607Z 24016KT&D457NG. As you can see the times match. After that, Simconnect shows always the same time but FSUIPC starts reading this EGLL&A24 211147Z 16210KT&D627NG and GLOB&A0 201607Z 24016KT&D457NG. It goes on this way, while the glob has always the Simconnect log string time, FSUIPC reads the glob like the simconnect, but the local ICAO is set at a totally different time. I don't know how much it can influence this, but the matching times (GLOB and simconnect) are depicted, while the not-matching ones (ICAO-simconnect) are disregarded. So it seems ar least. From the strings in my previous post you can see also other stations are reporting this mismatch, and it's the same everywhere, each station. Hope this helps a bit more.CheersFedeP.S. Of course I didn't change anything, time date, acceleration, etc..

... while the glob has always the Simconnect log string time, FSUIPC reads the glob like the simconnect, but the local ICAO is set at a totally different time.

I'm not sure exactly what you mean here, but if I'm understanding your worry correctly, then I think it is a non-event. It is likely that, with the weather change slider not set (by ASA) to freeze the weather, but allow it to change at some rate, the local weather at WX stations will be developing, so that each time it is read it will have a different timestamp to indicate this. GLOB weather is not developed, so retains the original setting timestamp.Note that you, the user, cannot set a zero rate of change -- the minimum position on the rate of change slider in the Options-Settings-Weather menu in FSX, is not actually zero rate of change. Zero rate can only be set via SimConnect, and even then I don't think it truly freezes things.RegardsPete

Thanks for the explanation Pete. Anyway, both my FSX sliders and ASA are set to zero, or I'd better say the lowest possible value :)Fede

Thank you so much for the tip about FSUIPC3 in the FSX Modules folder. Now I'm finally able to use ASA on a client pc with FSX on a server for the first time since ASA's release last year. Because simconnect and I have never been friends. Not that I use FSX that much, but I like a spin in a GA now and then. Thank's again guys!

Fede,In ASA set the rate of change slider to something in the middle and see what happens for you.Thanks,