solved HOTAS key bindings after reinstalling

[Tabasc0]

Hello dear pilots.

I have changed my motherboard. So I had to move DCS to another disk, then move it back to c : . I have launched DCS repair tool to make my DCS working again. Everything is ok except my HOTAS key bindings. I guess everything has moved due to changes to USB ports (new motherboard). Is it possible to bring all the bindings back ? I have moved the "Saved games/DCS" folder, i find all my *.dif.lua bindings but they are not assigned to the correct buttons.

Don't tell me I have to manually bind all the commands for all my modules. Please. 

[Flappie]

Hi. Windows has re-discovered your devices and it gave each of them a new codename, but your situation is not lost at all. Here you go:

0/ Backup your "C:\Users\...\Saved Games\DCS\Config\Input\" folder if you haven't already.

1/ Open your dcs.log file (from Saved Games/DCS.../Logs).

2/ Look for a section such as this one:

2023-02-28 20:21:34.435 INFO    VISUALIZER (Main): SceneManager initialization
2023-02-28 20:21:34.879 INFO    VISUALIZER (Main): cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2023-02-28 20:21:34.963 INFO    INPUT (Main): Device [Keyboard] created.
2023-02-28 20:21:35.029 INFO    INPUT (Main): Device [Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}] created.
2023-02-28 20:21:35.029 INFO    INPUT (Main): Joystick created[Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.036 INFO    INPUT (Main): Device [Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}] created.
2023-02-28 20:21:35.036 INFO    INPUT (Main): Joystick created[Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.048 INFO    INPUT (Main): Device [VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}] created.
2023-02-28 20:21:35.048 INFO    INPUT (Main): Joystick created[VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.049 INFO    INPUT (Main): Device [Mouse] created.

3/ Copy the codenames between braces (not the ones from my example of course, the ones from your file).

4/ Browse an aircraft "joystick" folder (e.g. "C:\Users\...\Saved Games\DCS\Config\Input\su-25T\joystick"). You'll see find some .diff.lua file(s) such as these:

You'll have to do the same for each aircraft and each device.

5/ If I'm not mistaken, you will see that the codenames have changed. All you have to do now is to rename these files so their name mention the new codenames (the ones from dcs.log). Be warned: each device has its own codename.

 

Please let us know if it works for you.

Edited May 15, 2023 by Flappie
typo

[Tabasc0]

Hello Flappie !

Many thanks for your answer. I understand the "codenames" idea. I have copied-pasted the codes of my HOTAS (Stick, Rudder pedals and Throttle) in a module folder. It seems that only the stick is correctly binded after that. Throttle and Rudder pedals are not.

Same for my second attempt in another module folder.

How can we explain this ?

[Flappie]

Please zip your "Input" folder along with your dcs.log file, then attach them here. I'll give it a try.

[Tabasc0]

Hello Flappie. 

You can find here the input folder, and the dcs.log file.

Many thanks in advance !

 

dcs.zip Input.zip

[Baldrick33]

13 hours ago, Tabasc0 said:

Hello Flappie !

Many thanks for your answer. I understand the "codenames" idea. I have copied-pasted the codes of my HOTAS (Stick, Rudder pedals and Throttle) in a module folder. It seems that only the stick is correctly binded after that. Throttle and Rudder pedals are not.

Same for my second attempt in another module folder.

How can we explain this ?

Which module did you copy and paste the controller ids and is that in the Input zip you posted?

Edit: Also are all functions of the stick mapped? - roll & pitch will probably work by default.

Edited March 3, 2023 by Baldrick33

[Tabasc0]

I've tried the bindings on the Viggen and the Harrier.

 

[Baldrick33]

18 minutes ago, Tabasc0 said:

I've tried the bindings on the Viggen and the Harrier.

 

Ok, just to be sure, you need to rename your existing files to the new names, e.g.

X56 H.O.T.A.S. Throttle {B80694C0-3ED4-11eb-8007-444553540000}.diff.lua should be renamed to :

Saitek Pro Flight X-56 Rhino Throttle {AB9C1880-B7B9-11ed-8002-444553540000}.diff.lua

In the Viggen folder I can see entries for both

I do find it strange the name of the device has changed as well as the id though? I guess that is due to new drivers with the motherboard swap?

Edited March 3, 2023 by Baldrick33

[Tabasc0]

Baldrick 33, you are my hero

After renaming the HOTAS in each folder of the modules, everything is ok.

Maybe it was due to the different driver. I was sure I 've downloaded it on the official website, as usual.

 

 

[Flappie]

Thanks for your feedback.

[Baldrick33]

When I had this happen I created a little batch file (.bat) to rename the folders and copied it into each config\input\[module name]\joystick folder and ran it from there.

Something like this:

rename "Arduino Micro {C7514800-588C-11ea-8001-444553540000}.diff.lua" "Arduino Micro {42D97A40-DDEC-11e9-8001-444553540000}.diff.lua"
rename "Arduino Micro {B98437C0-1FF5-11ea-8001-444553540000}.diff.lua" "Arduino Micro {C152B650-32EE-11ea-8001-444553540000}.diff.lua"

[AstonMartinDBS]

On 3/1/2023 at 11:34 PM, Flappie said:

0/ Backup your "C:\Users\...\Saved Games\DCS\Config\Input\" folder if you haven't already.

1/ Open your dcs.log file (from Saved Games/DCS.../Logs).

2/ Look for a section such as this one:

2023-02-28 20:21:34.435 INFO    VISUALIZER (Main): SceneManager initialization
2023-02-28 20:21:34.879 INFO    VISUALIZER (Main): cascade shadows init (preset:'default' quality:4 layers:4 size:4096)
2023-02-28 20:21:34.963 INFO    INPUT (Main): Device [Keyboard] created.
2023-02-28 20:21:35.029 INFO    INPUT (Main): Device [Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}] created.
2023-02-28 20:21:35.029 INFO    INPUT (Main): Joystick created[Joystick - HOTAS Warthog {91C40740-7531-11e7-8002-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.036 INFO    INPUT (Main): Device [Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}] created.
2023-02-28 20:21:35.036 INFO    INPUT (Main): Joystick created[Throttle - HOTAS Warthog {91C40740-7531-11e7-8001-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.048 INFO    INPUT (Main): Device [VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}] created.
2023-02-28 20:21:35.048 INFO    INPUT (Main): Joystick created[VKBsim Black Box  {75D8AB30-73DD-11e7-8001-444553540000}], ForceFeedBack: no
2023-02-28 20:21:35.049 INFO    INPUT (Main): Device [Mouse] created.

3/ Copy the codenames between braces (not the ones from my example of course, the ones from your file).

4/ Browse an aircraft "joystick" folder (e.g. "C:\Users\...\Saved Games\DCS\Config\Input\su-25T\joystick"). You'll see find some .diff.lua file(s) such as these:

You'll have to do the same for each aircraft and each device.

5/ If I'm not mistaken, you will see that the codenames have changed. All you have to do now is to rename these files so their name mention the new codenames (the ones from dcs.log). Be warned: each device has its own codename.

Since I'm getting a new PC in about a week, I'm glad I discovered this helpful thread. Thanks for sharing your solution @Flappie!

If you have defined modifiers for certain aircraft with an affected input device, you'll have to edit the specific "modifiers.lua" as well.

 

Here's an example of the content of this "modifiers.lua":

 

Edited May 15, 2023 by AstonMartinDBS

[Dr Zaius]

This thread just saved my life, thank you @Flappie

[jnr4817]

Is this still the only way to move bindings from one PC to another after moving all of the hotas and controllers over to new system?

[AstonMartinDBS]

AFAIK: yes.

[Baldrick33]

On 8/3/2024 at 1:18 AM, jnr4817 said:

Is this still the only way to move bindings from one PC to another after moving all of the hotas and controllers over to new system?

Although some investment in initial setup is required, Joystick Profiler is an excellent utility for managing controls across multiple aircraft. Changing a common control across all modules takes a couple of mouse clicks for example. It can also manage swapping devices and moving to a new PC where the device name changes.

https://github.com/Holdi601/JoystickProfiler