Hi Damian! I posted trouble ticket about this but I have more information concerning my trial of new Build 651 and it wouldn't warrant another trouble ticket so I am going to fill you in here. First off, using DWC with dynamic change to "0", it holds aloft weather perfectly and weather at departure airport also spot on. I set up a flght and changed the departure and destination weather directly through the display interface. I noticed, however, that if I attempted to alter the surface wind or temp, the aloft weather levels all went to "0". I tried pressing "parse" but then the levels came back but only surface weather was depicted for each altitude! I refreshed and got original wx metar back ( I use historic OFFLINE ) and this time only altered clouds and visibility and added heavy rain to make it hard IMC. I then selected "force wx destination zone" and "high priority" and saved Options. I then decided to manually set my destination wx to an 80nm radius but when I went back to the screen it had altered my clouds. I had orignally set overcast Cu from 200-8000 msl and CB from 8000-26000 broken. The metar had changed to 200-1300 overcast stratus and 8000-11000 Cu broken. I reset and tried to switch out of the screen and then back again and again the alteration but different each time but it would not retain the CB. During the takeoff, climb and enroute (to RJBB, Japan) the weather stayed perfectly in sync with what was being displayed in the ASE. I had set my flight plan in 'briefing' window and kept switching out of FSX and comparing my observed wx to "report" in ASE. When I arrived at about 16000 feet and 70nm from destination FSX ATC gave me clearance to the wrong runway. ASE showed both in "report" and in the logs that it was transmitting the correct wind and wx information to FSX. I went into the map menu in FSX and moved it over to the destination airport to read the weather conditions. Instead of displaying the wx info that ASE was transmitting (verified by log flie) it showed surface wind direction/speed identical to my current aloft wind direction/speed which in this case was 180 degrees off from what my destination wind was predicted by ASE. I refreshed ASE and it again sent out correct wx info but FSX was adjusting the destination winds to conform to my current aloft wx. As I descended I monitored the destination ATIS and it kept changing as my aloft winds changed on descent but it was too late since ATC wouldn't change my landing runway. This was my second trial flgiht with this new build. On my first flight the weather at all altitudes was blowing from basically the same direction so I got the correct runway and by the time I was on final the weather was matching ASE but this time wind was reverse until below 6000 ft. Also on first flight pressure was 29.85 and that agreed on approach but this time RJBB was showing 30.07 in ASE but FSX would not allow pressure above 29.99. Even tho ASE was sending correct 30.07 FSX kept changing it back down to 29.99. I continued descent thinking that weather would eventually clock around but below 6000 feet FSX went to "Clear skies" and even attempts to refresh ASE would not change "clear sky" depiction in FSX. So much for IMC.I had to disconnect ASE and then FSX would accept my manual input of correct IMC weather and pressure. I am sorry this is so long-winded, Damian, but maybe the Beta testers were experiencing similar so I wanted to put in as much detail as I could remember to help you trouble shoot. I was reluctant to add such detail in my trouble ticket #AGY-825-68708 but this should help you coordinate the two. BTW, I am very excited about the accuracy of the aloft with DWC in the Beta and no more "INVALID METAR" msgs in simconnect log! I did try a flight with SP3 without the upgrade but actually enjoyed more success using STANDARD with suppression range of 100 and 12000 ft but point by point accuracy while aloft was not there. No stutters or frame rate problems, however, with the suppressions set. I started flight with DWC then restarted with STANDARD and again pressure was low so not sure if the pressure limit problem already existed in SP3 prior to the upgrade.

More insight into destination weather error: I flew the same flight Naha to Kansai starting from a saved enroute point. I again modified destination metar to make it extreme IMC as before. Again enroute everything was dead on in sync with what ASE was showing and likewise on descent. ATC announced the runway for landing opposite of what it should be so I tuned in ATIS for the destination and confirmed that visibility/temperature/wind being announced for the destination were EXACTLY the same conditions I was having aloft at that moment. As I descended the destination announcing weather kept changing to match the weather at my planes current position and by the time I was below 3000 feet on final it was conforming with ASE settings! I again set up the flight from the same aloft position and setup ASE as before. Once plane (NGX) initialized and I flew long enough to verify wx had initialized, I went to FSX map window and clicked on fixes and airports in about a 50 mile radius of the plane and sure enough the surface conditions at all the points mirrored exactly my aloft wx: 276 @ 82K / -53C and vis greater than 20sm!!! Apparently the fix to make the DWC mode work perfectly involved constantly setting global weather to match enroute wx. The ASE.log file, however, just shows the correct surface wx being sent to FSX! On the second flight when I was within 80K I pressed the "reset AI" button but knew it wouldn't work because the wind I was flying through was 180 degrees different from the correct surface wx. I am pleased to finally have ASE weather correct while enroute but...

Hello Craig, Answered in your support request, but for everyone here, this is exactly how DWC operates by design. Smooth Cloud Transitions or Standard depiction modes use station-based parameters which do not control the global/ambient conditions, which is what may be desired, but then your aloft wind depiction will be problematic.