Jump to content

Bf-109 K4 Controls Menu Corrupted


Lynchsl62

Recommended Posts

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

  • Like 2
  • Thanks 1

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

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.

Primary for DCS and other flightsims: i9 12900K@default OC on MSI Z790 Tomahawk (MS-7D91) | 64 GB DDR5-5600 | Asus TUF RTX3090 Gaming OC | 1x 38"@3840x1600 | 1x 27"@2560x1440 | Windows10Pro64

Spoiler

Secondary: i7 11700k@5.1GHz on MSI Z590 Gaming Force MB| 64 GB DDR4-3200 | PowerColor RX6900XTU Red Devil | 1x 32"@2560*1440 + 1x24"@1980*1200 | Windows10Pro64

Backup: i7 6700K@4.8GHz | 64 GB DDR4-2400 | PowerColor RX5700XT Red Devil | SSD-500/1000GB | 1x49" 32:9 Asus X49VQ 3840x1080 | Windows10Pro64

Flightsim Input Devices: VPC: ACE2 Rudder / WarBRD Base / T-50CM2 Base with 50mm ext. / Alpha-R, Mongoos T-50CM, WarBRD and VFX Grip / T-50CM3 Throttle | VPC Sharka-50 + #2 Controle Panel | TM Cougar MFD-Frames| Rift S - Secondary: TM HOTAS WARTHOG/Cougar Throttle+Stick, F-18-Grip | TM TPR Rudder | DelanClip/PS3-CAM IR-Tracker

Link to comment
Share on other sites

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.

  • Like 1

PC: 9980XE @ 64GB RAM /2080Ti, Samsung C49RG90

Joystick bases: VKB GFIII, FSSB R3L, Brunner CLS-E, Virpil Mongoos CM2

Joystick grips: Realsimulator (F-18CGRH, F-16SGRH-CE), VKB (MCG Pro, F-14, KG-12), Virpil Warbrd

Throttles: Virpil CM2, Kantorrin,

Other: TrackIR, TM MFDx2 (Cubesim Screenx2), Virpil Control Panel 1

Link to comment
Share on other sites

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 by LeCuvier
  • Thanks 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

  • 3 weeks later...

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

Hardware: T-16000M Pack, Saitek 3 Throttle Quadrant, Homemade 32-function Leo Bodnar Button Box, MFG Crosswind Pedals Oculus Rift S

System Specs: MSI MPG X570 GAMING PLUS, GTX 1070 SC2, AMD RX3700, 32GB DDR4-3200, Samsung 860 EVO, Samsung 970 EVO 250GB

Modules: Ka-50, Mi-8MTV2, FC3, F/A-18C, F-14B, F-5E, P-51D, Spitfire Mk LF Mk. IXc, Bf-109K-4, Fw-190A-8

Maps: Normandy, Nevada

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 year later...

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

image.png

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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.

Bf-109K4 Bindings.JPG


Edited by LeCuvier
  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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.

 

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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

image.png

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


Edited by Amarok_73

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

You need to open a ticket with the support desk!

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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

null

image.png

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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 by LeCuvier

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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?

 

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Link to comment
Share on other sites

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 by Amarok_73

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

2023-04-27_22-28-47.png


Edited by Amarok_73

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

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...

 

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

  • 1 month later...

@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.

Natural Born Kamikaze

-------------------------

AMD Ryzen 5 3600, AMD Fatal1ty B450 Gaming K4, AMD Radeon RX 5700 XT, 32 GB RAM Corsair Vengeance LPX, PSU Modecom Volcano 750W, Logitech G940 HOTAS, Turtle Beach VelocityOne Rudder.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...