Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Augmented reality maximum view distance #2765

Open
astewart77 opened this issue Jan 9, 2025 · 1 comment
Open

Augmented reality maximum view distance #2765

astewart77 opened this issue Jan 9, 2025 · 1 comment
Milestone

Comments

@astewart77
Copy link

Why is the maximum allowed only 100 feet? If I am following a backtrack, but not constantly watching my phone, it's easy to walk more than 100 feet past a turn. When I suspect I missed it and turn around, I can't see the path.

Also, when looking to cross a path from a gpx file with points more than 200 feet apart, I walked between two points without seeing the path when I crossed it. It took an arbitrary walk to the right or left at a probable intersection to pick up the path.

Is there a computational difficulty with a larger maximum?

Alan

@kylecorry31
Copy link
Owner

Hi, the maximum path view distance was set due to performance concerns based on real world testing. I can experiment with increasing it, with a warning that it may degrade performance.

Trail Sense uses the following algorithm, so it should be able to handle spaced out points in most cases:

  • Interpolate points on the path to obtain the desired spacing (this should handle spaced out paths)
  • Snap to the nearest point if within ~60 feet (accounts for most GPS drift)
  • Clip to the bounds
  • Render the points to the screen

@kylecorry31 kylecorry31 added this to the 6.8.0 milestone Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants