Allow decimals in axis tuning

[virgo47]

Currently, we can only enter whole numbers (0-100) for the Deadzone, Saturation X/Y and Curvature - and also, only whole numbers are shown in In/Out fields. This is sometimes too coarse, for instance when matching the AB detent with Curvature (Deadzone/Saturation is probably OK, but there is no reason to not allow it there as well).

The internal values are decimals in 0-1.0 range, the precision can be much higher, it is probably not necessary to allow any/max number of decimals, but two - or even the single one - would add tons of precision to this kind of setup.

The same would be also great for user curves, of course:

Here the difference of 1 is often very coarse on some ends of the curve.

Currently we have to go to Lua files for any more precision. As you already work with decimals in the config info anyway (x100), it would be great if UI allows for decimals as well. Thanks.

[Insonia]

The DCS input functions and dxgui widget can handle the floats. just need turn the option acceptDecimalPoint to true. they just need to change the user-writeable box, it's simple; if they don't do it. you can do it yourself.

However, the in/out box its data from input:getinputactions(), which is a C++ function from input.dll. It always gives two digits, and was utilized in many parts of the game. These parts did not handle the roundups at all. changing a value format that used in many other parts of game, or add 2 exclusive C input functions just for those two boxes. i wonder will they consider it? probably not..

 

DCS is working on an AB hardware detent function. We don't know how long we have to wait. The userCurvatureSize only = 11 plus the S-curve is only default filter , the results were not very linear for the AB detent purposes. Since you are requesting a fine resolution settings. if you want precise AB detent via in game settings only. i may share my 2 cents.

it is slightly complicated to set up but it is very accurate, and very customizable.

The game input functions and profiles are capable of supporting much larger userCurvatureSizes for a very long time. Basically it just LUT(look up table) with no strict limits. it was only restricted by the UI. Ui can't handle more than 10 value points. But game can handle very large LUT. The user can generate a array in Excel via common functions. create multiple linear or non-linear stages. different curve shapes. then format into a table, import it to the lua.  I have tested settings with 100 points with no problems.

Spoiler

  

fig: big lut breaks the UIs but working

 

Edited January 5, 2024 by Insonia

[virgo47]

2 hours ago, Insonia said:

The DCS input functions and dxgui widget can handle the floats. just need turn the option acceptDecimalPoint to true. they just need to change the user-writeable box, it's simple; if they don't do it. you can do it yourself...

Man, thanks, I didn't expect this answer. As a programmer, I understood the first and second paragraphs, although googling for DCS acceptDecimalPoint didn't provide any handy pointers (yet) and grep showed the option is used in various places (dll/dlg file, nothing in Config though) but from the look at it not related to this dialog.

So my simple question - where exactly should I adjust this option?

In/Out using a function that many other things rely on... pitty, but I can understand it will not be changed, although currently the output is very coarse (and I suspect it is floored, but not sure about it).

The info about AB is a bit over my head (yet). I'm fine with current options, just not with the lack of precision.

And the info about curvature supporting more "rows" - that's cool. But that asks even more for more precision for the values as well. But as "more keys" are available in the config only, I can enter the precise values there. User curves are not my main concern (but it may be for others). But curvature with more precision would be cool.

Thanks for all the info... I'm going to further process it now.