DCS last Update: Big problem !!!

[schurem]

It's being worked on. The program is not reading your custom input files right. Don't panic!

[Whisper]

Ok rebinding all your controls not only does not fix it, its also a LOT of unnecessary work. A short bit of googling, and some sniffing around you'd have found these new "defaults" that get superimposed over your own, untouched, custom bindings. Get rid of those and no more problems.

 

ED have really messed it up this time, though.after trying to help a buddy on this issue (at first I was like you, "don't worry, it's easy to correct") I dont see currently a way to get saved bindings back. They really screwed it up. Im gonna wait before patching myself, in case ED comes up with a fix. Would be great of to first deign acknowledge it.

[backspace340]

ED have really messed it up this time, though.after trying to help a buddy on this issue (at first I was like you, "don't worry, it's easy to correct") I dont see currently a way to get saved bindings back. They really screwed it up. Im gonna wait before patching myself, in case ED comes up with a fix. Would be great of to first deign acknowledge it.

 

Follow these instructions:

[Dutch Baron]

Same here and numerous reports from my other squadron members.

Would ED be so kind to reply to any of these multiple threads that have started since yesterday?

[macedk]

This happened last time ED introduced a new keybind (night vision for f-18 ).

 

How is this not picked up in testing ??

 

Please have real testers outside your office, and delay any updates that have game stopping issues.

 

Could we work together ? How ? look at twitch and youtube ...people work/help for the creators and It is very rare that a piece of content is not accessible.

 

Come on let's work together...

[funkyfranky]

This happened last time ED introduced a new keybind (night vision for f-18 ).

How is this not picked up in testing ??

This one is different. It's not a bug. They did this deliberately.

[macedk]

Backed up all input folders and replaced after update and tried the f-18 and it works

[macedk]

This one is different. It's not a bug. They did this deliberately.

 

Lol Break the game ..nahhh don't think that was on purpose ;)

[Sir Gus]

Same problem,all my controls are messed up and i cant use some actions,like air brake,because they are greyed out.

[thrustvector]

ok just to pass on some info, if you have a saved folder of inputs etc, delete all the files in the dcs ka-50 input joystick folder except the default lua, then either re load, or like me re add your saved files from earlier.

if you haven't after this then make a backup somewhere else :)

[Marnes23]

Same here, all the keys are corrupted and some keyboard commands are not working for instance lower gear in F/A-18. I had to re-assign everything from scratch and about to test it

[Marduk879]

Same problem here. So far discovered it on Su-25T - many crucial keybinds are red and do not work(for example weapon change, laser rangefinder,A2A mode...).

Using Thrustmaster T16000M FCS and TWC throttle.

 

 

Same problem on Su-27.

Edited October 11, 2018 by Marduk879

[Raven (Elysian Angel)]

I had to re-bind all my controls for the F-18, but was able to do so without issues.

[Devrim]

It's being worked on...

Source? Official?

[gonk]

ok just to pass on some info, if you have a saved folder of inputs etc, delete all the files in the dcs ka-50 input joystick folder except the default lua, then either re load, or like me re add your saved files from earlier.

if you haven't after this then make a backup somewhere else :)

 

Ok this worked for me.. thanks. :thumbup:

 

 

1:- Always backup your controller profile categories whilst they work... before this/every patch.

 

2:- Go to where the game is installed and continue to the controller folder....

Example:- C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick

 

3:- Delete all (or move) all of the files except the one called "default.lua" from this folder.

4:- start the game and load your saved profiles back in...

 

Worked for my F18C... does not for the A10C.. Weird.. oh well..

Edited October 11, 2018 by gonk

[Marduk879]

Nineline somewhere on hoggit... Is that even an OFFICIAL statement?!....

Edited October 11, 2018 by Marduk879

[spike2450]

Can we have an official ED comment please.

 

Hi, after the horror of the latest binding gate, I've just had the nightmare of going through all the F18 bindings and noticed the F15 is just as bad.

 

Do we wait for a Hotfix or do we struggle on.

 

Can you let us know what the new control assignments are as well.

 

In anticipation :helpsmilie:

[QuiGon]

This issue is pretty much unavoidable for a module in Early Access (and sometimes even for an older module), because systems change during Early Access development and with that the controls change as well. For example: You first implement a simple ECM function where you can just push artifical hotkeys to dispense flares and chaff or activate ECM and later the actual ECm suite gets implemented and now you have to work with the actual HOTAS commands where you don't have a button for chaff or flare, but instead have to work with CM-programs. That's the nature of a module that is still in active development.

Edited October 11, 2018 by QuiGon

[Mr_sukebe]

I’m a bit confused.

Went and flew a bunch of aircraft last night including the Spit, Gazelle, F18, harrier, Viggen and mirage, all with no issues.

 

Is this issue meant to be affecting everyone, or just pilots with certain kit?

[MasterZelgadis]

It is not unavoidable, you can leave all other mappings, that are not affected by that feature, what they were. Or you can migrate the old config, leaving only the ney functions unmapped.

It's a question whether you want to do that work for a module, where every customer knows (by the tag "early access") that everything can and probably will be subject to change

[backspace340]

They're looking into fixing it in some form or fashion (I'm assuming as a hotfix): https://forums.eagle.ru/showpost.php?p=3652107&postcount=51

[spike2450]

F15 isn't in early access and that is as bad as the f18.

[backspace340]

I’m a bit confused.

Went and flew a bunch of aircraft last night including the Spit, Gazelle, F18, harrier, Viggen and mirage, all with no issues.

 

Is this issue meant to be affecting everyone, or just pilots with certain kit?

 

It affects anyone using the equipment they made default profiles for - e.g. TM Warthog, Hotas X, 16000 among others.

[Devrim]

For example, I, X-55 user, have no any issue about this problem.

But if ED will do same update for Saitek products next update, I could jump down from a mountain. :P

[thrustvector]

dam, not sure if it has worked, gone out the game came back in all back to being messed up, still don't get why they can mess up our own profiles!!