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

Check this out:http://www.fsdreamteam.com/forum/index.php?topic=3433.0 8th post down.They were having a problem with the simconnect interface being hammered NOT by them... but another add-on. Anyway, this might/might not apply. The PM I sent you covers yet another approach.

Dave:I still have the problem with FSX going out of sync with the graphic card when I use the menu (Alt) during a flight. When I chose an option no problem, the option opens. It is when I come out the option and go back to the flight that my screen is all messed up. FSX is still running though, I can hear it in the background. Some time I can get the screen back and continue and finish the flight. I think Open Cloud should stop when an option on the menu is chosen then resume again after FSX does. It seems to happen while on the air only. For some reason I still do not have flashes.Cheers,MAB

They were having a problem with the simconnect interface being hammered NOT by them... but another add-on. Anyway, this might/might not apply. The PM I sent you covers yet another approach.

No, def do not have any sim connect clients installed. I never installed Level D's 767 for this very reason. (Don't go there!)Not sure this is a simconnect issue at all. The data goes in ok, its just not rendered. In my simple logic it's like fsx is drawing the sky before it's finished calculating that the sky isn't blue at altitude.Anyway, I don't think your other idea works either. (I had been looking at it to sort out violent wind changes.) I'll do some proper testing on this tomorrow just in case.I've got some ideas for work arounds, would rather get a propper fix though ;-)

Hi All,It's a standard SimConnect issue, reported to Microsoft many moons ago, that they were not able/willing to fix. It would require some re-programming of SimConnect, which is not going to happen. To confirm, anyone can write Pete D. or Damian C. and they will confirm the issue.

Hi All,It's a standard SimConnect issue, reported to Microsoft many moons ago, that they were not able/willing to fix. It would require some re-programming of SimConnect, which is not going to happen. To confirm, anyone can write Pete D. or Damian C. and they will confirm the issue.

Hi Jim,Thanks for the feedback. Saves me trying to find a fix that doesn't exist. I'm guessing that if you can spare time to help me out with advice your customers must get very well looked after!Anyway, I'd better go and start on a workaround.

So if it's a 'standard simconnect issue', why is it only happening with this? I use the default FSX 'real' weather as well as Active Sky and have never had the flashing problem.

The default weather doesn't use simconnect.

The default weather doesn't use simconnect.

And Active Sky lets you use 'Global Weather' instead of station based (via the DWC option) thats why you see no flashes.

Could you guys with the flashing stuff test if

TextureMaxLoad=30

changes things there?I remember getting rid of all those somehow flashing texture load corruptions since using this setting and I have ASE (without DWC) and Open Clouds running.In my opinion, this white flashing isn't Simconnect based but "just" a texture load operation and while the correct texture isn't processed, you see these white flashes. As clouds are textures to be loaded, that's what you experience.I could be wrong on this of course, but I don't experience those flashes here. Following Bojote's description about the TML value, it influences the loading of textures so give it a try.I have

TEXTURE_MAX_LOAD=1024

together with REX 1024 clouds.

I use 4096 with FEX clouds, and no plans to change it. Why would anyone want to lower that to 30?

I think you mix them both up.

TextureMaxLoad=30 

and

 TEXTURE_MAX_LOAD=1024 

aren't the same, the first one is in [Display], the second one in the [GRAPHICS] section. First one is the speed of the loading (somehow, Bojote can explain it better), the other one is the size of the textures.I suggested the first one just for testing purposes, to rule out the Simconnect based flashing and turn it into a texture-loading based one. Would be interesting to know your findings if you suffer from those flashes when the weather gets an update. :smile:If we follow Bojote's suggestions in using the TextureMaxLoad= setting, you could try e. g. a "6" or a "9" together with a current TEXTURE_MAX_LOAD= of 4096Both variables multiply each other and result in an amount of texture data and you have increased one by four, so we have to lower the other one but keep a divider of 3 there. Sounds like rocket science, I know, but as I mentioned, it would be interesting to know if the flashing is really Simconnect based or just depended of the texture loading speed. This speed can be influenced by the TextureMaxLoad (small fonts, no dashes, [Display] section) setting.

And if you will use B640 or B641 of ASE in Standard Mode you will see the flashing because that mode uses a standard simconnect connection.

Thanks for the heads up on the ASE (beta) update. Impressive changelog there and surely a thing to try.Looking at the various new options there I must admit that I seem to be getting to old for that complicated stuff and really appreciate the clearity Open Clouds offers here. If I just want to turn a little J3 Piper in the PNW area together with having some nice real time misty weather, it takes me two clicks and it's done while the other one asks me to decide about this and that.However, having both approaches available is luxury of course and who doesn't like luxury at all?

"Failed to load new weather. Will attempt to load old weather if possible." For some reason, this is the message I always receive when attempting to load weather with Open Clouds. It worked just fine until the other day, anyone have a clue what has gone wrong?

"Failed to load new weather. Will attempt to load old weather if possible." For some reason, this is the message I always receive when attempting to load weather with Open Clouds. It worked just fine until the other day, anyone have a clue what has gone wrong?

Same here. Must be a problem with the servers that Open Clouds connects to.