illern Posted December 20, 2018 Posted December 20, 2018 Hi! In the keyboard/default.lua there are multiple keybinds on the same keys. They make those action not usable. If you remove the default keys(inside game) then it doesn´t matter what you assign because they become red in the list. I have to change them in default.lua to get them to work. But everytime we get an update I have to change them again. I change 3408(parking brake) to V and 3010(select data cartridge down) to X They are free. Also it would be nice if the quotations where the same kind so it is easier to search for duplicates. As of now both " and ' are used. {combos={{key='W',reformers={'LCtrl','LAlt'}}},down = 3408, cockpit_device_id = devices.FLIGHTDATAUNIT, value_down =1.0, name = _('Parking brake'), category = _('Flight Control')}, {combos = {{key = "W", reformers = {"LAlt","LCtrl"}}}, down = 3969, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1.0, name = _("Weapon selector turn counterclockwise"), category = _("Weapons")}, {combos = {{key = 'C', reformers = {'LCtrl', "LAlt"}}},down = 3010, value_down = -1.0, cockpit_device_id = devices.NAVIGATIONPANEL, name = _('Select Data Cartridge - Down'), category = _('Navigation')}, {combos = {{key = "C", reformers = {"LAlt","LCtrl"}}}, down = 3314, cockpit_device_id = devices.WEAPON_SYSTEM, value_down = 1.0, name = _("IR-missile uncage"), category = _("Weapons")}, Win10Prox64, Gigabyte Z390 Aorus Pro, Intel i7-9900K@5,1GHz, 32Gb DDR4 GSkill TridentZ@3900GHz, Gigabyte RTX 2080ti Xtreme 11Gb, Game on Samsung M2 960 Pro, TM WH HOTAS, TM TPR , HP Reverb Pro G1, TM MFD
Fisherman82 Posted May 12, 2019 Posted May 12, 2019 (edited) I thought I would add keybinds for emergency yaw trim since that was missing, I then noticed that there where many errors in the default keybinds, this is just some examples: There is no one for passive radar mode off Altimeter settings are missing and duplicate and wont work even work for some reason if you remove the duplicate AFK lever is duplicate and vill only engage the AFK, you cant disengage Many things link to the wrong item, dont remember whitch one now but there was one thing that was linking to the radar stick incorrectly There where some error regarding a radio base or group selector, dont remember exactly I came to the conclusion that it was to much for me to try to fix I must wait for Heatblur The switch for Nödtrim Tipp does not move to Bakt when you try to trim the emergency trim up using keybinds. Minor thing perhaps but wierd since the connector PNT 389 shuld move to -1.0 according to the keybinds. Skickat från min D5503 via Tapatalk Edited May 12, 2019 by Fisherman82
TOViper Posted May 13, 2019 Posted May 13, 2019 I thought I would add keybinds for emergency yaw trim since that was missing, I then noticed that there where many errors in the default keybinds, this is just some examples: There is no one for passive radar mode off Altimeter settings are missing and duplicate and wont work even work for some reason if you remove the duplicate AFK lever is duplicate and vill only engage the AFK, you cant disengage Many things link to the wrong item, dont remember whitch one now but there was one thing that was linking to the radar stick incorrectly There where some error regarding a radio base or group selector, dont remember exactly I came to the conclusion that it was to much for me to try to fix I must wait for Heatblur The switch for Nödtrim Tipp does not move to Bakt when you try to trim the emergency trim up using keybinds. Minor thing perhaps but wierd since the connector PNT 389 shuld move to -1.0 according to the keybinds. Skickat från min D5503 via Tapatalk I am pretty sure Cobra and RagnarDa already know about all the errors in the keybindings. I hope they repair them soon, I am getting old backing up and restoring my keybinding files after each update. Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
Fisherman82 Posted May 13, 2019 Posted May 13, 2019 Yeah I know, I was just listing what I saw in case something had not been noticed before, that Nödtrim Tipp not going to Bakt despite that it seems to execute the command is a real shady one to find Skickat från min D5503 via Tapatalk
TOViper Posted May 13, 2019 Posted May 13, 2019 Yeah I know, I was just listing what I saw in case something had not been noticed before, that Nödtrim Tipp not going to Bakt despite that it seems to execute the command is a real shady one to find Skickat från min D5503 via Tapatalk seems you mean this one here: https://forums.eagle.ru/showthread.php?t=216089&highlight=emergency+trim Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
Fisherman82 Posted May 13, 2019 Posted May 13, 2019 Yes that one, you beat me to it Skickat från min D5503 via Tapatalk
Devrim Posted September 5, 2019 Posted September 5, 2019 This issue still exists and it's very confusing. One command (same function) can be viewed in two different category by typing category names at the end of the command line in default.lua category = {_('category1'), _('category2')} Why doesn't H.B. do that?.. Intel i7-14700@5.6GHz | MSI RTX4080 SuperSuprimX | Corsair V. 64GB@6400MHz. | Samsung 1TB 990 PRO SSD (Win10Homex64) Samsung G5 32" + Samsung 18" + 2x8"TFT Displays | TM Warthog Stick w/AVA Base | VPC MongoosT-50CM3 Throttle | TM MFD Cougars | Logitech G13, G230, G510, PZ55 & Farming Sim Panel | TIR5 & M.Quest3 VR >>MY MODS<< | Discord: Devrim#1068
Tippis Posted September 20, 2019 Posted September 20, 2019 Yes, still around and still causing problems. Having just gotten done a controller hardware, I had to rebind a lot of things anyway and thought I'd take the opportunity to update a few other controls as well. Instead, I noted that a ridiculous number of binds are marked duplicate/yellow even just using the defaults, and assigning anything to them is completely hit or miss if it will work or not. I am now unable to change kneeboard pages, which is… not ideal in the Viggen. ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
TOViper Posted September 21, 2019 Posted September 21, 2019 Yes, still around and still causing problems. Having just gotten done a controller hardware, I had to rebind a lot of things anyway and thought I'd take the opportunity to update a few other controls as well. Instead, I noted that a ridiculous number of binds are marked duplicate/yellow even just using the defaults, and assigning anything to them is completely hit or miss if it will work or not. I am now unable to change kneeboard pages, which is… not ideal in the Viggen. I think I understand your problem, and I think I have it too from time to time, mostly when flying in VR. I posted my problem here a time ago: https://forums.eagle.ru/showthread.php?t=246283 No response from anyone so far. Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
Tippis Posted September 21, 2019 Posted September 21, 2019 Yup. Sounds like the same — or at least a very closely related — issue. Granted, I think this may be a ED level problem and I think it started when they made the Big Keybind Revamp a while back (in February?) that they had to roll back. All kinds of binds have been all kinds of broken ever since, with these duplicate-by-default errors popping up everywhere. ❧ ❧ Inside you are two wolves. One cannot land; the other shoots friendlies. You are a Goon. ❧ ❧
TOViper Posted October 2, 2019 Posted October 2, 2019 I am also still having this issue. Kneeboard commands are sometimes orange. After restarting DCS it works again. Visit https://www.viggen.training ...Viggen... what more can you ask for? my computer: AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1
Eldur Posted October 9, 2019 Posted October 9, 2019 Noticed this as well today with the kneeboard keys (prev/next page). They were mapped to the [ ] keys, but wouldn't work., then I checked the settings and saw they were mapped correctly, but in orange font and with a double entry. One that just would take keyboard inputs, the other just joysticks and alikes. So I tried mapping those to my stick base buttons, which, as opposed to the keyboard bindings, then did work. Tried finding out why there are separate bindings, but couldn't find any clue. Both input lua files load up common_joystick_binding and common_keyboard_binding respectively, and in both of them the bommands are as follows (only difference being the combos block for the keyboard file to have that default binding): {down = 3001 , cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Next Page') , category = _('Kneeboard')}, {down = 3002 , cockpit_device_id = kneeboard_id, value_down = 1.0, name = _('Kneeboard Previous Page'), category = _('Kneeboard')}, In both files, above kneeboard_id is defined by: local kneeboard_id = 100 if devices and devices.KNEEBOARD then kneeboard_id = devices.KNEEBOARD end So the only real difference that I can find is this: local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") local res = external_profile("Config/Input/Aircrafts/common_keyboard_binding.lua") dofile(folder.."../../Cockpit/Scripts/devices.lua") dofile(folder.."../../Cockpit/Scripts/command_defs.lua") In the Cockpit/Scripts/devices.lua the kneeboard is defined as follows, which is just being processes by the keyboard file, so I suspect that there lies the culprit: devices["KNEEBOARD"] = 100--counter()
Wintermute74 Posted October 24, 2019 Posted October 24, 2019 Please try changing the order of the top three rows in your AJS37/Input/keyboard/default.lua file (as shown below) and respond if it resolves the problem. It did for me, although I'm still not sure why it avoids the duplicates being formed. :huh: dofile(folder.."../../Cockpit/Scripts/devices.lua") dofile(folder.."../../Cockpit/Scripts/command_defs.lua") local res = external_profile("Config/Input/Aircrafts/common_keyboard_binding.lua") The topic is also being discussed in other threads in the forum, e.g. https://forums.eagle.ru/showthread.php?t=250653 Major Wintermute :joystick: PC: i7 4770K - ASUS Z97 Deluxe - 16 Gb RAM - Nvidia GTX 1080 - 27" BenQ XL2720Z - HOTAS Warthog - TPR Pendular Rudder Pedals - MFD Cougar pack - TrackIR 5 DCS Modules: AJS-37 Viggen - A-10C I/II Warthog - F-16C Viper - F-14B Tomcat - F/A-18C Hornet - Su-33 Flanker-D - Su-25 Frogfoot - P-51D Mustang [sIGPIC][/sIGPIC]
Recommended Posts