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
If multiple robots on the same alliance use AutoBuilder, the teams should be able to import both autonomous routines into one instance of the program, then tweak and re-export them if necessary.
At the very least, this would allow you to check for possible collisions, even if robots need to cross each other's paths. More advanced uses might even make it possible to do things like pass game objects from one robot to another.
The text was updated successfully, but these errors were encountered:
Sounds like a cool idea that could be really useful! This would require some pretty significant refactoring (as we need to load both configs at the same time and load up multiple autos at the same time), but I'll probably look into this more once the offseason hits!
If multiple robots on the same alliance use AutoBuilder, the teams should be able to import both autonomous routines into one instance of the program, then tweak and re-export them if necessary.
At the very least, this would allow you to check for possible collisions, even if robots need to cross each other's paths. More advanced uses might even make it possible to do things like pass game objects from one robot to another.
The text was updated successfully, but these errors were encountered: