Jump to content

Frequent keybind unavilability issues (red exclamation marks) with the F-4E


Go to solution Solved by Smyth,

Recommended Posts

Posted

Hello there!
I have encountered frequent keybinds issue with the module with those red exclamation marks on both the names and the slots of the key binds. It has happened three times in a roll for me in the past two weeks with one instance on pinky switch weapon selction (radar) and two instances on the left wheel brake.

I did try deleting the input folder under C:/saved games and let the DCS generate a new input folder, and loading my previous keybind profile. For some time the issue was fixed but it kept popping back up. I just suddenly lose that keybind and there's a red exclamation mark on it. Any idea what may cause that issue? Thanks in advance!

Digital Combat Simulator  Black Shark Screenshot 2024.06.10 - 23.36.17.28.png

  • Solution
Posted (edited)

I had a similar issue and eventually noticed that the default keybind for both of those commands was 'LShift + D'.

At first the persistent red exclamation point would completely block the pinky switch radar selection on joystick buttons, and no combination of disabling/enabling/re-scanning devices fixed it reliably. After starting over and deleting those double-assigned keybinds first, the situation improved but was not completely resolved. Now I only have to go to control manager and choose 'rescan devices' every time I start the game, which has been working reliably. I don't know if that will work in your situation.

Edit - confirmed experimentally that this can be fixed completely by updating line 193 in "DCSWorld\Mods\aircraft\F-4E\Input\F-4E-Pilot\keyboard\default.lua"

From:

{ name = _('Wheel Brake (Left)'), combos = combo('D', 'LShift'), pressed = iCommandLeftWheelBrake, up = iCommandLeftWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },

To:

{ name = _('Wheel Brake (Left)'), combos = combo('D', 'LCtrl'), pressed = iCommandLeftWheelBrake, up = iCommandLeftWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },

Then fixing the .diff file in 'Saved Games' folder to work with that.

However this is still not a great solution because DCS updates will likely break the keybind again.

There must  be some reason that most players are not experiencing this, but I cannot figure out what it could be.

Edited by Smyth
core file edit example
  • Like 3

More or less equal than others

Posted

The wheel brake commands have been fixed in the last update, version 2.9.5.55918. The LUA lines for left and right wheel brakes are now

{ name = _('Wheel Brake (Left)'), combos = combo('D', 'LShift'), pressed = iCommandLeftWheelBrake, up = iCommandLeftWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },
{ name = _('Wheel Brake (Right)'), combos = combo('D', 'LAlt'), pressed = iCommandRightWheelBrake, up = iCommandRightWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },

 

  • Like 2

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted
16 hours ago, Smyth said:

Edit - confirmed experimentally that this can be fixed completely by updating line 193 in "DCSWorld\Mods\aircraft\F-4E\Input\F-4E-Pilot\keyboard\default.lua"

Thank you so much for the help! It is now working fine on my side as well. But yeah, it is kinda mysterious why the LShift+D becomes a 'Nay' button... I hope devs can figure that out. 

  • Like 1
Posted
9 hours ago, LeCuvier said:

The wheel brake commands have been fixed in the last update, version 2.9.5.55918. The LUA lines for left and right wheel brakes are now

{ name = _('Wheel Brake (Left)'), combos = combo('D', 'LShift'), pressed = iCommandLeftWheelBrake, up = iCommandLeftWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },
{ name = _('Wheel Brake (Right)'), combos = combo('D', 'LAlt'), pressed = iCommandRightWheelBrake, up = iCommandRightWheelBrake, value_pressed = -1, value_up = 1, category = { categories.gears_brakes_hook, categories.pedals } },

 

Those are still the problematic lines. LShift + D is also used at line 165 for pinky switch. I am on 2.9.5.55918.

More or less equal than others

Posted
6 hours ago, Smyth said:

Those are still the problematic lines. LShift + D is also used at line 165 for pinky switch. I am on 2.9.5.55918.

You are right indeed. But that's easy to fix. The expression "combo('D', 'LAlt')" is only a default binding. You can clear the default binding in Options/Controls and replace it with a unique one.

I changed Wheel Brake (Left) to "[LCtrl] + D". This override is stored in the file "Keyboard.diff.lua" under "Saved Games" and it will be "respected" by the game software when you do an update or repair. Here is what the entry in "Keyboard.diff.lua" looks like:

local diff = {
	["keyDiffs"] = {
		["dnilp2112u2112cdnilvdnilvp-1vu1"] = {
			["added"] = {
				[1] = {
					["key"] = "D",
					["reformers"] = {
						[1] = "LCtrl",
					},
				},
			},
			["name"] = "Wheel Brake (Left)",
			["removed"] = {
				[1] = {
					["key"] = "D",
					["reformers"] = {
						[1] = "LShift",
					},
				},
			},
		},
	},
}
return diff

It's the only keyboard binding I changed, that's why there is only this entry in the file.

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted
7 minutes ago, LeCuvier said:

You are right indeed. But that's easy to fix. The expression "combo('D', 'LAlt')" is only a default binding. You can clear the default binding in Options/Controls and replace it with a unique one.

I changed Wheel Brake (Left) to "[LCtrl] + D". This override is stored in the file "Keyboard.diff.lua" under "Saved Games" and it will be "respected" by the game software when you do an update or repair. Here is what the entry in "Keyboard.diff.lua" looks like:

local diff = {
	["keyDiffs"] = {
		["dnilp2112u2112cdnilvdnilvp-1vu1"] = {
			["added"] = {
				[1] = {
					["key"] = "D",
					["reformers"] = {
						[1] = "LCtrl",
					},
				},
			},
			["name"] = "Wheel Brake (Left)",
			["removed"] = {
				[1] = {
					["key"] = "D",
					["reformers"] = {
						[1] = "LShift",
					},
				},
			},
		},
	},
}
return diff

It's the only keyboard binding I changed, that's why there is only this entry in the file.

That was the first thing I tried. The basic problem here is that for whatever reason, my DCS installation does not like removing this duplicated default keybind with the .diff file:

image.png

Still have to 'rescan devices' on every startup that way. Only fixing the core file makes it go away completely.

More or less equal than others

Posted (edited)
1 hour ago, Smyth said:

That was the first thing I tried. The basic problem here is that for whatever reason, my DCS installation does not like removing this duplicated default keybind with the .diff file:

 

Still have to 'rescan devices' on every startup that way. Only fixing the core file makes it go away completely.

That's weird! I do not see this behaviour at all. And I don't understand what "Rescan Devices" would do in this case.
When I enter 'LCtrl' + 'D', my Phantom veers to the left. So it works as expected here.
1. I suppose you changed the diff.lua via the Options/Controls screen, correct?
2. can you show the Options/Controls with the wheelbrake lines?
3. Does the diff.lua still look like the screen copy in your post above?

Note: changing the "default.lua" is not a lasting solution. It will be restored to the stock file content with every update or repair. Making a backup copy doesn't help as this module is in very early early access, and there will be changes + additions to this file which you will miss when you restore from your backup copy.

Edited by LeCuvier

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...