Mine got wiped out as well
Yikes, thanks fit the heads up!
Usually that mean they added some key-stroke functions…
Or It’s just me?
usually. In this case I’ll bet it was the NVG commands.
So could there be a small patch to address that loss of key binds or are we basically just going to be required to live with the loss? If it’s the former, I may just wait to update.
Forgot to take off the VR mod before the update - wondered where my FPS went. I read that it still works, so will put it on again I guess…
2 Likes
I doubt it’s considered a big enough deal to warrant a patch. In the scheme of things it’s not that difficult to just remap the controls.
Did you use a mod installer?
No. I used to use JSGME, but this has been my only mod I’ve used in a long time, so figured I’d just have to reapply it.
It’s an odd one, because the Mods\terrains..\metacache files in the install folder only need to be removed just to force DCS to actually look at and recompile all the shader files again from the changed .hlsl source files - it’s why it takes so long compared to a normal install at start-up.
1 Like
For people whose main hobby is not playing DCS but who occasionally want to join in the fun, it’s stuff like this that makes it a hassle. I speak from experience trying to fly with ‘more casual’ pilots.
On topic:
Don’t forget to turn off your mods! I know I always forget that, let’s hope It remember this time
In my experience DCS (or Arma, or anything with sufficiently complex controls), could be a one button install and people who aren’t motivated will find excuses. 
If you don’t use Cougar MFDs, the Hornet is fully functional with about 25 buttons OTOH.
The PG map is looking great. It looks like the clouds respond to the base elevation setting in the mission editor much better now, which is cool. You can set them much lower then before. I also lost my key bindings, but thankfully I do nightly backups. Will try to restore later.
“All terrains are updated”
Any ideas what all this includes? A little more detail would be nice.
1 Like
I know they’ve been messing with lighting on the pg map, that might have gotten pushed out to the other maps perhaps?
Changing “G for gear” to “G for grenade” was one of the most boneheaded moves of all time.
5 Likes
Also: Funny as hell.
4 Likes
Hahaha that’s amazing! Talk about a practical joke by the devs.
1 Like
Just a heads up, I dont think saving the files to try to restore the keybinds works either, but YMMV. I’ll just rebind.
1 Like
Control configs are now in your saved games DCS folders - not the install folders. (something like below)
C:\Users\yourname\Saved Games\DCS.openbeta\Config
1 Like
This work-around worked for me and saved me from having to redo any:
https://forums.eagle.ru/showpost.php?p=3570603&postcount=91
This only works if you haven’t rebinded anything yet in the F/A 18C. You go to:
X:\Users\grumpyfrog\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick\Your Stick etc .diff.lua
and
X:\Users\grumpyfrog\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet\joystick\Your Throttle etc .diff.lua
and do a search and replace in Notepad+ (or something) changing all instances of ‘cd38’ to ‘cd13’ (there are about 14 or so of them at least). Essentially the ‘device_id’ changed in a breaky way, but it’s easy to fix up.
Man I wen’t looking tonight with hope, but found no files that match that. I hope there is a hot fix soon.