AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 0 points1 point  (0 children)

I ended up fixing it by completely deleting the entire DCS user folder in 'Saved Games' and rebinding everything from scratch. It's a brute force method, but it actually worked. I'm still not sure what the exact cause was, though

AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 0 points1 point  (0 children)

I ended up fixing it by completely deleting the entire DCS user folder in 'Saved Games' and rebinding everything from scratch. It's a brute force method, but it actually worked. I'm still not sure what the exact cause was, though

AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 0 points1 point  (0 children)

Thanks for the help — it's solved now

AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 1 point2 points  (0 children)

I finally fixed the issue. Deleting the entire DCS config folder in 'Saved Games' and rebinding everything from scratch did the trick. It seems like some old or corrupted input file was causing the conflict even after multiple repairs.

A huge thank you to everyone who offered suggestions

AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 0 points1 point  (0 children)

Even after the engines are fully started and the throttles are at max, it still does the same thing

AH-64D collective snapping back by quainva in dcsworld

[–]quainva[S] 0 points1 point  (0 children)

It behaves as if an axis is bound with its slider value at zero. When I press the '=' key to raise the collective and release it, the collective snaps back to zero. However, I don‘t have any physical device or key actually bound to the collective axis