Hi all, This is _not_ a bug report, nor perhaps FG specific, but rather a discussion of a joystick issue I see - now I have seen this, it is like when you get a little stone in your shoe, but no matter how much you look, you can't find the bugger - but because you know it's there, you can't stop thinking about it :-D
Plug in my USB Microsoft SideWinder Precision 2 Joystick: Mar 10 13:03:46 linuxamd kernel: input: Microsoft SideWinder Precision 2 Joystick as /class/input/input9 Mar 10 13:03:46 linuxamd kernel: input: USB HID v1.10 Joystick [Microsoft SideWinder Precision 2 Joystick] on usb-0000:00:07.3-2 Now, at this stage KDE joystick app reports everything is OK. All axes, buttons etc. are 100% accurate. Running jstest also reports the same. Now, either running fgfs or js_demo, the joystick works great. But after running either of these two apps, three joystick axes are now 'recalibrated': X, Y and Z axes at 'rest' are all set to 337 *exactly*. Running jstest also now reports X Y Z to be at 337: Axes: 0: 337 1: 337 2: 337 If I now unplug the joystick, and plug it in again, then ALL axes and controls are all perfect again (i.e. X Y Z at rest are 0). It was suggested maybe a hardware issue, but I don't think so as just X Y Z axes are set exactly to 337 after running FG. Reading plib code, I see that the kernel deadband zone is written out as plib uses it's own - could this cause this strange issue? BTW, it doesn't affect FG in anyway - '337' off 0 on a 65535 scale is unnoticeable in real life. Nick ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
