Klaus, I used to have a problem with how inputs are handled by neXt. I have this since always, and I never reported it because I found a workaround in the radio. And also I thought that if nobody else has a problem like this, then it is maybe something very specific to my PC or Windows installation.

But now I have a new laptop, fresh Windows, fresh neXt and same problem. So I thought I'll report it, because maybe other people get the same problem while trying next and end up just not buying this, and they will never report.

The hardware: FrSky Horus X10S, running latest OpenTX and FrSky XSR-SIM dongle. XSR-SIM is a joystick/gamepad in windows.

The problem is, that all channels in neXt are seen the following way (please note I describe values in -100...100 range)
- if channel value is 0, neXt sees it as -100
- if channel value is +100, neXt sees it as +100
- if channel value is +50, neXt sees it as 0
- if channel value is anything negative, neXt sees it as +100

Or in other words, if we make a graph it looks like this:



where horizontal axis is what radio is sending, and vertical axis is what neXt makes out of it.

The values in all other sims I have, and also in Windows (joystick settings) are all OK. So I don't think there is anything wrong with radio setup or dongle.

I workarounded the problem by making radio only send values in 0..+100 range for full stick travel, so it's only using half of the channel, and recalibrated neXt. It kind of works, I just get maybe less resolution, which is not a big problem, and have to keep additional mixes in the radio and have to toggle a switch anytime I use neXt.

If it is not clear, I can try to make a video. I wanted to report first, because maybe the problem is known, and making a vid is some time..|addpics|rer-3-8601.jpg-invaddpicsinvv|/addpics|

Ah ok. But why is then everything fine if I check channels in Windows? I mean in this window:
|addpics|rer-4-1cb7.png-invaddpicsinvv|/addpics|