leofaye01 Posted November 16, 2019 Share Posted November 16, 2019 (edited) Hello! I am a new user who's been casually using DCS A10C for a few years now. This is my first time reporting a bug. I hope I am providing enough info. I searched and could not find it under either DCS or A10 bugs. This is not a binding issue, axis issue, deadzone or curvature. I believe this to be a game-controller issue. Joystick1: Logitech X-56 flight control. JOystick2: Logitech X-56 throttle. (1) Logitech's Windows7-based configuration software is set to 0% curvature and 0% deadzone. (2) Logitech's own Window-based "X56 H.O.T.A.S" reports smooth responses across X and Y axis. (3) DCS's A-10C (Real) axis are set to 0% curvature and 0% deadzone for both X and Y. (4) DCS reports the same smoothness and response within the axis configuration page. DCS fails to translate movement into in-game flight stick. For example, attempting a right roll I pull right 5% of the mechanical range of motion BUT the airplane fails to register the movement (even though the DCS configuration page is registering the move and should be deflecting the ailerons). Instead, no deflection of the flight surfaces occurs. Until... I pull the joystick further. By then, at, for example, 15% (arbitrary), the A10C's stick SNAPS to that 15% range and abruptly rolls right. Same with left, up and down. The keyboard right arrow key is able to smoothly deflect the ailerons between 0-15%-- but the joystick causes a snap deflecting from all controls. Once the "deadlock" has been beaten, a smooth translation occurs between +/- 15% all the way through 100%. Using a curvature does not address the issue. Smooth rolls and pitches and impossible to do in flight as a result. The A-10C snaps left/right up/down. Please let me know if a log is needed. I'll try to provide whatever you need. Edited November 16, 2019 by leofaye01 Link to comment Share on other sites More sharing options...
Yurgon Posted November 17, 2019 Share Posted November 17, 2019 That is a very good problem description. I've been pondering for 5 minutes what might cause this, but I have almost no idea. It sounds a little bit like fighting the auopilot, but then the cursor keys should show the same behavior. I would try the following: Make sure that "Force Feedback" is not checked in the game's options. Rename your Saved Games\DCS folder and check if the problem is still there (the folder will be newly created next time DCS starts). In any case, you can later remove the new folder and rename yours back in order to restore all settings. If that doesn't fix anything, I'd try DCS repair (Windows Start -> All Programs -> Eagle Dynamics -> DCS World -> Repair DCS World) If the problem persists, I'd try to uninstall and reinstall DCS. But first and foremost I hope someone has a better idea. ;) Link to comment Share on other sites More sharing options...
leofaye01 Posted November 17, 2019 Author Share Posted November 17, 2019 Thank you! I'll try that and be back :) Link to comment Share on other sites More sharing options...
leofaye01 Posted November 17, 2019 Author Share Posted November 17, 2019 DCS just updated itself. I belive from 2.5.5.35461 to 2.5.5.39384 The problem has been resolved. Perhaps an admin can pitch in on whether the latest update contained some corrections to the controller logic. Thanks for heling out Yurgon! Link to comment Share on other sites More sharing options...
Yurgon Posted November 17, 2019 Share Posted November 17, 2019 Excellent, glad it's now sorted. :thumbup: I think I flew the A-10 in most of the recent DCS versions and never noticed this problem. In any case, let's hope it'll not come back and you can now enjoy the game again. :) Link to comment Share on other sites More sharing options...
Recommended Posts