fixed Bf-109 K4 Controls Menu Corrupted

[Lynchsl62]

Since the last update the controls menu has become corrupted, with several command disappearing and a lot of commands combining into a heading input as per the attached file for keyboard commands.

Uninstalled the module and reinstalled the module with no change, and this seems to be the only module effected

How to resolve to get the original controls options back

Keyboard.html

[schmiefel]

And it seems coms menu is broken there, too. Have not changed the button bind and when checking in controls menu it's correctly assigned. But flying in the plane it's not working. In F-18 it works as ever.

[Slice313]

Warbirds controls binds also are a mess, most descriptions are bugged

[Lynchsl62]

7 hours ago, Slice313 said:

Warbirds controls binds also are a mess, most descriptions are bugged

As far as I can see only the P-51 control bindings are not affected.

[LeCuvier]

The bug is acknowledged by the ED team. Concerns all WW II aircraft except the Mustang, plus the Yak52.

Note: it does not make you lose existing bindings, but obviously makes it hard to find the right lines for new bindings.

Edited November 22, 2021 by LeCuvier

[Magic Zach]

Bump.  The 109 and Spitfire are hit especially hard by this

[Flappie]

No need to bump. This should be fixed in the next OB update.

[Flappie]

Fixed in today's open beta 2.7.9.17830.

[Amarok_73]

Should I consider this as corrupted? If so, how to correct it? I've already tried to reinstall module...

[LeCuvier]

I do not see this in OB MT. In which version do you see this? It looks like a bug we had some time ago. It's related to the localization, the bug presents the internal command identifiers rather than the localized command names.

[Amarok_73]

Hi @LeCuvier, I am not using MT as it's too buggy yet to me, so in OB ST I can see this.

[LeCuvier]

I tried in OB ST, latest version (2.8.4.39313) and it displays correctly (see attached screenshot).
Are you using the latest OB version?
I suppose you are not using a localized version like German or French?

Edit: as far as I know the conversion from internal identifiers to command names is based on the file "input.mo" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES", file size 218 KB. Do you have that file?
If it's the same bug as we had some time ago, you would see the same problem with the Spit. P-47 and Mosquito. They all use this strange structure to facilitate localization.

Edited April 25, 2023 by LeCuvier

[Amarok_73]

Yes, I am using most recent OB, but then, something came to my minds regarding the DCS Updater GUI. I remember, there's somewhere place, where locales have to be defined, that may have something to the issue.
I'll check it when I'll return to home.

 

[Amarok_73]

...two switches of locales and total repairs later...
null

I did also what is described in this thread, but in vain...

Edited April 25, 2023 by Amarok_73

[LeCuvier]

You need to open a ticket with the support desk!

[Amarok_73]

@LeCuvierJust for the record, second WW2 module bought on current sale, the Spitfire, and there's the same issue.

null

[LeCuvier]

Yes, as I said, the Spit as well as the Mosquito and P-47 use the same localization mechanism. That mechanism is active even if you use English.

Did you verify that you have the file "input.mo" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES", file size 218 KB?

Edited April 26, 2023 by LeCuvier

[Amarok_73]

13 minutes ago, LeCuvier said:

Did you verify that you have the file "input.mo" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES", file size 218 KB?

I did not had this file, so according to the other thread from this subforum, I did described changes, but without any effect. It can be, that I've downloaded obsolete files from this thread.
I can see, that some modules do not have the I10N subdirectory with LC_MESSAGES, so is it something special for selected modules only? For this module, the existence of these subdirs is obligatory, or it's just the way to assure, that the localisation mechanism works correctly?

 

[LeCuvier]

In the context of your problem, only the file under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\l10n\en\LC_MESSAGES" is relevant. Most of the aircraft modules do have the I10n folder structure, but the "messages.mo" files are mostly empty. Don't worry about these!

[LeCuvier]

I had a crazy thought: did you manually edit the folder name of "l10n"?
In case you did, there is potential for confusion. The folder name in file explorer looks like a capital "I" in "India" but it's actually an "l" like in "lake".
But if you did a repair, that would have been fixed I believe.

[Amarok_73]

I did actually copied this name from the other module where this directory is present. Could You put here for me package with the file(s) from this directory, so I'll be sure that they're up to date? The thread i've taken it from for my tests is quite old, so it could be the reason that these files did not worked out.
And still, only the mods of Spitfire and Bf-109 (bought on current sale) shows the non-localized entries in controls.

Edited April 27, 2023 by Amarok_73

[Amarok_73]

Edited April 27, 2023 by Amarok_73

[LeCuvier]

I sent it to you via PM.

[Amarok_73]

19 minutes ago, LeCuvier said:

I sent it to you via PM.

Thanks, I've put these files using the structure from package, and effect is still the same.

I think we done all we could. I'll open the ticket...

 

[Amarok_73]

@MotorEAST Hello Konstantin, any chance to get tips on this one? My ticked with the report for this issue was autoclosed, and still I struggle with meaningless binding descriptions.