On some input devices there can be less input buttons/keys/axes than there are functions that must be mapped. Because it's possible to use two input devices simultaneously this doesn't need to be a problem, but at present every function must be mapped to at least one input on each device. This means that if there aren't enough, one button must be mapped to multiple functions even if I didn't want to trigger some of those functions from that device at all.
In the case where the device only has a pair of input axes it really doesn't work, because STK won't allow remapping of functions away from the axes and so it's impossible to use the device without triggering things unintentionally.
Author: flherne
On some input devices there can be less input buttons/keys/axes than there are functions that must be mapped. Because it's possible to use two input devices simultaneously this doesn't need to be a problem, but at present every function must be mapped to at least one input on each device. This means that if there aren't enough, one button must be mapped to multiple functions even if I didn't want to trigger some of those functions from that device at all. In the case where the device only has a pair of input axes it really doesn't work, because STK won't allow remapping of functions away from the axes and so it's impossible to use the device without triggering things unintentionally.
Migrated-From: https://sourceforge.net/apps/trac/supertuxkart/ticket/1114