Modified controls Lua resetting every update

[ScopeDope]

Hey guys how do you keep from having your default.lua reset every time they push an update? I've added warthog 3 way bindings and after every update they get wiped away. I've tried editing the default.lua in my Saved games/AV8BNA folder which doesn't seem to work.

[Devrim]

I have headache with controller control method of DCS for years and years.

That's why I hate early access or WIP modules.

 

So, I gave up. I just assigning keys in-game. You'll see Input folder under Config folder, in Saved Games.

 

For example, today, Start Flare (or whatever) keycommand was lost in my HOTAS. I re-assigned it. Etc... etc...

 

Life is hard, mate. :)

[jonsky7]

Hey guys how do you keep from having your default.lua reset every time they push an update? I've added warthog 3 way bindings and after every update they get wiped away. I've tried editing the default.lua in my Saved games/AV8BNA folder which doesn't seem to work.

 

Use JSGME,

 

it's a mod manager that allows you to quickly put your modified .lua back into the game after an update.

 

https://forums.eagle.ru/showthread.php?t=98607

[Nero.ger]

that poses a problem in modules that are in development.

if the Devs change the original input.lua and you copy an old version with your mods back, you might miss out on updates (happend in the harrier and the TDC-axis slew).

 

the "trick" that worked for me is , after an update, imidiatly(!) exit the game and copy my modified lines back into the default.lua.

never had to redo any keybinds

 

this post was made without coffee

[Raz_Specter]

i also am using a custom default.lua with my warthog to enable the 3 ways etc. I just check each time there is an update if the flaps are workng, if not I use OVGME update the file.

 

I also have my segement at the top of the file so can create another from the update and just past in my custom controls which helps and you dont miss an update

[ScopeDope]

Thanks guys, seems copy paste is the way I'll go. Wish 3 ways for at least the basic stuff would get put into their base code. It literally would take 2 minutes for them to take what's been posted in the forum.

[firmek]

Thanks guys, seems copy paste is the way I'll go. Wish 3 ways for at least the basic stuff would get put into their base code. It literally would take 2 minutes for them to take what's been posted in the forum.

Unfortunatelly yes. The only way is manually merge the files. Programs like WinMerge can make it easier but the mentioned JSGME is not a solution at all. Quite opposite as you don't know if something hasn't been changed with the update you may end up overwriting an updated file with an old one.

 

Just create a clearly commented out secion on top of the file and copy it with every update.

 

The solution?

Developers should stop screwing around and to their job of creating 2 and 3 way switches abstraction for every single switch in the cockpit.

Seriously, I'm more than tired to have to do that on my own for every single module - quite often failing as only toggle action is available while separate on/off are not.

It's not asking too much - such list is created and posted on the forums within hours after a module release. The bottom line is - devs are taking a shortcut thinking that community will manage it.

 

It's not funny that the only single module in DCS which is working correctly out of the box with TM-Worthog is A-10C.

[Deano87]

Developers should stop screwing around and to their job of creating 2 and 3 way switches abstraction for every single switch in the cockpit.

 

Yep... This.

[jonsky7]

that poses a problem in modules that are in development.

if the Devs change the original input.lua and you copy an old version with your mods back, you might miss out on updates (happend in the harrier and the TDC-axis slew).

 

the "trick" that worked for me is , after an update, imidiatly(!) exit the game and copy my modified lines back into the default.lua.

never had to redo any keybinds

 

this post was made without coffee

 

Good point, well made :thumbup:

[scrapple]

Will modifying the default.lua cause any problems with integrity checking on servers? I'm still confused about what you can and can not get away with for integrity checks.

[Nero.ger]

no it does not cause problem, because the IC is ment to prevent cheating by changinf missle damage or the like, not preventing you from using your Expensive Hardware

[The LT]

The solution?

Developers should stop screwing around and to their job of creating 2 and 3 way switches abstraction for every single switch in the cockpit.

Seriously, I'm more than tired to have to do that on my own for every single module - quite often failing as only toggle action is available while separate on/off are not.

It's not asking too much - such list is created and posted on the forums within hours after a module release. The bottom line is - devs are taking a shortcut thinking that community will manage it.

 

It's not funny that the only single module in DCS which is working correctly out of the box with TM-Worthog is A-10C.

 

No, this isn't an optimal solution. An optimal solution would be to update the DCS keybinder to be aware of actions other than a keypress. It would be a simple matter of adding "key-up" and "key-down" actions to the keybinder. That way, we would not have to revert to LUA editing.