Wayne,
We had several PM's discussing this Solix track bug prior to my opening post and recently another.
Your building tracks for 400 acre lakes so your tracks are not being scrubbed by a Solix because they are too small. So yeah, it works for you.
I respect you and all the help you've given to this HB forum, but please don't gaslight this thread with examples that can be build which are not relevant.
HB has a mess with Solix tracking.
First:A scrubbing bug which removes a apex-track-points which destroys track integrity. Current Track has the bug also, but because most users run Default Track Setting creating a track-point every 7 feet, then removing "apex-track-points" causing a very minimized loss of accuracy even after track-point scrubbing.
Second:Management decision to scrub track-point at all. One idiocy is creating 7-foot track-point intervals by default. Set the track-point distance at 100-300 foot intervals resulting in a new track-point every 100-300ft OR CHANGE IN DIRECTION. Less processor-load creating and no need to scrub. Win-Win. QED
HB Support first response was that the Solix Display-Code scrubbed track-points to reduce load on the hardware processor. HB's second response was the standard "not responsible for navigation use of their products". I've since requested and awaiting some technical responses as I search for a doable workaround. Still waiting for a Humminbird call-back, but really do not think it is coming.
I like my Humminbird's. I attempted to report and resolve with HB. I suggested solutions. But I do not work for HB, but with HB's responses, I'm warning HB users that Solix tracking might not be trustworthy for safety. Sorry HB.