Well, yes, I did buy a T.Flight Hotas X, and well, it's not awesome but it's ok. What bothers me the most is the way the ADCs are used:
There are 2 10 bit ADCs on X+Y, the rest is 8 bit ADCs. Each ADC gets stripped of 25% of its range on the controller. So you have a 12.5% deazone in the center and 6.25% deadzones at maximum. This results in 768 and 192 different values for the 10 and 8 bit ADCs.
I already wrote a small DirecInput->vJoy bridge that allows me to 'gamma' correct each axis (to have an exponential value distribution) and this already adds a lot to its sensitivity and usefulness. Nevertheless, the ADCs and the internal digital deadzones on throttle and rudder are quite annoying.
What I am thinking about now it to rip out the current controller and replace it by a Teensy 3.2 (~$20). The Teensy has 16 bit ADCs with 13 bits usable. Removing the least significant bit here to reduce the noise will still result in 12 bit resolution per axis.
The plan is now to write the firmware in a way, that it's possible to configure hardware deadzones and axis curves and have them persisted in the device.
So, the software part is not what bothers me, but I did not yet open the T.Flight to check how everything's wired and if I can get away by just replacing and rewiring the controller inside the stick unit.
My question now is, has anybody experience with replacing the controller (be it a Arduino/Teensy or a BU)?
Edit: Corrected some assumptions because of wrongly configured input ...