This version is an attempt to fix delays some people are experiencing. All i can suggest is give it a try. What it does is limit the number of NMEA sentences to 10 hz instead of allowing many sentences that may have accumulated due to windows being busy and then overloading AOG by making a zillion frame updates. They are simply dropped.
KML now has RecPath, Zoom buttons fixed. Rate Controller is now in support.
There is a new number on the screen. This shows how many times AOG ignores the incoming new NMEA sentence because it arrived less then 90 msec from the time the previous sentence arrives. 10 hz gps is 100 miliseconds a new one shows up, and 8 hz is 125 milliseconds a new one shows up.
If you are driving along, this number should NOT be changing. If you open a field, make a boundary, open Config, you will see the number count up - it is supposed to. But not when you are just driving along - one maybe once in a while ok - Windows is not a real time operating system.
What i think was happening is AOG was actually just getting behind and couldn’t catch up. v5 uses the new nmea sentence to trigger a frame update (redraw and do all the calcs) much better then v4 that checked often and if new data arrived would update. But if the system was busy drawing a border contour for example for a couple or more seconds there could be 20 or 30 sentences waiting to be processed so they would get get dumped in all at the same time. If your frame rate was fast enough (really good openGL card) it would survive, but many did not so they never caught up.
Think of it like a huge pile going thru a combine harvester - and we all know what happens. Think of this update as a pile eliminator. Now if only i could do this for a real combine…
Please let me know if this helps. I’m pretty sure you will.