Yeah I think this is an overall failure of the FSX weather system.  OPUS does similar things on my end. 

 

No ASN fixes this if you have the enhanced Overcast option on default is off, because there is a little performance penalty I flew the other day from KMCO to KDFW in that big storm they had, and had complete overcast skies, from Georgia to Dallas. Never seen that in FSX before.

 

Edit: Set historical time to 12/9/2013 at 4AM UTC, then fly from Atlanta to Dallas, to see it for yourself!!

Ah ok I got your point, thanks Devin and Andy

 

 

I also seem to be getting the importing of clouds in textured patterns and holes in the overcast layers.  See attached pic.  My cloud coverage density is also set to 8 and distance set to the default 90.  The pic was also taken over the snowstorms currently in the NE.

 

ASN and flying through clouds is amazing so hopefully I can get this issue fixed and it will be an insta-buy.

 

I didn't change any ASN settings from default.

 

Pls can you also comment on these square holes?

I already got them with AS2012 and now with ASN. Textures could not be the reason, because I tested different.

With FSGRW I never recognized these sharp borders in clouds.

I flew the other day from KMCO to KDFW in that big storm they had, and had complete overcast skies, from Georgia to Dallas. Never seen that in FSX before.

Ha! I did a 1500nm trip with the Turbine Duke too, solid undercast all the way. Long, boring flight! Nothing to see! Lol!

 

At least you know that you'll be getting in that soup at the end!!

 

 

Sent from my iPad using Tapatalk

Setting maximum cloud draw to 150 is also cool feature but beware - hardware has lot of work

Ha! I did a 1500nm trip with the Turbine Duke too, solid undercast all the way. Long, boring flight! Nothing to see! Lol!

 

At least you know that you'll be getting in that soup at the end!!

 

 

Sent from my iPad using Tapatalk

Yeah, got into the soup at 6000ft, all the way down to 300ft at touchdown. Forecasted visibility at the time 0.3sm at KDFW

Pls can you also comment on these square holes?

I already got them with AS2012 and now with ASN. Textures could not be the reason, because I tested different.

With FSGRW I never recognized these sharp borders in clouds.

Damian is addressing this over on the official HIFI forum:

 

http://www.hifitechinc.com/forums/showthread.php?1899-Cloud-Grid-Patterns-Sparse-Clouds

 

 

Sent from my iPad using Tapatalk

Same observation as Q_flyer. Started in believable foggy weather, climbed above clouds and voila; thick overcast turned into scattered and it was crystal clear visibility down from the cloud breaks.

Regarding visibility at 3 miles, in this case we don't generate a fog layer.  Its <3 miles that triggers this.  Note that visibility especially at 3 miles+ is not really an "overcast".  If you're looking for a "haze layer" you always have the option to enable it, by unchecking "disable haze layer".  Yes P3Dv2's volumetric fog is vast improvement of the haze layer technology in FSX and we're tuning ASN for P3Dv2 to use this approropriately.

 

As to the cloud depiction issue shown, that discussion is happening at our official forums.  We're trying to identify why this is happening and how to work around it.  So far we theorize that increasing the CDD range may resolve this.

 

I'd also like to suggest that any technical issues are brought to our forums, either here at AVSIM, our official forums, or via our support ticket system.  Thanks!

Where does ASN pull the METAR from?  I've been trying out a few airports and skyvector and ADDS have the METAR, but ASN seems to be a but behind.  How do I force it to manually update?

No ASN fixes this if you have the enhanced Overcast option on default is off, because there is a little performance penalty I flew the other day from KMCO to KDFW in that big storm they had, and had complete overcast skies, from Georgia to Dallas. Never seen that in FSX before.

 

Edit: Set historical time to 12/9/2013 at 4AM UTC, then fly from Atlanta to Dallas, to see it for yourself!!

 

I see this now and imho it should be selected by default to ON.  There's a huge difference on my end with this OFF.  In fact so huge I was just about to report the METAR and ASN being far off but now it's much better with ON.

 

I see this now and imho it should be selected by default to ON.  There's a huge difference on my end with this OFF.  In fact so huge I was just about to report the METAR and ASN being far off but now it's much better with ON.

It defaulted to off because in some circumstances it can double the amount of clouds drawn in the scene and that can have a big impact on performance. The manual discusses things like this in lots of detail.

Dave,

 

Set your max cloud draw distance higher than the 90 NM default in the settings, or alternately, turn down your max upper visibility to 90NM

 

 

Sent from my iPad using Tapatalk

 

Are you referring to the 'max upper visibility' setting in ASN or FSX?

 

I don't see that option in FSX, and I believe FS9 did have one, so I assume you are talking about ASN.  I do think that would fix the margin between the clouds and end of terrain but I still am not sure how it will fix the grid cloud pattern.  Hopefully Damian will come back with words of wisdom!

The data comes from our servers which has a slight delay as we collect and process the data from various sources.  You should set 5 minute update interval to increase the speed of the downloads.  Changing your update interval will also trigger a new download, but at 5 minutes there really is no need to force one, it will occur quickly enough.

 

Overcast enhancement on or off by default, we decided off late in the beta stage as it may be too much performance penalty for many systems.  As much as we try to make everything ideal for as many folks as possible with default options, there is too much variance in hardware (and user expectations) to really accomplish this perfectly.  Performance options are thus important to tune to get the best experience.  Please see the Performance Considerations chapter in the user guide for tips here.

It defaulted to off because in some circumstances it can double the amount of clouds drawn in the scene and that can have a big impact on performance. The manual discusses things like this in lots of detail.

 

I've not even touched the manual.  I want to see how this program performs "out of the box" so to speak.  So far I'm not seeing a huge reason to change from OPUS.  For example I seem to get massive stutters during Wx injection with ASN.  On the flip side, ASN seems to be more VAS-friendly than OPUS.  For a lot of the folks who used AS in the past - the $30 might be worth it.  But I've never owned any of their stuff so it'd cost me $50.  OPUS has camera module as well for 5 bucks less.  For me, I need more convincing from ASN to see if it's really worth it.  

 

Oddly enough I've really not touched the OPUS manual either.... apart from getting the exe to run as soon as FSX starts.

 

I've got plenty of time to test ASN though, we'll see!

Anyone know if the TRIAL has to start its activation in order to read the manual?  I'm seriously ill and confined to my bed which means I dont want to start my 7 days yet.  Would be nice to read up on it though.

Anyone know if the TRIAL has to start its activation in order to read the manual? I'm seriously ill and confined to my bed which means I dont want to start my 7 days yet. Would be nice to read up on it though.

Here:

 

http://nimbus.hifitechinc.com/ASNInfo/ASN_User_Guide.pdf

 

Hope you feel better.

 

 

Sent from my iPad using Tapatalk