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

Better movement done detection #89

Open
orkaboy opened this issue Sep 13, 2023 · 0 comments
Open

Better movement done detection #89

orkaboy opened this issue Sep 13, 2023 · 0 comments
Assignees

Comments

@orkaboy
Copy link
Collaborator

orkaboy commented Sep 13, 2023

Right now, we are checking for if we've completed a stage of SeqMove and related functions by seeing if we are close to the target pos. This can sometime cause the TAS to double back if it overshoots the target (high movement speed or low TAS update framerate).

This could be solved by improving the target detection code:

  • Save the "origin" position (start of SeqMove or between steps)
  • Draw a line to the target position
  • Draw a perpendicular "finish line" at the target
  • Check if the TAS has crossed the finish line
@orkaboy orkaboy self-assigned this Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant