I don’t know about that. The complaints were made first of all for the XT1. I complained about the XT2 as soon as I bought one - it was the first thing I tested, I think. By then others in other forums had started raising the issue. I think they may be using the XT2 as a test bed for the solution rather than advertising the fact that they have possibly released their latest model with a known fault.FrankB wrote: Sun May 24, 2026 6:12 pm @jfheath Thanks for taking the time John!
Honoustly it would have surprised me if they would have fixed it for the XT2, but not for the XT3. Or at least sooner for the XT2 than the XT3. I did a test a few weeks ago with my XT3 and it definitely showed the same RUT behaviour as my XT did a few years ago. Applying the 'mImported fix' still works for the XT3. Note that there was no firmware update for the XT3 since I did the test.
Garmin have a history of fixing things in stages. Their solution to the issues with closest entry point I found to be very revealing. I doubt that they will offer releases for the XT1.
What amazes me is that they have not just put in an option in routing preferences to modify the mImported byte.
Eg when deviating a) recalculate to the next route point b) recalculate to the closest point on original route.
Simple.