Bitcraze Forums

Joysticks generally produce values in the range -1-1. Buttons such as those on a keyboard are (typically) a boolean affair (True/False). Using a button would therefore rely on having a way to map the digital nature of a button onto the analog nature of a joystick. There are a few solutions I can ima...

For thrust, it seems the PC client does the same mapping to a signed value as for the other axes, but then only considers positive numbers as valid. Indeed. The existing client assumes several things. One is that axis values will be in the range -1 to 1. Another is that the user will be using a con...

beat wrote: For thrust only the upper half of the stick range can be used.

Why's that?

rmirwin2 wrote:What types of scaling are you thinking about for the drop-down?!!

Currently there are three. The linear one and two others. They are implemented in terms of a function which curves an input value from the controller to an output, which is processed further and finally send to the UI and the radio.

I have been working on a variety of enhancements mostly in the form of more advanced config settings for axises. This allows enabling a deadband for each. I will make a pull request on the bitbucket repo when it is ready.

Hi folks, my copter has been experiencing a strange wobble during flight. This occurs along the axis containing motors 1 and 3. It manifests as a quick oscillation, that flattens out within a second or so. The severity of the oscillation varies, from barely noticeable to bad enough to cause a crash....

It is possible to do so, but adding that functionality would require a pretty significant refactor of the existing input handling code. Best to make a new issue unless you want to dig into the code yourself.

The u in u'sidewinder' indicates unicode, which would suggest a string encoding issue. Perhaps you can inspect the json conf file which corresponds to your controller and make sure there are no weird characters present. The default name of the USB device may have included some unicode trash which is...

I am not the original poster, merely trying to provide some corroborating evidence from my own spin issues.

I found a few things were causing my spin problems. One was crappy joysticks on the controller (Proex PS3 clone) I was using. I have switched to a different one (Logitech Dual Action) which has less jitter while the sticks are in their 'neutral' position. I am going to swap out the Proex sticks with...