Interesting. I must say that I've never noticed this one, probably because I've never found a reason to use deadzone on any of my controller axes. I DO set curves for all my axes that are controlled by potentiometers - pitch, yaw, roll, throttle, trim up/down, trim left/right - using the IL2Joy utility; but,as stated, no deadzone, and no filtering.
I seem to recall, from years ago, that it was explained that these latter functions were intended for older devices that jittered around their centrepoints. It may be that you have no need of these filters in the first place. Also, it all seems to be rather a 'static' interpretation of input. When I'm flying a plane I find myself constantly trimming anyway, either with the stick and pedals or the trim wheels - so it doesn't much matter whether the centres are creeping or not, so long as the instruments are centred in the cockpit.
I can see this might cause problems when using the Autopilot function offline, or Level Stabiliser flying a bomber, but it's still adjustable in the latter case using trim. I suggest that leaving deadzones and filters alone might help
brando
__________________
Another home-built rig:
AMD FX 8350, liquid-cooled. Asus Sabretooth 990FX Rev 2.0 , 16 GB Mushkin Redline (DDR3-PC12800), Enermax 1000W PSU, MSI R9-280X 3GB GDDR5
2 X 128GB OCZ Vertex SSD, 1 x64GB Corsair SSD, 1x 500GB WD HDD.
CH Franken-Tripehound stick and throttle merged, CH Pro pedals. TrackIR 5 and Pro-clip. Windows 7 64bit Home Premium.
|