Jump to content

Recommended Posts

Posted

Hello there,

 

I'have being using these controllers for 5 years or so, and as you maybe already know, it goes all ***tty as time goes on. I managed to solve problems like buttons don't respond and things like that.

 

BUT, this one is driving me crazy. Problem is simple, when I move through throttle axis, dcs does not detect the real limit of the throttle, so when the throttle on my desk is at idle, I can see it is 25% on DCS axis display (ctrl+intro).

And the same happens when I push it to MAX on my desk, dcs shows 85%.

 

Happens to me in all planes I have, and I'm trying my best with logitech profiler, but nothing.

 

Anyone have the solution for this problem?

 

thank you in advance.

Posted

The controller Windows calibration should work as that resets the axis range that driver is then outputting to games.

 

So if you have a physical limitation on controller, the calibration reads the sensor output how far it can go on the full range of the axis theoretical and then maps the input to new output scale.

 

The calibration can't work if:

 

A) The game/software could override the HID driver (that is the OS operation)

B) the hardware would report a false reading from the sensor while calibration and then another for the game/software.

 

I have the same HOTAS and have needed to calibrate it once every new Windows installation and since then never had problems with it (after doing the modding to loosen the throttle cable and hot gluing the solderings in place from motion).

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

Posted

How did you manage to make HID driver override any other aplication?.

 

(about that "modding" you said, I had to place new wires to make it work hahaha.)

 

Thank you for your replay.

Posted

Well, nothing but the most stupid setting was wrong.

 

I'm not sure if it is the correct way to solve it. But I changed saturation on DCS control settings, and set it to it's maximum value (100). Works perfect now.

 

Thank you everyone.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...