I think I have found the problem.
1. The file shared in post #3 is a track, presumably lifted from some TET forum or website.
2. It loads straight into BaseCamp, no problem.
and looks pretty much the same as the version issued up by Pocket Earth on my iPad
3. I then asked BaseCamp, on my pretty powerful Mac, to convert the track to a route. This it struggled with, taking maybe five minutes to render up a route that is only a touch over 19 miles long.
4. On the face of it, what it offered up looked pretty similar
5. But on closer inspection, it was not smooth but rather composed of lots of jagged sections sort of cobbled together.
6. I realised that, as it’s a TET route it probably hacks off across fields on very small paths. These paths are not always shown on the Garmin detailed maps, so naturally the software has to do its best. The best it can do is straight lines, as there is no road or path for it to follow.
7. I then changed the BaseCamp map to Open Street Maps, which shows more little paths. I also changed the mode to ‘off road’ and forced a recalculation. This offered up a better version.
The conclusion I draw is that BaseCamp and its Garmin map is creating you a hybrid, somewhere between a conventional ‘on road’ (where the route follows known roads) and ‘off road’, where it marches off down unknown goat tracks.
Why did it crash your Nav VI?
I think the reason is that when a route is sent from BaseCamp into a Nav VI, it strips out some of the sub-detail. In other words it only sends just enough of the basics. This is not usually a problem, as the route usually follows known roads, shown on the device’s map.
When you summon up a route in the Nav VI, the device fills in the missing gaps as it were, matching the data to the roads it knows about. Big sections of the TET went along goat tracks, which the poor Nav VI had no idea were there. Its poor little brain fused with the effort and the device crashed. This is not surprising, as it took my powerful Mac about five minutes to do it.
There is a way around this, which would be to manually trace over the TET track and creat a fresh hybrid route, patching together smooth ‘on road’ with less smooth ‘off road’ (ie ‘direct’ routing) - I do this sometimes to force routes over a bridge, that BaseCamp does not think is passable - but that would be pretty dull task. You would probably also have to create it in Open Street Maps, routable and run the same maps on your Nav VI.
Me? I’d simply import the track into my Nav VI and use that, unconverted into a route. You’d not get turn instructions but so what?
Someone who does a lot of off-roading (Berin, maybe) may well have some better ideas.