|
|
|
 *referring to Team Titanium's 2012 robot*
If only it could play guitar hero at the same time. sigh. - rsisk [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| *referring to Team Titanium's 2012 robot*
If only it could play guitar hero at the same time. sigh. - rsisk [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#7
18-02-2010, 06:46
|
|||
|
|||
|
Re: Camera Issues (we have tried practically everything!)
The default code is always looking for the target, in all modes. If you don't take advantage of this, you can turn off the button that enables the vision processing. You can also do this programmatically by turning off the global for different game modes, based on a button, etc.
If you want to process for targets, it definitely takes CPU, but shouldn't really affect the way the robot drives. Have you moved the vision code into teleop or something? Greg McKaskle 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 1726 - practically done! | TheOtherGuy | Robot Showcase | 10 | 19-02-2008 16:14 |
| Camera Oversaturation Issues? | 114Klutz | Programming | 11 | 19-04-2007 17:47 |
| Camera Issues | RedOctober45 | Programming | 5 | 08-02-2007 15:59 |
| Camera issues | Todd | Programming | 0 | 16-02-2005 19:06 |
Threaded Mode