Anyone else's bindings messed up with the new patch 2.5.3.22652?

Just updated to the new patch 2.5.3.22652, hopped in an instant action and found I couldn't select AMRAAM or Sidewinder using my usual bindings. I've checked controls and it looks like a load of bindings have been changed, plus some are greyed out and so even they're the correct bindings they're not working. I've tried setting the binding again but it's not changing anything. I'm not sure what to do at this point - this doesn't seem like before where the bindings got wiped as I could at least remap them then.

Mine seem ok, just quickly checked after seeing your post.

Using default controller lua's, if that could be the issue.

Edit: Just added a screenshot of the same segment.

Edit: And for what its worth. I didnt change my controller lua's back when the Hornet controls got screwed with some ID change of sort (I think it was). I just remapped it all.

+1, same issue :doh:

Some controls have a redish color, not sure what that means and even being re-binded they wont work :cry:...whats going on??

Just in case it helps - I can't even use the default keyboard bindings to select Sidewinders/AMRAAMs (so it doesn't seem to be a controller issue).

Restart worked for me, and got rid of the red bindings.

Mine seem ok, just quickly checked after seeing your post.

Using default controller lua's, if that could be the issue.

 

Edit: Just added a screenshot of the same segment.

 

Edit: And for what its worth. I didnt change my controller lua's back when the Hornet controls got screwed with some ID change of sort (I think it was). I just remapped it all.

Yeah I didn't edit any luas either, I just rebound - it looks like they've added/updated some default configs for the Thrustmaster joysticks and throttles according to some lua sleuthing someone else did, so seems like that's possibly causing the issues for me (I'm using the T16000 and TWCS which is on the list). I'm guessing there's a conflict between their default and my previous bindings.

I think if you set the binding marked red to "default" and restart the game, this will fix it and then you'll be able to change the assignment as you like.

At least that's what usually works for me if I see such error.

Yep, and there a comm issues. Not sure if its our server but SRS won't work and key binds will not work.

Yes, a quick restart fixes the issues.

I hate these binding issues! ED never found a proper technique to handle binding thing!

Until last year I was directly editing stock lua files to fix my own bindings but I couldn't stand against updates, updates and updates. That's was exhausting modding for me. I quit.

... but I luckily have zero problem with bindings on today's update. :D :D :D

Same issue engine crank left and right dont work for me

confirm, update double binded the buttons on my T16000.

(hopefully )fixed it by deleting/moving the Diff files in the Inputs folder....

Mine are TOTALLY SCREWED UP again. Its really SHODDY release control by ED messing up binding, seemingly at random. They really need to sort themselves out, this is VERY basic stuff that any IT newbie developer should be able to deal with. There is no reason whatsoever why bindings should change UNLESS ED specifically notify which ones as part of the release notes. I seriously have to worry about the lack of professionalism of ED in this area (And I speak as an IT professional with 30 yrs experience including being my organisations release manager for 10 of those years.) BE ASHAMED ED.

Same here. I have had to resign bindings in all modules.

Does this have anything to do with that Triple-Screen Missing Controllers from last week?

Restarting did not fix it for me. I'm going through removing all the new default bindings and then going to try again.

Doesn't seem to work just blanking it and re-assigning either.

Mine are TOTALLY SCREWED UP again. Its really SHODDY release control by ED messing up binding, seemingly at random. They really need to sort themselves out, this is VERY basic stuff that any IT newbie developer should be able to deal with. There is no reason whatsoever why bindings should change UNLESS ED specifically notify which ones as part of the release notes. I seriously have to worry about the lack of professionalism of ED in this area (And I speak as an IT professional with 30 yrs experience including being my organisations release manager for 10 of those years.) BE ASHAMED ED.

You were warned multiple times that keybindings could and will change during EA. This is not the first time and it won't be the last.

I seriously doubt the veracity of your claims. As an IT Solutions Architect I have not seen a single business operate an IT department at any level without errors. I have seen patches work flawlessly in a Test environment to only fail miserably in a Prod environment.

I have personally witnessed Project Managers lie to get features or config changes pushed which resulted in Prod failures.

I have personally seen manufacturer hardware patches bring down a Prod network resulting in the manufacturer paying Federal Reserve Fines that were incurred as a result of a mandatory upgrade.

So I call BS on everything you typed...

I should say (before anyone else mentions it) I DID follw the usual ED advice and back up my controller mappings before the update. Restoring them after the update had messed up my bindings did NOTHING, they were still messed up after I restored the backup in the same way (multiple keys/buttons bound to functions at random, same button mapped to more than one function, other mappings I had deliberately BLANKED appearing again. Also I notice that the ORDER in which devices appear in the mapping screen changes randomly after updates. I use KEYBOARD, THRUSTMASTER WARTHOG JOYSTICK, THRUSTMASTER WARTHOG THROTTLE, THRUSTMASTER RUDDER PEDALS and MOUSE. But after an update the order the devices appear in on the screen changes at random on those occasions when the update has messed up the bindings (and differs between Release version and Open Beta). SO I end up having to remap everything which is a total pain when you have multiple DCS modules to do the remapping for, and the 'Backup' approach doesn't work (probably because the device order changes randomly). No I haven't replugged my devices by the way.

This isn't just a Hornet issue. It seems to have impacted all of EDs aircraft in some way. (3rd party aircraft seem to be fine). So basically none of these aircraft are flyable except using the default bindings right now for me (and some of the default bindings are awful).

REVELATION : IT departments do make errors. but should NEVER NEVER NEVER make the same error twice, let alone MANY times, each time causing major disruption to the customer, and worst of all appearing to not care they are doing it. I HAVE SACKED STAFF FOR LESS. So don't 'seriously doubt' what I say, come and work for me and see how long before I sack you for causing unacceptable disruption to customers.

REVELATION : IT departments do make errors. but should NEVER NEVER NEVER make the same error twice, let alone MANY times,

each time causing major disruption to the customer, and worst of all appearing to not care they are doing it.

I HAVE SACKED STAFF FOR LESS.

So don't 'seriously doubt' what I say, come and work for me and see how long before I sack you for causing unacceptable disruption to customers.

Fighting about it isn't constructive and reduces the likelihood of a response as the thread rapidly becomes toxic.

Its an issue that has affected pretty much all of EDs aircraft not just the Hornet and expecting something to be done the moment it is brought to their attention (as if they knew it was a problem and pushed it anyway) is unreasonable.

Please also bare in mind this was an update to the Open Beta version of the game, there is nothing stopping you from rolling it back to the standard version at least for now if that is what you choose to do.

As far as I can see, they added default mappings for all popular input devices which messes things up. Nice to see some more default mappings... It's still EA and not the end of the world...

Confirmed here as well. HOTAS bindings completely broken. Many TM Warthog buttons not even recognized. I did backup my previous settings, but no avail, it did not override what ED broke again. Smh...

I had only some double bindings, Com1+2 and Airbreak retract, everything else is working fine as before the update.