Whilst there is a certain amount of misunderstanding of the input options around, as a mechanical engineer by qualification, with strong interests in electronics and programming, and having designed and made my own hotas, I don't think I have too many misunderstandings of this topic.
Because I don't use filtering, and set all sensitivity sliders to 100%, with no dead band, I don't see the original problem shown by MikkOwl when flying in IL2. However, I could reproduce it by following MikkOwl's steps, but only in the axis configuration screen, and not in the cockpit.
The problem I mentioned regarding level flight might not be related to the one being discussed.
Quote:
Originally Posted by MikkOwl
Question to everyone (Letum, Julian, Aviar, KG26_Alpha etc): what version of the game do you have? As in, DVD, steam, direct2drive or whatever else is out there. Mine is the STEAM version.
|
Originally 4.07m from an Australian (same as European?) DVD, upgraded to 4.08m then 4.09m with UI 1.1 mod. My tests were done in modded 4.09.
Quote:
Originally Posted by MikkOwl
The 2-3% thing seems to be the way IL-2 reads the axes. I get it as well on devices that have 256 positions (while in-game throttle might have 120 positions).
|
Indeed. My best
guess is that IL2 checks for a match to certain percentages, whereas the controllers don't quite match the values that IL2 expects. For example, the controller might output 34.125%, whereas IL2 is looking for 34.000%, hence 34 is skipped. Just a guess, however.
Quote:
Originally Posted by MikkOwl
However, the hardware isn't faulty, for I have tried connecting and assigning all kinds of controllers to all kinds of functions in IL-2.
|
I definitely don't have a hardware fault either, I have never seen this in other games or setup screens, or DIView.