Problems with assigning the throttle to my Thrustmaster Hotas throttle unit

[wernst]

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.

[Art-J]

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 - HOTAS Warthog {839B5A00-446A-11ea-8002-444553540000}.diff.lua

Edited July 17, 2024 by Art-J

[wernst]

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. 

[jackd]

Hi Art-J ..... An old post on the p51.

As for now i am trying to setup the p51 controls for my TM viper stick re-mounted on a TM AVA base.

I cannot get the elevator-ailleron trimming to work on my sticks nose up, down button assignment. Works from the keyboard however.

All my control mappings are from the days that i used the old magnetic base, there it worked for the trimming..

Are you saying that possible fixes my result only when i reinstall all my control mappings from the ground up, or can i just reset the p51 to default and edit it? thnks

[Art-J]

12 hours ago, jackd said:

Are you saying that possible fixes my result only when i reinstall all my control mappings from the ground up, or can i just reset the p51 to default and edit it? thnks

Hi Jackd. My post was related to "red dot" issue we suffered from back then, a different problem than yours right now, so let's forget about it.

Not sure if I understand you - by "all" do you mean all mappings for all aircraft? That would surely be an overkill, as from DCS point of view other aircraft diff.lua files have nothing to do with Mustang ones so they might as well not exist.

For a start I would indeed reset only Mustang to default (either by relevant button on options screen or simply deleting any diff.luas you created up till now). Or maybe go one step further - erase any default trim commands you can find (or maybe all joystick defaults if you plan to remap everything anyway?) reboot DCS, then try mapping your trims first before anthing else and briefly check if they work in free flight mission?

Mind you, I've never used TARGET gibberish or any 3rd party software for my Warthog, only mapping directly in DCS.