Bindings gone in this update 2.5.4 - again?

It's happened again.

My bindings on the planes I've tried so far - F-5E, Spitfire, K4 - are all missing.

Gone back to the default. Why does this happen over and over again?

I noticed a few things as well. I removed/adjusted as needed (within the Bug)

It only seems to be some, not all this time.

System is working that your personal .diff.lua file defines differences between default .lua control file and end result. What happens in patch where default .lua file is changed that .diff.lua is incompatible as a change layer because it is designed for a different version.

If .diff.lua doesn't combine well with new .lua foundation then it is discarded and there is no different from default applied.

System is working that your personal .diff.lua file defines differences between default .lua control file and end result. What happens in patch where default .lua file is changed that .diff.lua is incompatible as a change layer because it is designed for a different version.

 

If .diff.lua doesn't combine well with new .lua foundation then it is discarded and there is no different from default applied.

I’m sure you’re right, but that doesn’t make it any less annoying!

Again? Buff I just finished my ka-50 profile. I will switch again to use CH Manager for key binding.

It is very annoying.

Sent from my MiG-29S (9-13S) using Tapatalk

System is working that your personal .diff.lua file defines differences between default .lua control file and end result. What happens in patch where default .lua file is changed that .diff.lua is incompatible as a change layer because it is designed for a different version.

 

If .diff.lua doesn't combine well with new .lua foundation then it is discarded and there is no different from default applied.

Well they "ED" should learn to program better I mean really that's so 80's to not include some form of converter routine to update the old format to be compatible to the new format.

Honestly I would have thought things would bet better with 2.5 given they no longer need to support 2 forks 1.6 and 2.x etc.

Yes I had the Mustang completely borked but the Hornet was fine? One would think with how angry this makes people you would go out of your way to avoid it happening, in saying that I have no idea how to build a flight simulator of this complexity so I don't know what's involved, I just know how frustrating it is to have to re go through all your bindings, then help your squad mates out resetting their stuff up, then doing it again because you missed something when we just want to be flying.

Frankly, it would be impossible to progress with software updates without making changes to the old code. Why are you so upset because change makes old settings obsolete occasionally?

There is a very simple way to avoid changes. Run with the stable version and leave the Beta work to people with the ability to adopt and adapt.

Just don't get so precious about minor inconveniences. It takes minutes to check and fix control inputs after all!

It seems that by adding a new Mustang ED made some errors in the bindings folders. The settings for -25 (which old missions default to) are saved in a new folder ("Saved Games\DCS\Config\Input\P-51D-30-NA"). And the folder is empty. If you copy your old Mustang bindings from "Config\Input\P-51D" it will work fine.

C-101CC also has separate bindings to C-101EB, which is understandable.

Haven't had any issues with Bf-109 or Spitfire bindings on my machine.

Frankly, it would be impossible to progress with software updates without making changes to the old code. Why are you so upset because change makes old settings obsolete occasionally?

 

There is a very simple way to avoid changes. Run with the stable version and leave the Beta work to people with the ability to adopt and adapt.

 

 

Just don't get so precious about minor inconveniences. It takes minutes to check and fix control inputs after all!

I disagree with this. Sticking to the 'stable' version only delays the issue, it doesn't make it go away.

I am not privy to DCS code - obviously - but I can't imagine it would be a difficult task to ensure the binding files are easily converted.

You say it only takes a few minutes, but those few minutes multiplied by a dozen aircraft is quite a painful, and, I would think, quite unnecessary task to undertake. There is also the issue of remembering all the bindings in the first place.

Can you imagine what the reaction would be if 'normal' (non DCS) game updates nullified previous version save games?

Hmm...

I disagree with this. Sticking to the 'stable' version only delays the issue, it doesn't make it go away.

I am not privy to DCS code - obviously - but I can't imagine it would be a difficult task to ensure the binding files are easily converted.

You say it only takes a few minutes, but those few minutes multiplied by a dozen aircraft is quite a painful, and, I would think, quite unnecessary task to undertake. There is also the issue of remembering all the bindings in the first place.

Can you imagine what the reaction would be if 'normal' (non DCS) game updates nullified previous version save games?

Hmm...

Not to sound indifferent to the problem , but stable did avoid that whole bindings debacle of 2-3 months ago .

Not to sound indifferent to the problem , but stable did avoid that whole bindings debacle of 2-3 months ago .

That's true on that occasion, but I seem to remember that was because ED released a hotfix to the beta to solve the issue. That is why I am kind of surprised we are here again.

Frankly, it would be impossible to progress with software updates without making changes to the old code. Why are you so upset because change makes old settings obsolete occasionally?

 

There is a very simple way to avoid changes. Run with the stable version and leave the Beta work to people with the ability to adopt and adapt.

 

 

Just don't get so precious about minor inconveniences. It takes minutes to check and fix control inputs after all!

How many minutes are you talking about, times how many modules you own? Get serious, re-doing all those settings is a major pain in the ***.

“Precious”? , jeez!

So what was the change that supposedly was so great that it bined my .dif file?

My bindings are gone and I can't assign new ones?

This time is a little different for me. Before, when I lost my bindings, I was able to go back and reassign them. Now, all of the controls are blacked out for my HOTAS and a message that says there are no devices to assign controls to. This is only happening to a few of my planes like the Su-27. Viggen, F-15, and a few others are OK. I thought I might have deleted something important when cleaning up some folders so I deleted DCS, and reinstalled everything but I'm still getting the same result.

I am getting this exact same problem. DCS sees my joystick, but the column is greyed out. God damn it, now I can't even play. What to do?

Load the diff.lua again or delete the diff.lua to revert to default controls.

Hi, some of control assignments look like this, and I cannot bind them to my joystick or throttle.

Do I have to delete my control settings and rebind everything?

Red marks indicate oddities like two different controls with same name, multiple binds which conflict, etc. It's not good but if it works it works.

I would open the diff.lua (plural, one for each controller) and delete the entries associated with the red lines. Then those lines should revert to default. That will be a lot less work than a complete wipe.

I experienced the same @$!#$ with the controls settings again!

Neil, it takes me over an hour to reassign my control PER A/c that is effected!

ED, There has to be a method to back up keyboard and profiles, some file to save and then reinstall.

What good is the "export/inport" of profiles is they don't work! :)

I have NOT seen a reply from ED on this at all, have I missed one?

Backup before Updates the conten of your:

C:\Users\YOURNAME\Saved Games\DCS\Config

and then restore it....

been there, done that, does not restore key settings a function hosta assignments!

I am building a A-10C warthog cockpit. i bought all the flight equipment as far as thrustmaster hotas warthog stick and throttle, MFG crosswind rudder pedals, volairsim.com flight sim chasis and 3 32 inch tvs for a 96 inch screen. i am now onto the control panels build of cockpit. i bought board from desktopaviator.com model 2120. wired the switches for the power/canopy panel except for the inverter and the canopy buttons that are 3 position. i need new board for that. i set the binds. in both game and sim and even in the aircraft panels them selves but it still wipes my binds as soon as i exit settings. wether i bind and save or load the bind profile i just made3. it only keeps the hotas keybinds. please help.

New Update. And again, all joystick settings are gone. Restore the backup config didn't work either. Very anoying.... :(