Rotary knob axis only half range utilized

[F29Retaliator]

On rotary knobs like HUD Brightness only the second half on an axis is used. I tried multiple input device (Virpil CM2 throttle and Total Control MFBB). If an axis is mapped to the HUD Bribhtness knob axis the knob only starts turning when the knob or lever (both axis devices) has already been moved halfway. It makes no difference if the Axis Tune has "Slider" checked or not.

For example, DCS recognizes an axis as -100 to 100 and HUD Brightness only turns and does something in the range from 0 to 100. Now checking "Slider" in the "Tune Combo Axis" changes the input range to 0 to 100, which should match perfectly, but now the knob only turns from 50 to 100.

The same controls work as expected in other modules and I tried multiple input devices. This seems to be a bug with the F-15E?

Edited June 30, 2023 by F29Retaliator

[MAXsenna]

On 6/30/2023 at 2:18 PM, F29Retaliator said:

The same controls work as expected in other modules and I tried multiple input devices. This seems to be a bug with the F-15E?

Lots of other modules have the same issue with lighting rotaries, like the A-10C. So who knows if its a core issue the SDK. It will eventually be fixed I'm positive.

Cheers! 

[LeCuvier]

This is a very common issue when you create an axis using information from "clickabledata.lua", and in that case you can't complain because you have customized the function.
But if this happens on an axis in the stock file it's a bug and should be treated as such.

[imacken]

Yes, there are one or two modules that are like this with stock files and they have been reported some time ago to ED. Nothing has happened about it though.

A quick workaround for this issue is to put in custom curves like below.

[MAXsenna]

On 7/3/2023 at 11:22 PM, LeCuvier said:

This is a very common issue when you create an axis using information from "clickabledata.lua", and in that case you can't complain because you have customized the function.
But if this happens on an axis in the stock file it's a bug and should be treated as such.

That's interesting. Since you know how this works, could there be an update to the "clickabledata.lua" from ED in the future that would remedy this? 

Cheers! 

[LeCuvier]

3 hours ago, MAXsenna said:

That's interesting. Since you know how this works, could there be an update to the "clickabledata.lua" from ED in the future that would remedy this? 

Cheers! 

ED could certainly fix this. I suspect wold not be in "clickabledata.lua" but in the software that uses it.

[MAXsenna]

ED could certainly fix this. I suspect wold not be in "clickabledata.lua" but in the software that uses it.

So, how would I phrase this if I was to make a wish?

Sent from my MAR-LX1A using Tapatalk

[F29Retaliator]

On 7/2/2023 at 6:37 PM, MAXsenna said:

Lots of other modules have the same issue with lighting rotaries, like the A-10C. So who knows if its a core issue the SDK. It will eventually be fixed I'm positive.

Cheers! 

Thank you, I just got a Total Controls MFBB and thus never noticed this issue before.

 

On 7/3/2023 at 11:22 PM, LeCuvier said:

This is a very common issue when you create an axis using information from "clickabledata.lua", and in that case you can't complain because you have customized the function.
But if this happens on an axis in the stock file it's a bug and should be treated as such.

The file is indeed stock.

 

On 7/5/2023 at 10:02 AM, imacken said:

Yes, there are one or two modules that are like this with stock files and they have been reported some time ago to ED. Nothing has happened about it though.

A quick workaround for this issue is to put in custom curves like below.

Thank you very much, this workaround works just fine!