- In the case of little bit longer activities/courses the TracBack navigation does filter the vertices of the inverted activities/courses distroying their original shape, creating an unusable one.
- This enormous filtering doesn't happen if the navigation follows the original direction of the same activities/courses.
1) First screenshot: navigation following the original direction:
2) Second screenshot: navigation following the inverted direction (TracBack):
- I consider this a very annoying critical bug, since the TracBack does change the trajectory too much into a supersimplified one: even the "Off Course" alerts aren't reliable any more.
- This behaviour is not something related to the memory resources since the non-reveresed navigation doesn't filter the vertices of the activities/courses.
- Important: the length of the activity/course shouldn't be too long to provoke this annoying bug: a 16-17 km hiking recorded in "Smart" mode can already lead to this behaviour.
