WelshZeCorgi Posted June 24, 2022 Posted June 24, 2022 With the brunner, where the stick physically moves with the trim using the brunner program, prevents the altitude hold from engaging because the stick is too far forward or too far back, making it think I am physically putting back or forward stick pressure, even though it is simply trimmed.
RustBelt Posted June 24, 2022 Posted June 24, 2022 Means your Interpreter program is moving the stick more (or less) than it should move according to DCS. This is why Brunner needs to suck it up and make a proper DirectInput driver. You’ll need to adjust your FFB curves to match the input curve.
WelshZeCorgi Posted July 1, 2022 Author Posted July 1, 2022 On 6/24/2022 at 3:56 PM, RustBelt said: Means your Interpreter program is moving the stick more (or less) than it should move according to DCS. This is why Brunner needs to suck it up and make a proper DirectInput driver. You’ll need to adjust your FFB curves to match the input curve. Just the curve portion? I'm not sure I follow how to fix, just mess around with the curve until the AP engages level hold with no issues?
RustBelt Posted July 1, 2022 Posted July 1, 2022 (edited) No try and match the stick output curve to the stick input curve. I think You’re getting a mismatch between where DCS thinks the stick should be, and where Brunner is putting the stick. Like your stick is moving say 1.2x or 0.8 times the in game movement. Making the game think you’re producing an intentional input. It’s why I refuse to get a Brunner until they make it directly talk to DirectX. Too much fiddling. Edited July 1, 2022 by RustBelt
Recommended Posts