Hi Jim and everyone, after some flights with the new build, (I'm on FSX) I am quite satisfied about the DWC, well done. The "prevent cloud redraws" option seems working good now, no more clouds when CAVOK or no clouds are reported (both values at 0 in settings). I still have a small bug with temperatures, instead of decreasing "linearly" with altitude, they change suddenly. At FL 90 I have +8, for example, it stays at +8 until FL120 when it drops to 0, then again and again until cruise. Same when descending. It seems it keeps the value listed on the "report" screen in ASA at the altitude specified until the next one kicks in suddenly. It should be smoother. That's what I found so far. I still have to check the wake turbulence if it has been fixed now. I'll report it.I tried the no-global ASA settings today, and it has improved as well. The depiction is more accurate, even though I didn't keep an eye on the program for the whole flight. What matters to me is departure and arrival, if in the middle the wx is not exact 100% I don't care that much :). First depiction, at departure, is accurate as it has always been. Now, first problem: how can I avoid this ugly effect? See imageThere's a line cutting the clouds! I think it has something to do with upper and lower visibility, hasn't it?Now, let's move to destination, ETNW, this was the metar: 20006KT 9999 FEW015 BKN096 17/15 Q1010. I took some pictures after landingGlobal settingDeeper, but sticking with no specific stationand more, specific stationAs you can see, all the stations have the same values: temperatures, QNH (wrong by 5 mb), winds, clouds and precipitation, though the METARs reported different things. If you want to check the active was 24th July 2009 at 07Z. It was raining in EDDV (depicted correctly) but not in in ETNW (ok here too). The cloud cover was different in the three stations, both in altitudes and oktas, here it shows the same one for all, instead. It even says "clear sky" in the global image, and in the specific station! Don't know what's wrong. The depicted wind was 169/6, instead of the reported 200/6. Looking around the surrounding stations, they ALL had the same values you see in this images.And this was the result (a part of it at least!):Quite strange, isn't it?Hope this was useful.CheersFede

Hi,1. Really not sure about that visibility layer cutting across the sky like that.2. For those bottom shots, don't rely on the FSX maps because there has always been updating issues and map depiction issues. Better to go to the ASA Map Screen and compare conditions.Thanks,

Thanks Jim, the map in ASA was showing coorectly. So you say to disregard the FS map? Ok, I thought that what was being depicted was being "written" inside fs wx engine, my mistake. There was a small .exe with FSUIPC some time ago, I believe it was still FS9, something like Weathercheck.exe, can't remember. I'll look for it, it tells you the wx FSUIPC detects. That should work, no?About that visibility issue, may it be that having two different maximum visibility settings for surface and upper altitudes causes this? It seems that the upper layer has a lower visibility than the lower one (in my settings the lower is set at 100 and the upper at 150), causing this evident cut.CheersFede

Hi, I made another attempt today, always without DWC. Apart from the QNH problem I reported in my other topic, I monitered closely the weather today. I still have the problem with winds at 0 during climb, they appear after a while in cruise (I used a jet today, not a prop like yesterday). I also used that wx tool (weather set) from FSUIPC to read the depicted weather, and here is what I've found. Departure ok, no problems. Arrival: checked the ASA ATIS wind calm, 7000, SCT4100, 36/23 Q0883 (this was the problem, ok). RC and weather-set reported 270/10 7000 SKC 31/26 Q1001 (yes, in this case, as the qnh is often wrong, it was good. You get the error with the first depiction, because the first depiction is correctly showing the QNH). That was the actual weather in fact. Because of the 7000m vis, I had that strange clouds' cut again ,less noticeable though, as the clouds were less dense than yesterday. But I saw it descending towards it, then the visibility fell to 7000 when I enterd the layer. Maybe adding some more layers of visibility would help this (if you have 50 miles at altitude and 10 at the surface, try adding 40 and 20 between, don't know).About winds aloft I saw there were two layers very close, one at 33927 feet 128/16 and another one at 33999 feet 147/22, and the winds were shifting aft and fore, left and right.Apart from these errors, let me say again, the depiction has improved, the engine seems working better. :)CheersFede

Hi,The only thing I can tell you is that we don't set visibilities in cloud layers, only near the ground and only to the altitude that FS allows. We set the actual visibility and FS controls the height.About your winds: in ASA ae winds zero or only in FS?Thanks,

No, ASA has winds in the report screen, it's just FS which doesn't apply them. It works this way usually. Start FS, clear wx via FSUIPC, launch ASA, connected, initial depiction message ( in. dep. can take from 20" to 3-5 minutes, depending how many stations are around), and then the wx is set. What I see in the report screen is just what I hear via RC ATIS, that's just perfect. Now, considering winds only, after I take off, winds disappear at about 3000-5000 feet, winds stay at 0 until I reach the TOC, then after a variable amount of time (from 5 to 15 minutes) boooom, winds appear. Luckily it's not a full motion sim! :)CheersFedeP.S. What about the temperature "stair-like" drop with DWC? I wrote it at the beginning of my first post, think you may have missed it.

Hi,Right now you are the only user reporting these issues. Yes, temps should gradually change.Please reset FSUIPC to Defalut Settings and Weather Settings Off.Thanks,