Fixed tracking inconsistencies #187
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a clean branch of dev that uses all of the learnings from bug/tracking-inconsistencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Restructured tracking entirely, along with retuning movements due to tracking reading differently now. There is slight differences still in switching from trackers to no trackers, but I think that will always be the case to some extent. This was always able to be tuned away with offsets.
Motivation:
Trackers didn't work on beta 4 unless they were on the right side of the drive, and horizontal trackers didn't work at all
References (optional):
#177
Test Plan:
Ran through multiple autonomous routines, tested with and without trackers, to ensure consistent behavior across everything.