Key Bindings again

[BigMac]

Folks, after updating to 2.5.2.20601 I find some of my bindings are gone again - only some tho:

 

Gun Trigger & NWS. This has happened a few times, Is this to be expected after updates?

 

HUD remained in CCIP mode with Master Arm off & AG de-selected?? I noticed it remained like that during landing and only dissappeared when I went back into the Stores page to unbox GUN. No nosewheel steering from my rudder pedals to taxi off the runway????

 

Any recommendations most welcome.

[Badger1815]

Yep, same here, though they seem to be all gone...

[Nealius]

I didn't experience this with the Hornet, but I did have this problem with some of my other modules. Controls were fine in settings prior to jumping in a plane, then when I jumped in the pit some of them were wiped.

[eliterizzo]

same here

[dburne]

Just launched the Hornet this morning for the first time in a few weeks, lot of my control mapping is now gone. Ugh.

[shootersteve77]

Just updated and tried to fly the F18. Not only did I lose my HOTAS setting but I can't find half of them in the list when I try and re program them! This is really upsetting. Is there a way to prevent this in the future? Some stayed the same and others were re-set or completely missing. My rudder pedals were moving the view around! Ughhhh. Can't fly until I find how to set up the target designator hat switch and others.

Edited August 30, 2018 by shootersteve77

[NineLine]

The Hornet is in early access, as such things can change, they do their best not to disrupt config files, but it's not always possible.

 

If you are missing things from the control section, it sounds like something is wrong with your config file, and you may need to delete it and start over. I personally saw no issue with my Hornet controls, but I know some have.

[SonofEil]

Whenever I update I immediately do a cleanup, repair, delete fxo and metashaders, and then computer reboot. I’d suggest doing those things first. I know there have been recent instances in these forums of lost key bindings being fixed just with the reboot. If none of that works then go nuclear like NineLine suggests.

Edited August 30, 2018 by SonofEil

[LeCuvier]

I just updated my Open Beta, restarted my computer and then checked F/A-18 bindings against my documentation. Bindings were all there.

[98abaile]

Just updated and tried to fly the F18. Not only did I lose my HOTAS setting but I can't find half of them in the list when I try and re program them! This is really upsetting. Is there a way to prevent this in the future? Some stayed the same and others were re-set or completely missing.

Sounds like you've got a corrupt default.lua file somewhere; I encountered this while experimenting with mod installation and custom joystick binds. The fault I experienced was caused by the file being corrupt (likely a comma is missed somewhere) which interferes with DCS reading it correctly.

 

First go to your save games folder and see if this folder is there:

\Saved Games\DCS.openbeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick

If it is, delete the default.lua file in there and try again; this is in case you've accidentally installed a mod that's causing a conflict.

 

If that doesn't fix it, go to \Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick and delete the default.lua file (this is in case your original file is corrupt). You'll then need to repair your installation. Alternatively, I've posted a modified default.lua file with extra controls for warthog users here that I've confirmed works.

Edited August 30, 2018 by 98abaile

[shootersteve77]

Thanks for all the tips. From now on I'm gong to backup the config files that I can find so I have some recourse if this happens again. It would be good if they gave us a list of what we need to backup or even included that utility in the program. I'm sure they are tiny files. The whole update process was confusing to me as I'm used to most of my other sims checking for updates automatically when at startup.

[moonshot]

The whole update process was confusing to me as I'm used to most of my other sims checking for updates automatically when at startup.

 

Unless you’ve somehow disabled it, DCS should be checking for updates once every 24 hours.

This can lead to a little confusion/frustration if the last time your install checked for an update was 2200 Tuesday night and you fire up DCS Wednesday morning expecting the update, DCS won’t check for it until after 2200 Wednesday.

Edited August 30, 2018 by moonshot

[98abaile]

I prefer to use Skatezilla's DCS updater utility and check manually.

[bradleyjs]

I prefer to use Skatezilla's DCS updater utility and check manually.

 

It’s a one-stop shop for me!

[oldpop]

does the "SAVE profile" work at all! in Any a/c???

[F900EX]

Same happened to me, all my Joystick bindings gone from last update on all aircraft.

 

Thanks ED !!

[NineLine]

I need more info guy, if you lost your bindings, what controller, anything of special to note? My bindings came along fine, are you guys deleting the Saved Games folder (that is where your bindings live).

[LeCuvier]

After the latest OB update, I lost the bindings for firing Guns and Cannons plus Weapon release for the FW-190 and Bf-109. The other bindings were still there.

In Options/Controls, these commands were bound to all my controllers (Joystick, Throttle, Button Box, Pedals) and these lines had red background colour. After removing the extra bindings, these lines were still red and when I returned to the mission the corrected bindings were not working. I had to re-start DCS World and then they worked.

I checked my other modules and found:

AJS37: no issue

A-10C: no issue

AV-8B: no issue

F-15C: no issue

F-5E: no issue

Ka-50: no issue

Mig-21bis: no issue

Mig-29S: no issue

P-51D: no issue

Spitfire: no issue

I did not have this kind of problem with earlier updates. I never had to delete the Saved Games folder.

 

My stick: VPC T-50 base with TM WH grip

My button box: DSD Flight 2

My pedals: MFG Crosswind

My Throttle: TM WH

 

 

Edit: forgot to mention:

F/A-18: no issue here.

I suspect this is not a F/A-18 issue.

Edited September 5, 2018 by LeCuvier