Why even Go with the kinect?

[WizenedEE]

My guess is that our team will have an autonomous that stays where it is and shoots 2 balls, and our kinect strategy would be to dump balls on the bridges onto our side of the field. Although, it's entirely possible we could write an autonomous that dumps balls as well.

I think the main "reason" to use the kinect is that drivers are presumably better than sensors, you can make strategy changes on the fly, and it's easy to set up (or so I've heard)

[Nerfighter1629]

Instead of viewing it as a control method, we view it as a start/stop mechanism. Last year in autonomous, we had many problems with field calibration that lead to a couple big penalties from putting an ubertube in an opposing feeding lane. The way I look at it, the Kinect is a way to avoid that. You can program a simple command to realign the robot a tad to save the hybrid mode

[darkMatt3r]

To be honest, incorporating the kinect into our program will probably only happen in two ways:
1. Attach it to the robot to do some kind of vision tracking.
2. Use it to see an epic pose made by our human player so it starts the program.

I don't think we're going to bank on using the kinect and i really don't tink we're going to be using more than one motion if we go with the kinect.