ChuckSK has worked on and improved the wind
"Particle" feature and it is much better, consuming less %memory, however the particles still fail about 3/4 of the way through when "playing" the grib. I have turned off everything except particles including the wind
arrows. About 3/4 of the way through the computer starts working hard, fans running, and memory use goes up to %13, then part of the display start to freeze and go white. This happens on almost any grib file you pick.
I have to use Task Manager to stop the process or select "Close the program" or "Wait" from the win prompt that comes up when I select upper Left X. Of course I am running it with opengl (using the an onboard NVIDIA Geforce GT540)
Now I have tried stepping through several grib files without using playback, and these grib files freeze almost in the same place, about 3/4 of the way through with the same symptoms.
It does the same things when running Opencpn
v4.1.718 without opengl.
Also I notice that when opening the grib plugin, the grib file will show at the end of the file (last frame) with the particles running. When I move the bar to the beginning it is ok the particles work. When I move the bar by hand drag past 3/4 point the grib freezes up again.
The freeze ups seem to be independent of what the other data settings are such as show wind arrows, etc. What I mean is the freezeups are being caused by the particles section of code, I am pretty sure.
I've tried about 5 gribs and it consistently freezes at 3/4.
I'd like to thank ChuckSK for working on this problem! I am sorry not to have gotten back sooner, but was on the water
PS: This is using the most recent OpenCPN
v4.1.718 freshly compiled and installed cleanly. With the previous v4.1.718 uninstalled first. There are no other plugins or devices (no gps
git merge upstream/master
git branch -va
* master 0154474 [ahead 95] Improve depth unit emboss font selection logic.