[thefro526]

Originally Posted by AdamHeard

The point shifts with the amount of friction in the drive, but past 10 fps with 4 CIMs in drive as a single speed is a risky proposition. Many teams have achieved success with it, but it requires more skill to drive. Slowing down in code is a complete nonsolution and provides no more benefit than the driver just deflecting the joystick less. It doesn't add any resolution.

Any time we've experimented with slowing the drive down in code we've used scaling functions and never had issues, always felt like it drove the same, just slower. Actually helped our drivers utilize mid-range speed much better, for what it's worth.