| 2007-06-20 15:18:11 |
Emmet Hikory |
libjsw: statusexplanation |
|
In order to actually fix this, the most useful information would be the section of /proc/bus/usb/devices for your joystick, the output of evtest for the affected device (this program is confusingly duplicated in dvb-utils and lineakd and poorly documented: I recommend installing dvb-utils for Ubuntu or Xubuntu and lineakd for Kubuntu), and a screenshot showing the issue.
On the other hand, unless you are playing Search & Rescue, you probably want to use the jscal program to calibrate your joystick, as jscalibrator only affects this single game. Also, please try to confirm your strange axis behaviour with js_demo from the flightgear package (note that there is a bug that requires you to unplug and reattach the joystick after using js_demo and before playing any games). If you can replicate it separately, it might be a problem with the input system, rather than specific to jscalibrator. |
|
| 2007-06-29 20:58:30 |
Emmet Hikory |
libjsw: statusexplanation |
In order to actually fix this, the most useful information would be the section of /proc/bus/usb/devices for your joystick, the output of evtest for the affected device (this program is confusingly duplicated in dvb-utils and lineakd and poorly documented: I recommend installing dvb-utils for Ubuntu or Xubuntu and lineakd for Kubuntu), and a screenshot showing the issue.
On the other hand, unless you are playing Search & Rescue, you probably want to use the jscal program to calibrate your joystick, as jscalibrator only affects this single game. Also, please try to confirm your strange axis behaviour with js_demo from the flightgear package (note that there is a bug that requires you to unplug and reattach the joystick after using js_demo and before playing any games). If you can replicate it separately, it might be a problem with the input system, rather than specific to jscalibrator. |
|
|
