Minimise distance routing not working

Is popularity routing enabled or disabled?

I would expect switching off popularity route would allow it to compute a shorter route.

The other thing to check would be what the avoidance settings have been configured to under navigation in the profile.

It might be useful to see where you were routing from and to.

There can be issues with map data which can produce extra long routes. (I've seen an example of routing in the UK that didn't want to use a roundabout designated as a highway to cross the highway.)

One trick is to route to a closer point (somewhere in the middle) and then route from the midpoint to the end.

If you have a smartphone, you can use routing there to determine a reasonable midpoint to use on the Garmin.

There are numerous smartphone apps that do routing offline (you don't need internet/cell access).

Ideally, there would be one that could produce a FIT file and save it on the phone. Then, one could transfer that file to your Garmin. Unfortunately,  transferring files without internet access isn't exactly straight forward. It's easier to on Android. The problem is that there aren't any smartphone routing apps that produce FIT files.

I bought the 1040 to replace the 830, but I'm disappointed with the way it's routed. It's about maps, 1040 handles them differently than 830. I tried 6 different maps (including paid ToPo and free OSM options), and in all cases 1040 builds a route not the shortest route, often making extra kilometers on roads, avoiding a short road through forest. On 830, this problem was not on any cards. I combined route settings in all variants (popular routes, type of coverage, etc.). On many maps the 1040 spontaneously reloads when navigating. For example, I attached a photo, the route to 830 is almost straight, and 1040 builds on the roads and gives a big detour.

6039366 said:

I tried 6 different maps (including paid ToPo and free OSM options), and in all cases 1040 builds a route not the shortest route, often making extra kilometers on roads, avoiding a short road through forest.

Many of these (including the Garmin maps) are based on OSM. So, getting the same result for OSM maps would be expected.

6039366 said:

avoiding a short road through forest

This could be an issue with OSM data but, since the actual short road is a secret, I wouldn't be able to check.

What "Routing Mode" are you using? Maybe, try "Mixed Surface" or "Gravel".

dpawlyk said:

This could be an issue with OSM data but, since the actual short road is a secret, I wouldn't be able to check.

830 builds forest routes on the same maps without any problems. Experimentally, I found points on the map, on the roads, where 1040 slowed down and stopped when creating a route (a route crossing some areas). Again, the 1040 also resets when navigating on many third-party maps that the 830 had no problems with. In 1040, something has changed in the support of topographic maps, they are processed differently than in 830, for the worse.

dpawlyk said:

What "Routing Mode" are you using? Maybe, try "Mixed Surface" or "Gravel".

I tried absolutely all modes to build the same route (photo above). None were able to give a shortcut (including the "mountain bike" mode).

Where is the road? You could provide a Google map link.

dpawlyk said:

Where is the road? You could provide a Google map link.

This is not a road, but a point on the road that 1040 cannot overcome. And therefore builds a route around. It is observed only on some third-party topographic maps (ToPo V.3.0 2019/2020/2021).

6039366 said:

avoiding a short road through forest

You said it was avoiding a road.

6039366 said:

This is not a road, but a point on the road that 1040 cannot overcome. And therefore builds a route around.

So, there's no road? 

The routing on these devices (all of them) follow roads/paths that are on the map installed on the device. They won't route through "open spaces".