I suspected a few days ago that display problems in Vws might be the cause for the mesomap problems I was having; per the problem report documented in the Ambient/Beta child thread.
What started presumption was the fact that the mesomap problems only occured after VWS was running. Clicking on ''update'' or deselecting a checkmrk in the map settings pane would temporarily fix it.
So, before the software developer recommended I not use every field in the mesomap settings setup, I made note of the GDI resources used by vws. Before I started discarding unuseful graphs/alfa numerics, I was at 513. I would decrease the number by 2 or 3, then wait an hr; as the mesomap problems would resurface w/in 10 min. Finally, I made it to 496 when the problems stopped; which ended up only being 2 graphs and 4 alfa numerics.
Today, I added my still from my webcam to the broadcast display, and the problems started again. The GDI resources were at 504. I removed a few more alfa's and the problem ceased.
Call it coincidence, but I don't think so.