I updated to the new SP1 for Active Sky Evolution, and lately I've noticed plenty of hard horizons and unlimited visibility at cruise altitudes, and it won't return to normal hours on end, or flash in and out of correct visibility. Attached is a screenshot on a flight from MKJS to KPHL over the Atlantic Ocean near Florida in LevelD 767.I don't use Direct Wind Control and its associated visibility smoothing because I prefer the wind smoothing of FSUIPC 4.60 and I'm not fond of the limitations that come with choosing DWC in regards to inaccurate ATIS reports and AI contrails of a/c on the ground when I'm in cruise altitudes. But sure enough, if I enable DWC the problem goes away and things look beautiful! But again, i'd rather not use DWC.Is this a new problem with SP1? I don't remember seeing this before and if it did appear sporatically pre SP1, the visibility depiction would eventually return to normal. Maybe its happening because i'm over the ocean?Here are some of the relevant settings I have active and checked:Force Destination Wx ZoneForce High Priority ProcessesCreate Additional StationsEnhance Route CoverageDynamic Rate of Change 10%Fog Layer GenerationDisable Haze LayerMaximum Surface Visibility: 60 smMaximum Upper Visibility: 80 smI'll try some flights over land to see if this problem still occurs, but wanted to know if this is something I can fix.Thanks for your attention

Hi,Please try with Max. upper visibility set at 50. Then restart ASE and FS, if it is running when you make this change.

I'm getting this too, at lower turboprop cruise altitudes (FL200 or less).I'm alternately getting clear visibilty which causes that weird effect whereby there are no clouds in front of until you get there, if you know what I mean, and an alternating clear/reduced viz effect. I had it yesterday and reset my visibilities set at 59 lower & 69 upper. I have cloud draw set at 70 miles in FS. That hasn't helped, but I'll try 50 miles also.

I apologize, I think I found the culprit. I had the fsx weather change slider at zero, I moved it up to about 10-20% and that seemed to cure the problem. So, check your weather change sliders in both FSX and ASE and make sure they are not zero%.

Thanks for the feedback.I will try that although I have always had my Rate Of Change set to zero (as I believe is recommended) but have only experienced this problem recently.Note the clock on the panel.

Hi All,Just an FYI that the rate of change slider in ASE supercedes the slider in FSX. Really, there is no need to even move the slider in FSX because it changes back everytime you start FSX anyway.Not sure what is causing the clearing and then the re setting of the visibility.Anything else running besides FSX and ASE?

Nothing running as such. FSX SP2 under Vista 32 bit. Single monitor but a big one, 1920x1080, which is fairly new.PC is pretty ancient - Pentium Q9300 Quad @ 2.5 ghz, 4gb RAM, ATI Radeon 3870x2 (2x512mb).No online ATC, no networking of FS across more than one PC. AI is good old World of AI which works off straightforward traffic BGL's (unlike UT2 which sits outside FSX and pushes AI into FS as & when it feels like it). I'm using AlacrityPC to shutdown unwanted programs & services.Ultimate Terrain is installed, the aircraft is the PMDG Jetstream which is pretty stressful on the system being complex and VC only. I have a fully registered FSUIPC which is smoothing winds and turbulence but nothing else. I had it like that when I was primarily flying the MD-11 to remove fishtailing. I think you may now have a solution of your own but I didn't change it on the solid FS principle "if it ain't broke...." That would have been with ASA though rather than ASE, as I went over to the Jetstream at about the same time as ASE came out. If there are definitive rules how FSUIPC needs to be set up, I'd be glad to take advice.

Hi,See if adjusting the Dynamic Rate of change slider in ASE makes anything different for you.

Ths is a "Bump" really as this topic seems to have died a death.I've tried fiddling with every setting I can find, turning off updates altogether, different visibility ranges, turning all my other settings down to avoid stressing the CPU/video card etc etc but I'm still getting this problem on almost every flight and it's ruining the whole effect.I noticed yesterday that I was getting quite violent "turbulence" I suppose - quite sigificant yaw inputs - and this seemd immediately to trigger a shift to clear visibility which would then (if I was lucky) revert to restricted visibility within a few minutes. On other occasions, going back out to ASE and refreshing seems to do the trick. Does that mean anything to anyone? Is at an issue at lower altitudes, maybe at the transition from ASE's high altitude visbility setting to its low altitude one?Help.

Update - I've just found this post:http://forums1.avsim.net/index.php?showtopic=286003in which Jim gives his own ASE settings. I have copied them and will check again that everything in FSUIPC is "off".Jim's settings don't look hugely different to mine except that he has Maximum Surface Visibilty at 100 miles and greater than Maximum Upper Visibity, whereas mine was 39 miles only and the LOWER of the 2 settings.We'll see.................

Update - I've just found this post:http://forums1.avsim.net/index.php?showtopic=286003in which Jim gives his own ASE settings. I have copied them and will check again that everything in FSUIPC is "off".Jim's settings don't look hugely different to mine except that he has Maximum Surface Visibilty at 100 miles and greater than Maximum Upper Visibity, whereas mine was 39 miles only and the LOWER of the 2 settings.We'll see.................

I had this same problem and mentioned it on the HIFI website. My only solution to overcome this and some strange TAT behavior is to switch DWC on. Without it it is the same unlimited visibility for hours.Menno

Hi ailchim,Seeing that you have tried with updates turned off, it is not the updates that are triggering this.I wonder is your computer is being stressed to the point where FSX starts dropping graphics and the first thing FSX starts with are clouds. As an experiment, try with the simplest plane you have and see what happens.

I wondered that too but in truth I have the Jetstream working reasonably well, it's certainly quite flyable. My settings aren't max-ed by any means but I'm getting mid or high teen frames at the airport and between 20 and my current 25 FPS cap in the air - which is when the visibility problems arise. The change in visibility doesn't seem to coincide with changing views within the aircraft: in truth there are very few of those as there is only a VC, so it's loaded & that's that. Indeed, I can be looking down at a fixed angle into the cockpit with only a small bit of windscreen showing and yet I can see the visibility flip when there's nothing moving on my side of the panel. That doesn't prove anything but it's usually switching views of panning around the scenery which brings a problem if you are going to get one.The reason switching off the updates is that it appears - and I wouldn't put it more strongly than that - that every time I get a drop out, the ASE log shows it just to have completed the final stage of one - calculation of thermals insn't it? That doesn't seem to be the answer though.Having got your ASE settings, I'm going to start a new FSX.cfg to make sure I don't have conflicting tweaks. I'm also going to go back to using unlimited frames in the sim and fsx limiter to cap them externally. I got a smoother ride with that before I got carried away with someone's latest opinion on tweaks & settings!

As an afterthought, prior to the Jetstream, the only aircraft I've flown in the last couple of years are: the Digital Aviation Cheyenne using the VC only, the PMDG MD-11 (2D and VC) and the Realair Spitfire (VC only). None of those are what you might call undemanding and I have only started getting this problem recently.

OK, this is proceeding slowly due the difficulty of finding time to fly.I have FSX & graphics settings which work pretty well and I have the standard settings in ASE.The bottom line is that I have completed 4 flights using ASX and I get absolutely no problems at all at any stage.After 20 minutes with ASE with settings all completely unchanged I'm getting the same horrible snap to clear visibilty and the same problem occurs with ASA.Som as far as I'm concerned, it's in Hi-Fi's court and it's something that changed post ASX.