Mt5_Roie Posted November 30, 2015 Posted November 30, 2015 Is it possible to map a button to a radio button (F1-F12) to use for radio communications? I built a panel recently with a phone like pad of 12 buttons plus one on the top. The top one activates the radio commands (i.e "\"). But if i try to map the F1 to the next button, it always maps to cockpit view. F2 always goes to external view. It won't use them for the radio communications. Is there a way to assign buttons to work like the keyboard F2 in that when radio communications is not up it acts for views, but when its up it acts for radio communications? If not, is it just possible to map those buttons for the radio communications...don't really need to views anyways since I tend to fly with the oculus rift on. Coder - Oculus Rift Guy - Court Jester
BravoYankee4 Posted November 30, 2015 Posted November 30, 2015 For that you would need some kind of macro/script. Search for autohotkey (AHK). Or try out the Vaicom software with the voice attack profiles available. Haven't tried it myself yet, but it seems good.
Mt5_Roie Posted November 30, 2015 Author Posted November 30, 2015 Looks like Autohotkey should be able to map it....thanks! Will test and let you know. For that you would need some kind of macro/script. Search for autohotkey (AHK). Or try out the Vaicom software with the voice attack profiles available. Haven't tried it myself yet, but it seems good. Coder - Oculus Rift Guy - Court Jester
NeilWillis Posted November 30, 2015 Posted November 30, 2015 Another possibility is Voice Attack or something similar, though you might find shouting EFF ONE! at your computer may raise a few eyebrows at home. Everyone here thinks I've lost it completely!
Mt5_Roie Posted November 30, 2015 Author Posted November 30, 2015 Well, that would require a working mic. My cat recently found it funny to chew on my Astro A40 cord...so no mic or cool audio until I get that replaced. But ideally would like to use the buttons on the panel I created...since that what I designed them for. Another possibility is Voice Attack or something similar, though you might find shouting EFF ONE! at your computer may raise a few eyebrows at home. Everyone here thinks I've lost it completely! Coder - Oculus Rift Guy - Court Jester
Sokol1_br Posted November 30, 2015 Posted November 30, 2015 roiegat I try something similar with HAT and XPadder, but find the same problem: I am no able to remap the F- keys used for radio for exclusive, so the cameras are activated together. A workaround was remap the camera F- keys with modifier, but after more than 15 years using F-1, F-2... for cameras is PITA remember the modifiers :( And, the bug (?) after announce "Inbound" - when the radio menu "magically" open again - is boring. Anyway after get used I can handle the COMM without look at messages on screen. Above, the clicks sequence open the COMM menu (with CapsLock key so their LED inform that COMM are "ON"), select Ground Crew, request "External electric power, close the COMM. What require 6 "layers" in XPadder. No macro involved, just memory. :D
Hansolo Posted November 30, 2015 Posted November 30, 2015 (edited) That might work. I have my F-keys swapped for the number on numeric keyboard by changing the lua file. Haven't though of changing them for a joystick though. I'll post the lua file a little later then that may help you Edit, have attached the lua file. perhaps the icommands can be included in one of the joystick lua files so you can map them cheers HansConfig.rar Edited November 30, 2015 by Hansolo Attached file 1 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Mt5_Roie Posted December 5, 2015 Author Posted December 5, 2015 HMA Your information led to the fix! I had to modify it bit but it worked. So far just tested it on L-39 but will test on the other aircraft as well. So what I did was go into MOD/Aircraft/L39/Input/Joystick and add the following to the general section: {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('General')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('General')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('General')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('General')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('General')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('General')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('General')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('General')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('General')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('General')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('General')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('General')}, Then I went into the sim and was able to map the buttons to the radio commands. So excited about this. Big huge thanks! Coder - Oculus Rift Guy - Court Jester
Hansolo Posted December 6, 2015 Posted December 6, 2015 You are most welcome. Glad to be pointing you in the right direction :-) Cheers Hans 132nd Virtual Wing homepage & 132nd Virtual Wing YouTube channel My DCS-BIOS sketches & Cockpit Album
Sokol1_br Posted December 7, 2015 Posted December 7, 2015 Nice, tested here, both keys o joy buttons method work fine. :thumbup:
Recommended Posts