You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 16, 2021. It is now read-only.
The current 1.2 SNAPSHOT version has all Vuforia targets removed except for the Relic Recovery ones. The ConceptVuforiaNavigation sample uses removed targets, and will probably crash if you try to use it with OpenFTC. It should be modified to track the Relic Recovery VuMarks instead.
The text was updated successfully, but these errors were encountered:
Ok so unfortunately this isn't a super simple task due to the way that the sample is set up. This is a sample for showing you how to use Vuforia to navigate your robot during auto. In this sample, Vuforia uses different targets (along with the hard-coded location of those targets on the field) to provide you with the absolute XY of your robot. That's great and all (and pretty cool too) however, converting it to use the VuMarks from this year isn't exactly going to work, since they're all the same image. How would Vuforia know if it was looking at the image on the far wall or the close wall? So what I think needs to be done here is to convert the sample to return XY relative to the picture, rather than absolute XY. Unfortunately, I don't really know much at all about Vuforia, so if someone who is more familiar with it than I am could take a look at this, that would be great.
# for freeto subscribe to this conversation on GitHub.
Already have an account?
#.
The current 1.2 SNAPSHOT version has all Vuforia targets removed except for the Relic Recovery ones. The ConceptVuforiaNavigation sample uses removed targets, and will probably crash if you try to use it with OpenFTC. It should be modified to track the Relic Recovery VuMarks instead.
The text was updated successfully, but these errors were encountered: