Kongamato Posted May 6, 2019 Posted May 6, 2019 I´m trying to map the knobs of the lights (beacon, flood, warn test, formation, console, etc.) in the keyboard, but it seems they don´t work. I don´t have problems with other rotatory knobs mapped in the keyboard (radar range, radar mode, the ones of the UHF radio and TACAN, etc.) and I there are no problems with mapping the rotatory knobs of the lights in an axe of the hotas. Is it a bug? Other people have the same problem?
LeCuvier Posted May 6, 2019 Posted May 6, 2019 I wonder why you even need to bind these commands to the keyboard. I have checked for Open Beta, and all these commands have default bindings to the keyboard. See attached picture. 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
Kongamato Posted May 7, 2019 Author Posted May 7, 2019 (edited) I wonder why you even need to bind these commands to the keyboard. I have checked for Open Beta, and all these commands have default bindings to the keyboard. See attached picture. Are you really asking why people could prefer to map the increment of a rotatory knob as "P" instead of the default "Right AltGr + Right Control + P"? What are you going to ask next? Why I prefer to map the rotatories and don't use the mouse? I´m asking about a possible and particular bug. If you have information about that and want to help, thank you very much. If not, please, don´t change the subjet of this thread. Anyway, it doesn´t matter. The default mapping of the panel of the lights in the right console doesn´t work for me neither. The taxi and landing lights switch, outside that panel, can be mapped, but the one of the beacon, inside that panel, can´t be. I can map all of them in the buttons of the HOTAS however. Someone have the same problem? Edited May 7, 2019 by Kongamato
LeCuvier Posted May 7, 2019 Posted May 7, 2019 (edited) You did not say that you want to re-map the commands so I assumed you were trying to map from scratch. Anyway, I was just trying to help, no need for you to get upset. And yes, I certainly I wouldn't want to use commands like RCtrl & RAlt & P myself. I can't even remember most of the single-key commands... However, just for fun, I have changed the command for the beacon light to just "p" and that works fine for me (in Open Beta). So it's not a general bug. Personally, I have modified the default.lua to get distinct ON/OFF commands (not toggle) with single ON/OFF switches on my button box. So with one ON/OFF switch I can switch the respective light between 0% (=Off) and 100% (=ON). Edit: P works in the stable version too. Edited May 7, 2019 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
Kongamato Posted May 7, 2019 Author Posted May 7, 2019 I sincerely apologize. English is my second language and probably I misunderstood you. I thought that you wasn't trying to help, but to start one of those byzantine discussions about "Why you do this your way? Do that my way" There are quite a lot of them in this forum. Thank you very much for the information. I´m trying to do an ultra cheap "cockpit" of the F-5 just labeling an old keyboard with the rotatories and the most important switches and that specific panel of lights of the right console is the only one doesn´t work, and since you say it´s not a general bug, I don´t know what is hapening. I suppose I have to do more tests.
LeCuvier Posted May 7, 2019 Posted May 7, 2019 ... just labeling an old keyboard with the rotatories and the most important switches... That sounds like a good idea and is much cheaper than a butto box. I must try that! About your problem, I really can't see why just the lighting commands don't work. You have not modified any of the .lua files I suppose? Still, it might be worth running a repair before anything else - if you haven't already done that. 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
Kongamato Posted May 8, 2019 Author Posted May 8, 2019 That sounds like a good idea and is much cheaper than a butto box. I must try that! About your problem, I really can't see why just the lighting commands don't work. You have not modified any of the .lua files I suppose? Still, it might be worth running a repair before anything else - if you haven't already done that. I saw this keyboar for FSX and I though "I can make one of this by myself for DCS with my printer". I select one of the buttons of the HOTAS as "modifier" (one of the triggers, but can be any button) and asign one key of the keyboard as "increment" of any rotatory, an the same key + the trigger as "decrement" of the same rotatory. This way I can map in the keyboard and the HOTAS abou 90% of the commands of the F-5E. You can´t do that with all the planes because you need a lot of keyboards, but it´s a good idea with your favorite plane. About my problem, after running the repair and get nothing, I have unistalled and reinstalled DCS, the "Open Beta" version this time, and it works fine now.
Recommended Posts