Once the visibilty gets over 10 miles it's impossible to know what the visibilty should be using Metars. I take it as 20 so I can build up layers on top and I think looks better visually. Alas it's not a perfect solution.

This is sorta what I wondered. How does the default know it's more than 10 mi? Anyway, instead of 20 mi, perhaps shoot for 30 mi... I think that would be more accurate in most areas.

Flashing issues.Well, I'm struggling on this one. What we know so far.Will happen every 5 minutes as Metars are updated every 2 seconds.Once all Metars that need to be sent have gone then there won't be any more flashes till the next update.Doesn't flash on my near obsolete PCDoes on my high end I7 with bufferpools=0Does on other high end machines without.I don't have a solution or much ideas on this at the moment.If anyone can work out what the issue is I'd be gratefull!

No solution but I have a suggestion, can you set the updates to 15-20 minutes instead of 5? Weather doesnt usually change that fast so less frequent updates would be fine IMHO.

... something tells me that good ol davethewave is programming like a mad man as we speak... I have confidence he will get it worked out as far as the visability/flashing. :(

... something tells me that good ol davethewave is programming like a mad man as we speak... I have confidence he will get it worked out as far as the visability/flashing.

I leave the ' Limit visibility' unchecked and havent had any problem with that.

I haven't seen any flashes yet.Now I am worried,Cheers,MAB

Just a thought... why the every 2 seconds for the merars updates? Why not evry 15 min. like the default FSX does?Jim

I check for updates every 5 minutes and then inject any metars that have changed or that you might be within visual range in 5 minutes. If I made it 15 minutes I'd end up injecting more as you could fly further in that time. Once I have the Metars to inject these are injected 2.5 seconds apart which is a good compromise between getting them all in and having little impact on fsx performance.

I check for updates every 5 minutes and then inject any metars that have changed or that you might be within visual range in 5 minutes. If I made it 15 minutes I'd end up injecting more as you could fly further in that time. Once I have the Metars to inject these are injected 2.5 seconds apart which is a good compromise between getting them all in and having little impact on fsx performance.

Dave:I am with Open Clouds version 1.08 and still no flashes. With all the buttons on I do not have the hipper winds at high altitudes either.Cheers,MAB

What settings, if any, do we use in fsx weather menu or the display settings weather menue.will these have any affect on open clouds weather.

What settings, if any, do we use in fsx weather menu or the display settings weather menue.will these have any affect on open clouds weather.

There are 2 places where you set up weather in fsx. In display setting such as cloud draw distance etc. Open Clouds does not touch any of these.The 2nd place is where you choose the weather ie, theme, real weather etc. It does not matter what you put here, as soon as you push the Start button your weather theme changes to custom and open clouds injects its weather.Hope that helps

OK, spent some time looking at the flashing issue. No joy so far. I can think of a few work arounds but these will be compromises and I'd like a propper fix if possible.Anyway, spoke to the only person I know who knows about such things, and if you want to test his ideas please do and report back here.

Hi Dave,Flashing in FSX is due to the terrain/3D engine looking for a 'texture' that is not there.. this can happen with:Clouds,WaterTerrain.Each has its own solution. For Water: Change setting to WATER_EFFECTS=6For Terrain: Increase SWAP_WAIT_TIMEOUT to 30 or 40 *IF* set too low.For Clouds: Use the shader 3 mod with replaced cloud shaders.Ask your customers and try to determine WHO is having the problem and who don't.. most likely, those that are problem free are probably using the Shader 3.0 mod + WATER_EFFECTS=6If none of the above solve the problem let me know.. I have one more idea to try. ******* (Hey-sus)

OK, spent some time looking at the flashing issue. No joy so far. I can think of a few work arounds but these will be compromises and I'd like a propper fix if possible.Anyway, spoke to the only person I know who knows about such things, and if you want to test his ideas please do and report back here

Thanks for the info, but since I dont have the flashing issue with any other weather generator, I am not going to start 'tweaking' my system. It's not a 'showstopper' for me, as I just enable the weather, let it update, then turn it off. I enable/disable it again when 50-100 miles from destination to get current weather, so the flashing is minimized and the flight is fine. Open Clouds is still 100% better than the default FSX, hands down.

I've found a lot of the time you can stop the flashing by unchecking 'Generate high level clouds'.It doesn't always work though.

Here is a demo of the issue.

As you get higher the problem gets worse. So I went very high!In this test I am injecting a new Metar for one airport every time I press a key. You hear a ding and see a flash each time.In each test I hold down the key so I'm submitting 20 or so metars a second. It's like switching the lights on.As far as I'm aware, this issue effects REX and ASE so if we could find a fix a lot of people would benefit. (I suspect they are hiding this effect or restricting updates because of it)Also, I think this effect will be on every PC. I went back to my old pc, I hadn't noticed it as it's a smaller screen and didn't flash. If I looked up sure enough the flash is there.

BTW, I'm pretty sure this is an issue with the Simconnect PIPE getting hammered. FSDT had a similar issue with DFW with users seeing flashes.Check your messages, just sent you a PM for 'Plan B'

BTW, I'm pretty sure this is an issue with the Simconnect PIPE getting hammered. FSDT had a similar issue with DFW with users seeing flashes.Check your messages, just sent you a PM for 'Plan B'

It's not being hammered.making just one call to simconnect will cause a flash. (No other clients running or anything else)