Odd Action Names have appeared in several aircraft controls lists following patch

[Baldrick33]

2.7.8.16140 Open Beta

Several aircraft now have strange names appearing in the Action column in the controls setup

These have the form Input.aircraftname.xxxxx

In some cases these can be aircraft other than the one being setup (presumably copied from other aircraft controls)

So far I have identified the following aircraft that are impacted:

Spitfire
Mosquito
BF109
FW190-D9
FW190-A8
Yak-52
P-47

An example of the Mosquito entries are shown below:
 

Edited November 20, 2021 by Baldrick33
Added Open Beta version number

[hicks78]

I was wondering this too, as it happened with my spitfire control setup, wasnt sure if it was an issue only with my client or what. Thanks for posting

[titi69]

I got the same for the spit, P-51 is ok , seems only WWII aricraft
I have checked lua input file and name has been changed

 

[Nealius]

This is gamebreaking for me, assuming keybinds are wiped and we have to reassign everything not knowing precisely what’s what. Will not update until it’s addressed in a hotfix or the next patch cycle. 

Edited November 22, 2021 by Nealius

[Baldrick33]

8 hours ago, Nealius said:

This is gamebreaking for me, assuming keybinds are wiped and we have to reassign everything not knowing precisely what’s what. Will not update until it’s addressed in a hotfix or the next patch cycle. 

 

My interpretation is that is it is just a change to naming of Actions rather than changing the bindings. So what was undercarriage down is now something like input.spitfireLFMkIX.uc1. The bindings are still there, just harder to find!

Edited November 22, 2021 by Baldrick33

[Munkwolf]

The labels in the LUA for the spit and some other modules have always been like "input.spitfireLFMkIX.uc1"... seems like what broke was the mapping of those resource ID's to the readable labels (it's a common pattern for localization)

[Nealius]

But no one had to redo their keybinds after the update, correct?

[Baldrick33]

Seems to have been addressed with today's patch. Thanks.