Jump to content

Problems with assigning the throttle to my Thrustmaster Hotas throttle unit


Go to solution Solved by Art-J,

Recommended Posts

Posted

I have problems with assigning the throttle via the control options axis setting. (Thrustmaster Hotas Warthog throttle unit). A red dot with an exclamation mark appears permanently next to the line for the throttle. After "clear" any setting the red dot remains.

I have now completely deleted the P-51 module and reinstalled it, at the same time deleting all config/input P-51 settings in the saved game folder a freh installation of the module. But still the red dot appears for the throttle axis when opening the control options page. After assigning ("add") throttle to the hotas unit ("joy-RZ") the throttle does not move neither in the cockpit nor on the control options page. But throttle movement is visible under "axis tuning".

In all other modules the throttle works as it should.
The red dot indicates an assignment conflict, but there is no other assignment "joy_RZ" for the hotas throttle unit on the control options page.

  • Solution
Posted (edited)

Since the problem is somehow default controls-related, have you tried clearing first ALL default throttle assignments, including keyboard ones? THEN restarting DCS and trying to reassign again? When I had similar problem with F-86 axes, I had to restart the game to make the changes "stick" and red marks disappear for good.

For reference, grab my diff.lua for warthog throttle, which works OK for me in 2.9.6. Obviously, it won't work on your PC because of USB ID, but maybe you'll be able to compare its lines with your old diff.lua. For the record I use left lever for throttle and right one for prop RPM. Also, screen shows how they look on my controls options page.

Throttle quadrant.jpg

Throttle - HOTAS Warthog {839B5A00-446A-11ea-8002-444553540000}.diff.luaFetching info...

Edited by Art-J
  • Like 1

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted

Thanks, Art-J, clearing the default throttle assignments did it. 

I mistakenly assumed that simply overwriting the assignment would work. Wrong, for some reason the default setting is more "dominant" in the background. Or, I neglected to restart DCS after clearing the category and making the new assignment. However, another DCS-ism (expression created by admiki) have been solved successfully. 

  • Like 2
  • Recently Browsing   0 members

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