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
With the addition of the VisionPortal in FTC CenterStage, our team has noticed breaking changes in the robot controller's code while attempting to install the DepthAI library required for the OAK-1 Lite vision sensor. What: The robot controller application crashes when booted after installing the DepthAI library. Why: It appears that there is a conflict between OpenCV classes in the code of the robot controller and the code of the bytedeco/javacpp-presets repository. Building the project generates errors because of this issue. Attempting to exclude the library from the module causes crashes whenever the app is launched.
Hi there - if there's an incompatibility in the versions of OpenCV used, probably your best bet will be to exclude the entirety of the Vision module from the Robot Controller build.
And then deleting all the vision portal sample OpModes from the samples directory.
I do not think it would break the robot controller build but I'm not sure. The blocks module does depend on the vision module, but it's already been compiled into an artifact here so I think you could get away with it. Obviously trying to use vision portal from inside blocks would crash
As an aside, it may be worthwhile to confirm on the Q&A forum whether the OAK1 is legal for competition.
Hello there!
With the addition of the VisionPortal in FTC CenterStage, our team has noticed breaking changes in the robot controller's code while attempting to install the DepthAI library required for the OAK-1 Lite vision sensor.
What: The robot controller application crashes when booted after installing the DepthAI library.
Why: It appears that there is a conflict between OpenCV classes in the code of the robot controller and the code of the bytedeco/javacpp-presets repository. Building the project generates errors because of this issue. Attempting to exclude the library from the module causes crashes whenever the app is launched.
Attachments:
exclude
statement to observe duplicate classes errors)Additional information:
The text was updated successfully, but these errors were encountered: