Thank you for the wonderful program.
When trying to configure the axes in FoxVox VCC, I use the Thrustmaster TARGET HID combined device
FoxVox normally sees axes from 50 to 100. From 50 to 0 there is a sharp transition.
In Falcon BMS and other applications, these axes are displayed and work completely normally.
I would be grateful for any help.
From a hardware standpoint, nose down and nose up are on the same axis, just half on one side, half on the other. The FoxVox Parser plugin automatically uses the range 0-45% for one side, and 65-100% for the other by default, leaving a small 10% dead-band in the middle (It may actually be 20%...I don't recall offhand).
I'm not familiar with the TM TARGET HID device, but you can manually set the desired axis range within FoxVox by clicking the controller button next to it and setting whatever range you want it to be.
For this command on the VCC, although the input is analog, it is working as a discrete on/off switch - toggling on and off as the axis enters and leaves the specified range.
Thank you very much. That's what I did.
If you use just Warthog without TARGET profile in FoxVox the whole range of axes is available.
But if you use a profile that combines stick and throttle into one HID device, this is needed for fine tuning of stick sensitivity, FoxVox loses values between 0 and 50.
Input nose down and left aileron work at 0 which comes immediately after 50 with minimal movement of the stick.
Nose up and right aileron do not have such a problem since FoxVox has full sensitivity from 50 to 100.
P.S. Also on the MJOY 1.3 device FoxVox does not see the axes, it only sees the buttons.
Once again, thank you very much for your wonderful application
