Does not enabling tracks cause issues with voyage recordings? Currently I’ve been unchecking the Enable Tracking on our fleet of boats to cut down on large numbers of tracks but was wondering if this would affect the voyage recordings. Running ECS +inland.
Tracks are completely independent of voyage recordings and one has no effect on the other.
The biggest problem with tracks happens when a large number of large tracks are recorded and kept in the current layer all the time. This not only clutters the screen but can slow the program down quite a bit and even cause stability issues.
Thanks for clarifying this for me, just recently learned how many tracks we had on our fleet computers and hope to avoid issues in the future ![]()
![]()
![]()
I’ve been very generous recording (and keeping) many high resolution tracks. Can you give some estimate of how much is too much? Is it the size of the .nob file generally, or specific to rendering tracks? If the latter, what magnitude of MBytes of total tracks (measured by moving a track to a new layer and checking the size of the file). And if the former, what magnitude of size of .nob?
thanks,
tom
Much of that is impossible to answer as it depends on too many things and your pain tolerance. If Coastal Explorer seems to be starting quickly and running just fine, then you are under your limit. If Coastal Explorer takes more than a couple of seconds to start or moving around the chart is sluggish, then you probably have too much data loaded.
Large tracks are certainly the leading cause of large .nob files (or cloud-synchronized layers), but some people also make large files my importing millions of marks or thousands of routes.
Personally, I like to have a layer for my current cruising plans and that layer will only have the routes, marks, and tracks that are either needed for those plans and stays pretty small. That would be the “current” layer most of the time. I also have layers that contain information I might want to reference no matter what my plans are now, and I keep those visible too. I also have layers for future plans and historic data but those are hidden so they don’t get loaded unless I need them.