. . .Clearing track on SOLIX does seem to help ...
Rickie
The SOLIX's Display-Code attempts to lessen the processor load by removing track-points from tracks when a track is displaying.
This causes two(2) problems:
Problem#1:Refer to the attached JPG:
The purple track is the true track imported via .HT file and displayed correctly
until a reboot.
The gold track is the same track imported via GPX file and Solix G1 & G2 units incorrectly display track-points.
Solix software code incorrectly removes "apex-track-points" resulting in a cutting-the-corner path. This could be dangerous.
Problem#2:Humminbird tracks can disappear when you zoom-in and the track-points are more than 200-300ft apart. This has existed since 1198/998 units. So you have a track with track-points at a distance apart to avoid "disappearing", but Solix units remove them, then they now will disappear.
Humminbird has the false idea to lessen the processor-load by removing track-points with the Solix Display-Code is foolish at best.
Solix's default track setting is to create a track-point by distance every 7ft. The default should be every 100 or 200 or 300ft.
Default=200ft means the unit will create a track-point every 200ft OR CHANGE OF DIRECTION.
So Humminbird current course is to create many track-points(processor-load), but remove track-points when displaying said track to reduce processor-load.
Stupid is as stupid does. . .