F18 Keybinds after 07/18/18 Update

same

It's not an issue that should be fixed.

 

During development stuff changes which affects config files, and this means the existing ones have to be replaced. Attempting to merge a user's custom configs with new ones (either during the update or manually) is prone to errors, which would make identifying actual problems much more difficult.

 

Best advice is to leave controller default as much as possible, and do the remapping (both keybinding and curves etc.) in the respective profiling software. Takes a bit of effort, but is far more robust.

Actually it is an issue that needs to be fixed. The very post that describes the fix, clearly reveals it as typing error on part of a programmer.

Think I found a solution.

 

...

First of all, I want to thank you, abelian! It is a great find!

 

Your solution is almost perfect. A small addition is that device numbers after 37 also changed, they moved up by 1, i.e. RWR number of 54 changed to 53. I can't tell right now which commands are affected besides HOTAS.

 

Module is in extensive development and such things could happen. I want to apologize, this particular case is my omission.

Will give this a try later this evening. Always good to see constructive input from the community! :thumbup:

EDIT: Fix worked fine. Only problem for me now the dreaded CTD. I'm sure it's unrelated to this fix though. Thanks abelian!

Wasn't the introduction of LUA.DIFF files supposed to eliminate this type of issue?

The reason the Key Bindings were reset is because Items were added and Key ID's were changed.

This is Early Access, so expect things like this to happen when major function keys are added.

Thanks for clarifying. The changes must be deeper inside as in the default.lua (joystick) the only change was the addition of these:

--NightVision
{combos = {{key = 'H', reformers = {'RShift'}}}           , down    = iCommandViewNightVisionGogglesOn   , name = _('Toggle goggles')   , category = _('Sensors')},
{combos = {{key = 'H', reformers = {'RShift','RCtrl'}}}, pressed = iCommandPlane_Helmet_Brightess_Up  , name = _('Gain goggles up')  , category = _('Sensors')},
{combos = {{key = 'H', reformers = {'RShift','RAlt'}}} , pressed = iCommandPlane_Helmet_Brightess_Down, name = _('Gain goggles down'), category = _('Sensors')},

So for example the ATC button mapping got removed:

{    down = hotas_commands.THROTTLE_ATC,                                up = hotas_commands.THROTTLE_ATC,                                cockpit_device_id = devices.HOTAS,    value_down =  1.0,    value_up = 0.0,    name = _('ATC Engage/Disengage Switch'),                    category = {_('Throttle Grip'), _('HOTAS')}},

In my build 411 diff my mapping was:

        ["d3037pnilu3037cd[b]38[/b]vd1vpnilvu0"] = {
           ["added"] = {
               [1] = {
                   ["key"] = "JOY_BTN6",
               },
           },
           ["name"] = "ATC Engage/Disengage Switch",
       },

In the new build diff.lua after remapping (why was the last number in version omitted btw?):

        ["d3037pnilu3037cd[b]13[/b]vd1vpnilvu0"] = {
           ["added"] = {
               [1] = {
                   ["key"] = "JOY_BTN6",
               },
           },
           ["name"] = "ATC Engage/Disengage Switch",
       },

I see what you did there. Just the simple question is: Why? When learning how to write software, one of the first things I learned was "never change auto generated IDs by hand", at least in databases.

At least we know this is not due to any kind of bug, but internal development process. More importantly, we know when it happens again.

Module is in extensive development and such things could happen. I want to apologize, this particular case is my omission.

For me it's fine because you guys did a brilliant job with all the bindings included right from the beginning :thumbup: I thought I were dreaming when I first fired up the module. WTG!

Think I found a solution.

 

Short answer is a text replace of

cd38

with

cd13

inside your joystick and throttle's diff.lua file (%userprofile%\Saved Games\DCS\Config\Input\FA-18C_hornet or %userprofile%\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet)

 

More details to follow...

 

Edit with details:

 

The problem is inside of DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua, devices["HOTAS"] was assigned twice, probably a copy+paste error by a developer. The latter assignment overwrote the former, so the HOTAS was assigned the internal device ID of 38. In the new version of the file, the second one was removed (probably when someone added the NVG device and noticed that the cockpit device).

 

https://i.imgur.com/cGaJnTh.png

 

So anything assigned to the HOTAS with the old version of DCS would be assigned to cd38 ("cockpit device 38"). This also had the effect of changing other device IDs. So if there was anything assigned to devices 39 and higher, the .diff.lua profiles need to be updated to match the new device ids.

 

And to add... it would have made much more sense to just use device 13 for the new NVGs. Then backwards compatibility would have been maintained, there would have been no unused device id, and NVG support would still work.

Thanks!! Worked like a charm.

All this talk of device IDs is over my head, but doesn't this fix really just delay the problem? If you revert to the old ID, won't you have the same issue of losing your bindings after the next update, or after you have to do a repair for some reason? It seems like we'll eventually have to rebind the controls, unless we want to continue to do this fix after every update?

Think I found a solution.

 

Short answer is a text replace of

cd38

with

cd13

inside your joystick and throttle's diff.lua file (%userprofile%\Saved Games\DCS\Config\Input\FA-18C_hornet or %userprofile%\Saved Games\DCS.openbeta\Config\Input\FA-18C_hornet)

 

More details to follow...

 

Edit with details:

 

The problem is inside of DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua, devices["HOTAS"] was assigned twice, probably a copy+paste error by a developer. The latter assignment overwrote the former, so the HOTAS was assigned the internal device ID of 38. In the new version of the file, the second one was removed (probably when someone added the NVG device and noticed that the cockpit device).

 

https://i.imgur.com/cGaJnTh.png

 

So anything assigned to the HOTAS with the old version of DCS would be assigned to cd38 ("cockpit device 38"). This also had the effect of changing other device IDs. So if there was anything assigned to devices 39 and higher, the .diff.lua profiles need to be updated to match the new device ids.

 

And to add... it would have made much more sense to just use device 13 for the new NVGs. Then backwards compatibility would have been maintained, there would have been no unused device id, and NVG support would still work.

Worked perfectly, just took a few seconds to do, thanks!

You guys screwed up and deleted my F18 joystick bindings!!! What the heck are you doing???

All this talk of device IDs is over my head, but doesn't this fix really just delay the problem? If you revert to the old ID, won't you have the same issue of losing your bindings after the next update, or after you have to do a repair for some reason? It seems like we'll eventually have to rebind the controls, unless we want to continue to do this fix after every update?

I had to rebind most of it. But actually, you just need to rebind the keys in the HOTAS section plus maybe some others to your liking. Doesn't take too long.

I will not remap. ED broke it ED better hotfix it ????

NineLine?

I see a new hotfix is about to be out, but doesn't say anything specific about the bindings being fixed.

I've made a backup of my config folder before doing the update. Haven't test it yet but would be possible to use the old config settings instead of rebind everything again?

I will not remap. ED broke it ED better hotfix it ????

NineLine?

WOW:D

Early access? It was "bound" to happen possibly...

Reassign several commands or edit several lines in .diff.lua. No other way.

How to edit it? THX

How to edit it? THX

One page back tifafan

One page back tifafan

I see thank you!

Reassign several commands or edit several lines in .diff.lua. No other way.

No hotfix about this?Okay.

Could someone explaing better what to edit?

it's not very clear to me on page 10