joystick axis resolution in steps of 1%

[Bolelas]

Need some help: why can`t i get axis resolution in steps of 1%?
I have tryed diferent joysticks, calibrations, even connected hall sensor to leo bodnar board BU0836A,(that has 4096 steps of resolution), and still didnt got 100 steps of 1%, and i am not talking just throttle that goes to 110%, in prop pitch is the same, eg: 1, 2, 4, 5, 6, 8, 10, 11, 12, 14...
On mouse Z axis, that was traveling all the way from 2% in 2% i managed to improove a little by changing the conf. ini file where it says: mouse, Z axis sensivity, changed it from 1 to 0.5 and got better, but still not 100 steps.(tryed 4% and it traveled in steps of 11%)
Is any thing i can change in conf ini file, or some place else, to get steps of 1%?
Not that this is a big problem for me, but just curious if this can be solved. I fly on IL2 since 2006, have version 4.10.1, windows 7 (32 bit).

[Letum]

My MSSWFFB2 does 1% steps fine on a default install.
I'm sorry i can't help more.

[Bolelas]

Ok, thank you for your help, i gess i will try some more tests with leo bodnar board, this time with brand new potentiometers instead of magnetic hall sensors. If someone else has another advice or tip for me i would appreciate.
The "comunity" is a powerful helping tool.

Thank you Mr Letum.

[Bolelas]

Well, i did get 100 steps of 1% with leo bodnar 12 bit board (4098 points of resolution) in the prop pitch axis (0-100%), but wen i assign it to throttle (0-110%) i wasnt able to get 110 steps of 1 % any more...

With my joystick, that has only 256 points of resolution in each axis (8bit), i never got full resolution of 1 by 1% steps, not even in prop pitch axis. But with that much resolution i should be able to get it! Damn!

[MadBlaster]

In game under hardware setup/inut, do you have "100" in all 10 boxes, dead zone and filter =0 ?

Another thought; the game's coded axis range may not be the same as what you see in the in-game display for some controls. For example, prop pitch may be coded as range from -1 to 1, but the in game display shows it as 0 to 100%. So in this example, if you controller sends at .01 increments, a .02 change in the controller position would be needed to show up as 1% change on the in game display (e.g., prop pitch 99% to 100%).

[Bolelas]

Originally Posted by MadBlaster

In game under hardware setup/inut, do you have "100" in all 10 boxes, dead zone and filter =0 ?

Another thought; the game's coded axis range may not be the same as what you see in the in-game display for some controls. For example, prop pitch may be coded as range from -1 to 1, but the in game display shows it as 0 to 100%. So in this example, if you controller sends at .01 increments, a .02 change in the controller position would be needed to show up as 1% change on the in game display (e.g., prop pitch 99% to 100%).

Yes, all axis have no dead zone and all 100 in the 10 gaps. I even learned what ment, in the conf. ini file, the two numbers before the 10 gaps of the joy(means dead band) and the two after(filtering), and the one after filtering (simetric or not), so i tried a lot! you can also set an axis to have the last number of more that 100%, it will not apear in the game menu but you will see when you test the joy, that the green barr gets to the end before the red barr! Well, thanks for the help anyway, but as i said before, not a big deal, i am just curious.