Jump to content

P51D bindings set in the opening screen "Options->Controls" menu do not show up in the P51D-30-NA in game


Recommended Posts

Posted

If I open DCS Beta MT and on the opening screen select the options gear and then Controls, the drop down menu offers a P-51D Option but not the variant P51D-30-NA. So I assumed it would be common bindings for both variants. If I then go into the mission editor and create a mission, the options there are for a P-51D-25-NA or a P-51D-30-NA but the bindings I set in the Options->Controls for the P51D are not present.

So I then looked in my "...Save Games/DCS.openbeta/Config/Input" folder and I see subfolders for both P-51D and P-51D-30-NA with the lua files for each of my controllers present in the joystick folder for each. 

The result is if I take the time to set up all of my bindings from the opening screen "Options->Controls" menu under the P51-D option. They will not show up when I place a P-51D-30-NA into a mission and attempt to fly it.

It seems to be a bug in that there is only the one option for the P51D in the "Options->Controls" drop down menu vs the two in game variants. And if you attempt to set up bindings in the "Options->Controls" menu for the P51D, they will not show up when you select a P51-25-NA or P51-30-NA variant in mission editor.

Work around: Only set P51 bindings from within the game after one of the two variants has been selected. Don not use the P51D optin from the opening screen "Options->Controls" menu.

Fix: ED needs to drop the P51D generic option in the opening screen "Options->Controls" drop down box and replace it with the P51D-25-NA and P51D-30-NA options. 

Posted

Nah, generic option would suffice allright, if only it worked properly - after all ED somehow did it well in P-47 module, which has 3 variants and they're all managed from the same single tab in controls menu without any issues whatsoever.

Mustang and Spit, however, require manual copy-pasting files from one variant folder to the other to make controls work. Imacken did a great research job on it, using Spit as an example.

It's been pretty much a ~5 years old issue (when D-25 and CW Spit were added) and if it wasn't fixed already, means it's low on priority list and I wouldn't count on it being tackled anytime soon.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted

It might be a low priority problem, but it is also a low workload problem. Considering how it works-which folder in  saved games  the values are written to, it shouldn't take 5 mins to fix it regardless of the priority. All that needs to be done is to save it to two specific folders instead of one generic folder. Low hanging fruit is being left to rot on the tree!

  • 4 months later...
Posted

Please check Imacken's reply to You in "sister" thread in Spitfire bugs section, with steps to reproduce the issue.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

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

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