Controls Hotfix applied?

Hi,

Been away for a week but read about the controls bindings issue and the hotfix announced by nineline.

Just wanted to know if that hotfix has been applied yet as the update available to me is still showing as 2.5.3.22652

Thanks

no I think its for tommorow

Thanks for the response :thumbup:

Hotfix available yet?

Hi, I can’t find the Hotfix for the control bindings. Is it available yet?

Thanks in advance,

Cuco Negron

San Juan, PR

Thanks, Weaz3L.

Cuco Negron

San Juan, PR

Mind you - this new beta update cleared my custom mappings :)

Mind you - this new beta update cleared my custom mappings :)

And mine too .. my custom bindings lua file has been deleted by the hotfix, no longer exists in the folder.

Restoring my backed up file (alwys back it up before an update as ED suggest) had no effect, bindings still trashed. Looks like a complete manual re-set up of all my modules bindings AGAIN (takes hours for all the modules).

Well, this hotfix seems to have destroyed more than it fixed. After the fix, the MiG-29 suddenly had double mappings, missing mappings and a mix of default and custom mappings. So I guess we will have to go through the control mappings on every single plane after this fix... But the Hornet is fine it seems! It's just everything else that is messed up.

EDIT - it seems that only aircraft that have had their control mappings edited since the previous version, are affected by this.

True and valid

And mine too .. my custom bindings lua file has been deleted by the hotfix, no longer exists in the folder.

Restoring my backed up file (alwys back it up before an update as ED suggest) had no effect, bindings still trashed. Looks like a complete manual re-set up of all my modules bindings AGAIN (takes hours for all the modules).

Yes, luckily I just need Hornet and MiG-29 so a bit easier for me. Interestingly my hardware setup is a mixture of TM Warthog stick and Saitek X-55 Rhino throttle. Only Warthog was cleared, all mappings for X55 are fine... but yes, bringing the backup file has got no effect.

Everything seems to be fine here (Warthog), quickly checked F18, Harrier, Huey and Spit. But I haven´t touched anything since the last patch. Did you guys maybe change any mappings after the last patch messed it up?

Here too. Tried to reassign the key bindings after today's update but again -

some of the keyboard keys are greyed out without any chance to change them. Some of the TM1600 buttons doesn't work either.

Again!! After previous patch, all the controls broken and saving of them. Then we had to delete the user files, and reasign again. 2 hours reassigning.

And today patch AGAIN!!!

RIP my mappings...

The lua controls mapping file in Saved Games was deleted by the Hotfix. I copied it back in from a backup copy taken before the update, and took the LOAD option from the bindings screen. Ii appeared to have no effect, mappings still broken afterwards. I then loaded a different (older) backup from a different folder, and likewise that appeared to have no effect, the 'broken' bindings on the Settings/Controls page never changed after either load. Its as if the file was't being loaded.

Your mappings in Saved Games should have been preserved, if they are not being picked up, please let me know. Also try importing your saved game settings in and see if that works.

1. They didn't.

2. Doesn't work. I copied over the backup Input folder I had from before last Wednesday's patch, and that still doesn't put my old config back.

I also don't work with profiles: I just make manual changes to the input configurations.

So basically we need to re-map everything once again, after today's Hotfix.

Did you change anything before the hotfix to get your controls to work? Did you put different profiles in the module input folders or anything like that?

Of course I fixed the bindings broken after the original update last week since DCS WORLD was unflyable without. I backed up those redone control settings.

I had saved the fixed settings using the SAVE option on the control bindings screen into file

c:\users\<username>\Saved Games\DCS.openbeta\AAdif.lua.

All was then fine UNTIL the hotfix was applied today

After the hotfix that AAdif.lua no longer exists in the

c:\users\<username>\Saved Games\DCS.openbeta folder.

Copying a saved copy back in, then taking the LOAD option from the settings / controls screen to load the restored AAdif.lua appeared to have no effect whatsoever, controls remained unchanged and broken with many duplicated bindings, and some bindings against non-existent buttons (e.g. against the Rudder pedal device).

(I have a Thrustmaster HOTAS Warthog Stick and Throttle, and Thrustmaster pedals)

Controls werent in the correct folder in Saved Games/Open Beta/Config/Input/module name/?

Never seen anything to say thats where the file HAS to be … anyway if you have lots of modules are you suggesting you have to have a copy of the bindings in EVERY distinct module's folder?

Thats why mine are in the top level folder, because ALL the bindings for ALL the modules (I have many) are in the same diff.lua file, which is as far as I can see the default where selecting SAVE PROFILE puts them.

Regardless of that (which may explain why the file was deleted, though I didn't think you deleted anything from the saved games folders on updates) , when a file is specifically LOADED surely wherever it is loaded from the bindings should be imported. The LOAD PROFILE screen allows you to navigate to any folder to select the file.

But the LOAD seems to have no effect.

I specifically tried putting my AAdif.lua file in

Saved Games/Open Beta/Config/Input/joystick/FA-18C_hornet and the LOAD PROFILE still does not import the bindings, leaving the broken bindings unchanged.

Did you change anything before the hotfix to get your controls to work? Did you put different profiles in the module input folders or anything like that?

It seems you are correct, NineLine. Only aircraft that have had their control bindings edited since the previous version are affected by this. Also, some users seem to be reporting that their .lua files are missing, but that is not the case here.

.. oh thanks for looking at the problem .. I'm not ungrateful, just frustrated as are many others having to spend hours redoing my binds every update.