Since Sp2 I've noticed that ASE is overriding the upper vis set by FSUIPC and it's actually causing a much lower visibility at altitude so I'm flying in a bit of soup. I've tried both with and without the 'enable vis graduation and smoothing' option checked, as well as setting the ASE max and min vis limits to 200SM. Nothing gets rid of the low visability other than to close ASE and use FSUIPC to clear weather, which then re-instates my FSUIPC limits. Note we're not talking about zero vis at altitude, rather about 5-10SM less than I have set in FSUIPC.I don't actually want to use the ASE smoothing/graduation as I have them fine tuned to my liking through FSUIPC, and infact the ASE vis sliders seem to just not be working given that I've set them to 200 and still see the issue. Graduation ceiling is at the default 5000 but I've tried it all the way up to 25000. I had no problems in SP1 ASE but am only just noticing this with SP2 as I chose not to bother installing any of the beta builds.Any ideas?

Hi,Please post a shot at altitude and then include what the visibility should be limited to from FSUIPC.

OK here's my normal setting when FSUIPC is controlling the upper visibility limit set at 3000. At FL390 so well into the upper limit setting. (Ignore my ugly extended ground tiles. Got them set like that on purpose)And here is is with ASE open, vis graduation/smoothing unchecked and the maximum/minimum set to 200nm just incase. Not a massive difference but it's more hazy...about 5-10mn less viz than the one above. This is what I see with ASE regardless of what the visibility sliders are set to. Things look much worse from a cockpit perspective as the extra bit of haze causes my clouds to just appear as one big white mass with no definition, and also causes the horison to be sharp. A setting of 3000 via FSUIPC is my sweet spot and one which I need to keep. Surely FSUIPC should still override the ASE limits as it has done previously?

Hi,I am sure you'll agree that there is no difference between those pictures. I know things may be different in the plane.BTW there is no way that the visibility is set to 3000 in that first shot. It has got to be 50 or 60 miles in order to make out the ground layer tiles in the distance. A vis of 3000 is about 1/2 mile. So that tells me that your FSUIPC is not controlling visibility even without ASE running.

As I said the difference is subtle but there none the less. I can assure you that FSUIPC is controlling the viz in the first shot and it is set to 3000. If I close ASE in sim, I can sit and watch the visibility increase out to the FSUIPC limit! I believe that the sky textures will have an effect on the haze density so that may be why you see different results.Perhaps these will illustrate it better. Changed the FSUIPC upper limit from 3000 to 4000...proving that it is working. With ASE running, any changes to the FSUIPC upper limit has absolutely no effect. Once AES is closed the FSUIPC limits will again change, when I change them.With FSUIPC limitASE limit....remember these are set to 200nm within AES and this is still what is depicted.

OK after a bit more fiddling around, I can say that this only happens when the 'disable FS haze layer' is checked with ASE. If it's left unchecked, the FSUIPC upper limits are dominant.