[Wish] Category Load/Save

[Devrim]

Because of that I'm sick about re-assigning the keyboard keys and Saitek buttons after every update (especially for Mi-8 and Huey), I decided to save and store each category. So, in a control category (for example, Uh-1H "Ins Cyclic Stick"), if there's any update (new keys or axis), I'd re-assign buttons etc., that's OK. But if not, I'd like to load that category that I previously saved.

 

But that's not possible; if I save a category, DCS saves all categories into one lua file!

 

I edited my "Ins Cyclic Stick.lua" file and erased other unwanted categories but "Ins Cyclic Stick" lines. Came back to Options/Controls page and tried to load it back. "Ins Cyclic Stick" category was loaded successfully, but other whole categories were blank! :(

 

I'm thinking that this system is not user friendly.

 

I know Wags declared about editable controls in game. But I don't think it's a solution for this. I feel worry in every update, "I wonder, is there any key/axis update?", "I wonder, if I use my saved lua file, will I lose any function of aircraft?", "Will I re-assign whole keyboard and joystic, AGAIN?!"...

 

I'm afraid this issue will create a psychological problem on me. :D

Thank you.

Edited October 21, 2013 by Devrim

[Devrim]

...Added input command for controls of the pilot's sight*

* You may need to delete the user input files for UH-1H for these changes to take effect

Yaeey! Another one!

 

Now we have to reassign all controllers from zero for Huey...

And we will have to... for future updates...

[Home Fries]

I would recommend a step further.

 

When a default control lua is updated, compare the new default to the old lua line by line. If the old lua has an identical line for the control name and description (but not the keys/buttons themselves), leave it as is. If the old lua has an obsolete control name, rem the line with -- (so you can manually go through your LUA to see what changed). If the new default has a control name that doesn't exist in the old lua (e.g. the pilot sight illumination in the latest Huey build), then insert it with the default mapping.

 

This way we can keep our profiles between builds, and anything that didn't directly translate could still be looked at manually.

 

EDIT: Come to think of it, I could probably write a VB Script to do exactly that.

[Devrim]

Thank you for advice and attention. :)

 

Actually I do that. For example, I updated my lua file of Huey via this method. But in fact (I'm thinking that) we shouldn't need to do that, or you shouldn't need to srite a script.

 

My honest opinion is that controllers page must be developed...

[Home Fries]

Unfortunately, the script isn't as straightforward as I had hoped. While the fields on each line are comma delimited, brackets are used to define subsets like control modifiers. I need to figure out how to do delimit only the stuff outside the brackets (not counting bounding brackets for the entire line).

 

e.g.

{combos = {{key = "JOY_BTN21", reformers = {"JOY_BTN31", }}, {key = "JOY_BTN23", reformers = {"JOY_BTN31", }}, }, down = 3021, cockpit_device_id = 9, value_down = 1, name = "Armament Selector Up", category = "Armament System"},