Brunner FFB stick incompatible with F14 autopilot.

[WelshZeCorgi]

I have the brunner ffb physically move when trimming, as I find it easier to trim this way. I also think the stick physically moving when trimming is how it actually works for the F14? (not sure).

But due to this, the autopilot will not engage properly, as the autopilot in the F14 seems to run on the premise that the stick is centered even when trimmed. So Altitude hold will not engage, because when the 14 is properly trimmed the ffb stick is very far from center. 

The basic autopilot functions also do not work properly as it never really seems to engage, as the 14 in dcs only engages the autopilot when again, the stick is centered. And when trimmed, the stick is not centered on the brunner. 

Is there a work around because the option for ffb stick in the special options does not seem to change anything, regardless of whether it is checked or not. 

This option does seem to work on the sidewinder, according to hoggit replies, but they disable a setting on the stick called "center spring" plus some tape to cover a hand sensor so that you can take your hand off the stick without disengaging some function. 

Edited December 21, 2022 by WelshZeCorgi

[RustBelt]

Reason is, the sidewinder is talking directly through DirectX and the Brunner is sneaking data out the back door. 
 

I don’t know why Brunner refuses to cobble together a DirectX interface for their driver software, probably some kind of licensing or old documentation or something, who knows, or they just don’t care. For the price, they could have at least tried. But, their primary customer uses non DirectX for control loading so they probably don’t see the point.
 

A directX to Brunner translator would be a valuable utility for anyone who can actually code in grownup, not python.