Assign axis

[peirof]

Hi,

 

i am redoing my controller profile, but  i have a dude.

 

I am usign Hotas Warthog, and i d'like to assig, 2 axis of throttle (in manual called SLEW CONTROL+PUSH) , identified in DCS as Joy_X and Joy_X to 

 

But in DCS Options-->Controls, when i try to asign those axis to this control, the box apear darker, and cant select and it does not let me select any axis, neither the throttle nor the control ... it is only in a light color, the mouse column, which IF I can assign ... But I don't want that.

I have seen several videos on Youtube, and in all of them they can assign those axes to the TDC controller (Target Designator Controller), in the videos I have seen, it is not in clearer, it allows the assignment of those axes (Those of the Throttle mouse from Hotas Warthog) to TDC.

Does anyone have any idea why it may be?

 

[peirof]

Hi,

 

I'm not really sure yet ...

Until now, I did not assign the actions to the command using the T.A.R.G.E.T. software, but I have started using it.

It seems that by creating a "profile" in the TARGET software, you link both the Joystick and the Throttle into a new "virtual" device, which is added to the DCS device column.

By doing so, you can assign the Throttle's "Mouse" axes to the TDC.

 

 

 

 

[peirof]

NO.....

 

something its wrong!!!!!!!!!!

 

every time the TARGET software stops, which is sure every time you stop the PC, and reload it. It seems that DCS assigns a "virtual" device (Joystick and Throttle) but WITH A DIFFERENT ID.

In this way, all key mapping is lost ...

What am I doing wrong?
What is the best way to assign the Hotas Warthog?

[Flappie]

Hi. First of all, you don't need to reassign your bindings when that happens. All you need to do is renaming your Warthog .diff.lua files according to the ne GUIDs. Here's an example:

 

In "C:\Users\username\Saved Games\DCS...\Config\Input\aircraft_name\joystick", I have these two Warthog files:

• Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-774553540000}.diff.lua
• Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-774553540000}.diff.lua

What you see between curly braces is the GUID of each peripheral. This GUID may change sometimes for reasons unknown to me (it never happened to me - maybe because I've never used T.A.R.G.E.T. ?).

 

When this happens, open your dcs.log file ( Saved Games\DCS..._Logs\dcs.log - may appear as "dcs" ), retrieve the new GUIDs in this part of the log:

 

2021-07-04 07:28:11.920 INFO    VISUALIZER: cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2021-07-04 07:28:12.052 INFO    INPUT: Device [Keyboard] created.
2021-07-04 07:28:12.087 INFO    INPUT: Device [Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}] created.
2021-07-04 07:28:12.087 INFO    INPUT: Joystick created[Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}], ForceFeedBack: no
2021-07-04 07:28:12.119 INFO    INPUT: Device [Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}] created.
2021-07-04 07:28:12.119 INFO    INPUT: Joystick created[Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}], ForceFeedBack: no
2021-07-04 07:28:12.120 INFO    INPUT: Device [VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}] created.
2021-07-04 07:28:12.120 INFO    INPUT: Joystick created[VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}], ForceFeedBack: no
2021-07-04 07:28:12.130 INFO    INPUT: Device [Mouse] created.

 

Then rename all the Warhog .diff.lua files you can find under "C:\Users\username\Saved Games\DCS...\Config\Input\" accordingly.

 

I can't help you with your T.A.R.G.E.T. issue, because I have no idea how it works.

[peirof]

Thank you,

I write it down, but for now I'm sticking with the RS Mapper mapping software, it's flexible and transparent enough for the mappings I want to do. Pulsations when you stop pressing a button ...