Unfortunately correct function of ASN needs this to max out to 8 (otherwise problems with precip sync and/or cloud visibility reduction may come up). Nevertheless, there is a misunderstanding about what this option actually does. This has already been discussed, but anyway let me start over: Many users seem to believe that this way they will make overcast depiction more "solid" and with less gaps/holes. Still however, this is not true and the main reason is that all this option does is to adjust the coverage of a cloud.
For example let's call "x" the initial coverage (x/8) that ASN (or whatever engine or manual fsx weather) wants a cloud to have. The "final" coverage (the one used to select the actual cloud model to be drawn) will be calculated as:
finalCoverage = x*CloudDensity/8 and if this is > 8, it returns 8.
So in effect by setting CloudDensity to 10, all you do is:
-if x=8 => finalCoverage = 8*10/8 = 10 and since it's > 8 => finalCoverage = 8
-if x=7 => finalCoverage = 7*10/8 = 8.75 and since it's > 8 => finalCoverage = 8
-if x=6 => finalCoverage = 6*10/8 = 7.5 that rounded becomes 8
etc etc
So, with this option set to > 8 and if already ASN considers that overcast conditions should be in place (8/8), then you'll notice no change. All it does is to force overcast conditions when broken clouds should be depicted. If all you want to see is overcast conditions then you can either use ASN manual weather (or don't use a weather engine at all and set the fsx weather conditions manually).
To prove that what I say is correct do a simple experiment: Disable ASN (in dll.xml), set the cloud density in fsx.cfg to 100 (yes one hundred!) and then start up fsx and load the "fair" weather theme. I am looking forward to your results
