Hi,Are you using any other textures then that may be over writing that file before you start FSX?

Hi,Are you using any other textures then that may be over writing that file before you start FSX?

Jim,I did have REX installed textures, but i removed them and reinstalled the original files. Then I took the cirrus overcast filed from ASE and copied it over to FSX textures. The above pictures are with the FSX original textures and the ase file copied over to the fsx textures. Would there be any other files/textures that may be overwriting it? My camera is charging....so i am waiting to do the video. Phil

Hi,No, I don't need that video, screenshots are good enough.Are you loading an ASE Snapshot?You did copy the correct file correct? Not the one with original in it's name.

Hi,No, I don't need that video, screenshots are good enough.Are you loading an ASE Snapshot?You did copy the correct file correct? Not the one with original in it's name.

Hey Jim,I copied the file from ASE named cirrus_overcast03 over to the FSX textures. I am not using an ase snapshot. I tried something different. On the weather options screen in fsx i changed it from user-defined to clear skies under the the weather themes. All the weather cleared. Then a couple seconds later that visibility layer comes back from ground up to 91800ft at 10miles visibility. No other weather showing. No clouds, no winds, etc. Just low visibility. Could there be a bad connection between ase and fsx?? With "enable visibility graduation and smoothing" it just seems to force this low visibility, no matter what the weather. When this is unchecked, the visibility will be correct up to about 3-5000ft, then from there would be unlimited. From the section 5000 and up you can adjust the visibility sliders to whatever visibility you want it and it will be depicted correctly. I am dumbfounded that it won't work correctly with "enable visibility graduation and smoothing" checked.Phil

Jim,Her are more pictures. The first one is at 30,000ft without "enable visibility graduation and smoothing" and you see the visibility sliders set and depicted correctly in fsx. Upper visibility was set at 90miles. The second picture is right after checking "enable visibility graduation and smoothing", you can see that the visibility went to 10miles at 30k. The pictures following the first two show what was depicted in FSX. Two show the visibility layers without "enable visibility graduation and smoothing" checked. you can see 2 layers..one up to 3100ft with 10 miles visibility and another from 3100 up to 91000 at unlimited visibility and visibility can be controlled via the visibility sliders in ASE. The final picture shows again what is depicted into FSX with "enable visibility graduation and smoothing" checked and not able to control through the visibility sliders in ASE.

Is there anyone out here experiencing what I am??? I am trying to figure this out and its driving me nuts! Thanks!!

Is there anyone out here experiencing what I am??? I am trying to figure this out and its driving me nuts! Thanks!!

Yes, I'm experience exactly the same as you have, maybe it's a error in the service pack, because i'm sure I didn't face this problem before I installed this servicepack.

Jim, So this is 2 more folks experiencing what I am, including the one over in the HIFI forums. You have told me in an email that no one else is experiencing this. Do we need more people to have this looked at more in detail???Thanks!Phil

Yes, I'm experience exactly the same as you have, maybe it's a error in the service pack, because i'm sure I didn't face this problem before I installed this servicepack.

Thank you for responding. The one great thing about ASE is the ability to smooth visibility. So why have this option if it can't be utilized. I would have stuck with ASX instead of spending the $50 to upgrade. Anyway, I am trying to work with Jim on this, but he has advised that no one else is experiencing this, so he and HIFI can't help. I need people who are having this issue to say something. This is the only way it will be heard by HIFI. Thanks! PhilJim, So this is 2 more folks experiencing what I am, including the one over in the HIFI forums. You have told me in an email that no one else is experiencing this. Do we need more people to have this looked at more in detail???Thanks!Phil

Hi,The 3-4 or four users who are experiencing this need to put as many details in an e-mail and send it to support(AT)hifisim.comPlease include FS version, ASE Build, FSUIPC version and registered or unregistered, ASE settings, flight plan details, FSUIPC settings if registered, and a description of the problem. Then those will get forwarded to the programming team to look at.

Hi,The 3-4 or four users who are experiencing this need to put as many details in an e-mail and send it to support(AT)hifisim.comPlease include FS version, ASE Build, FSUIPC version and registered or unregistered, ASE settings, flight plan details, FSUIPC settings if registered, and a description of the problem. Then those will get forwarded to the programming team to look at.

Thanks JIm. I will send info to them.

ok..so for anyone interested....I removed fsuipc and ase. I reinstalled ASE (not FSUIPC) and the visibility smoothing worked correctly and no more 5-10 mile visibility at cruise. I then reinstalled FSUIPC and the low visibility came back at cruise. There has got to be an issue with FSUIPC not liking what ASE is trying to do with the visibility. Can anyone having this low visibility issue at cruise try to remove FSUIPC and ASE, then reinstall ASE and check to see if you continue to have low visibility at cruise??thanks!Phil

ok..so for anyone interested....I removed fsuipc and ase. I reinstalled ASE (not FSUIPC) and the visibility smoothing worked correctly and no more 5-10 mile visibility at cruise. I then reinstalled FSUIPC and the low visibility came back at cruise. There has got to be an issue with FSUIPC not liking what ASE is trying to do with the visibility. Can anyone having this low visibility issue at cruise try to remove FSUIPC and ASE, then reinstall ASE and check to see if you continue to have low visibility at cruise??thanks!Phil

Ok...nevermind. After reinstalling ASE i installed FSUIPC. When I started ASE and changed my settings (checking dwc and enable visibility smoothing) and loaded FSX from ASE the visibility actually worked correctly. Now, when I save the settings it messes the depiction up and the low visbility comes back. I then uninstalled ASE and then reinstalled and started ASE and FSX through ASE and didn't save settings and visibility depicted correctly. So each time i start ASE it has to start with default settings. I don't know why this works!?

Thank you for responding. The one great thing about ASE is the ability to smooth visibility. So why have this option if it can't be utilized. I would have stuck with ASX instead of spending the $50 to upgrade. Anyway, I am trying to work with Jim on this, but he has advised that no one else is experiencing this, so he and HIFI can't help. I need people who are having this issue to say something. This is the only way it will be heard by HIFI. Thanks! PhilJim, So this is 2 more folks experiencing what I am, including the one over in the HIFI forums. You have told me in an email that no one else is experiencing this. Do we need more people to have this looked at more in detail???Thanks!Phil

I just experienced this today. Flying at FL370. It was a long flight and there was thick haze below me for much of the flight (until I got tired of it and downloaded the stock FSX real wx). I have the option checked to eliminate ground haze and this works well to eliminate the FSX ground haze issue. But the haze I expericenced today covered the ground up to my flight level. The only other wx program I'm using is RealSky Pro which mainly allows you to have different sky colors and tones for sunrise, sunset etc. and doesn't add clouds, winds, haze etc. I'm also using the registered version of FSUIPC.Bob

Hi,If this continues please put as many details in an e-mail and send it to support(AT)hifisim.comPlease include FS version, ASE Build, FSUIPC version and registered or unregistered, ASE settings, flight plan details, FSUIPC settings if registered, and a description of the problem. Then those will get forwarded to the programming team to look at.