fitness88 Posted March 2, 2019 Posted March 2, 2019 (edited) I am looking for a way to map the 'F1-F12' keys that control the comms menu and sub-menu to my HOTAS without using keyboard mapping software. However when mapping directly through DCS the 'F1-F12' keys open 'views' and do not control the comms menu. Is there a way without keyboard mapping software to map the comms menu? Thank you. Edited March 2, 2019 by fitness88 spelling
Svsmokey Posted March 2, 2019 Posted March 2, 2019 May i suggest avoiding immersion-breaking comms menus altogether ? Vaicom Pro and Voiceattack allow a much more realistic AI comms experience . 9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2
Supmua Posted March 2, 2019 Posted March 2, 2019 Target or Joystick Gremlin works for me, but these are external software. 1 PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
fitness88 Posted March 2, 2019 Author Posted March 2, 2019 It's interesting when the comms menu is open, 'F1-F12' keyboard commands will command the comms menu and when closed will command the 'View' but 'F1-F12' commands through DCS only commands 'View' and ignores the comms menu when it's open. I have all the software I need, I've used Saitek and Target in the past but have now mapped all commands through DCS and don't want to start with the software again only for this one issue if I don't have to but will if I have to. 1
fitness88 Posted March 2, 2019 Author Posted March 2, 2019 May i suggest avoiding immersion-breaking comms menus altogether ? Vaicom Pro and Voiceattack allow a much more realistic AI comms experience . I never thought of voice commands as an option, I'm not really into talking.
RustBelt Posted March 3, 2019 Posted March 3, 2019 I never thought of voice commands as an option, I'm not really into talking. Same, when I'm playing a game I don't really feel like yelling randomly at a computer. Unless it's like locking up or smoking or something. 1
Svsmokey Posted March 3, 2019 Posted March 3, 2019 Fair enough....i don't like machines talking to me :) 1 9700k @ stock , Aorus Pro Z390 wifi , 32gb 3200 mhz CL16 , 1tb EVO 970 , MSI RX 6800XT Gaming X TRIO , Seasonic Prime 850w Gold , Coolermaster H500m , Noctua NH-D15S , CH Pro throttle and T50CM2/WarBrD base on Foxxmounts , CH pedals , Reverb G2v2
DutchCoolHand Posted March 4, 2019 Posted March 4, 2019 Same, when I'm playing a game I don't really feel like yelling randomly at a computer. Unless it's like locking up or smoking or something. It is not random, you still use the comms switches on the throttle, so not random. I have been adding words as I started flying in VR. I also turned off the player's voice and that really adds to realism 1 AMD RYZEN 7 2700 / 32GB / RTX2070 / 500GB M.2 with Windows and DCS / 2 - 500GB SSD / Rift S/ TM Warthog with F18 stick and Virpil WarBRD / Foxx Mounts/ MFG Crosswind rudders + 3 MFD's | Now enjoying VR with PointCTRL controllers + Gamematrix JetSeat
Supmua Posted March 4, 2019 Posted March 4, 2019 I personally find key bindings to be more efficient than voice commands, which typically takes a few sec to register. With the F keys bound to hat switches I can issues 3 consecutive functions in just 1 second. PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti. Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2 Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon) VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/
RustBelt Posted March 4, 2019 Posted March 4, 2019 It is not random, you still use the comms switches on the throttle, so not random. I have been adding words as I started flying in VR. I also turned off the player's voice and that really adds to realism It's random to anyone else that has to hear me jibbering to my computer in a 1 way conversation 1
Sokol1_br Posted March 4, 2019 Posted March 4, 2019 (edited) fitness88 You need edit LUA for change radio COMM from F1-F12 to joy buttons. https://forums.eagle.ru/showpost.php?p=2585963&postcount=8 But since is need edit for each module - redo in game updates... I think that for this case an simple to set keymapper (JoyToKey, RS mapper..._) just for this function result more practical. Edited March 4, 2019 by Sokol1_br 1
fitness88 Posted March 4, 2019 Author Posted March 4, 2019 fitness88 You need edit LUA for change radio COMM from F1-F12 to joy buttons. https://forums.eagle.ru/showpost.php?p=2585963&postcount=8 But since is need edit for each module - redo in game updates... I think that for this case an simple to set keymapper (JoyToKey, RS mapper..._) just for this function result more practical. Thanks for this, looks like it will get my menu commands to work with whatever keys I want. I'll look it over later...thanks again. 1
Icebeat Posted March 5, 2019 Posted March 5, 2019 I suggested before to have UP, Down and Select commands for the Communications menu (the same as any console game does).
fitness88 Posted March 5, 2019 Author Posted March 5, 2019 I suggested before to have UP, Down and Select commands for the Communications menu (the same as any console game does). Yes I had that before, but once I dropped the HOTAS software comms became inaccessible through DCS, which is too bad. I'll work on what Sokol1_br posted. 1
fitness88 Posted March 5, 2019 Author Posted March 5, 2019 fitness88 You need edit LUA for change radio COMM from F1-F12 to joy buttons. https://forums.eagle.ru/showpost.php?p=2585963&postcount=8 But since is need edit for each module - redo in game updates... I think that for this case an simple to set keymapper (JoyToKey, RS mapper..._) just for this function result more practical. The link gives this file path: MOD/Aircraft/L39/Input/Joystick and add the following to the general section: I don't know what is meant by general section and where to go to change the mapping. 1
Sokol1_br Posted March 6, 2019 Posted March 6, 2019 Think he refer to Hansolo example - attached in previous message (# 7), edit "default.LUA" in ...\Config\Input\CommandMenu\keyboard. return { keyCommands = { {combos = {{key = 'Num1'}}, name = 'Command menu item 1', down = ICommandMenuItem1}, {combos = {{key = 'Num2'}}, name = 'Command menu item 2', down = ICommandMenuItem2}, {combos = {{key = 'Num3'}}, name = 'Command menu item 3', down = ICommandMenuItem3}, {combos = {{key = 'Num4'}}, name = 'Command menu item 4', down = ICommandMenuItem4}, {combos = {{key = 'Num5'}}, name = 'Command menu item 5', down = ICommandMenuItem5}, {combos = {{key = 'Num6'}}, name = 'Command menu item 6', down = ICommandMenuItem6}, {combos = {{key = 'Num7'}}, name = 'Command menu item 7', down = ICommandMenuItem7}, {combos = {{key = 'Num8'}}, name = 'Command menu item 8', down = ICommandMenuItem8}, {combos = {{key = 'Num9'}}, name = 'Command menu item 9', down = ICommandMenuItem9}, {combos = {{key = 'Num0'}}, name = 'Command menu item 10', down = ICommandMenuItem10}, {combos = {{key = 'Num-'}}, name = 'Command menu item 11', down = ICommandMenuItem11}, {combos = {{key = 'Num+'}}, name = 'Command menu item 12', down = ICommandMenuItem12}, {combos = {{key = 'Tab', reformers = {'LShift'}}}, name = 'Command switch dialog', down = ICommandSwitchDialog}, }, } Curious is that I post after in that topic that have tested changing COMM for keypad keys e joystick buttons, and work OK. But now... I don't remember anything about. :megalol:
fitness88 Posted March 6, 2019 Author Posted March 6, 2019 (edited) Think he refer to Hansolo example - attached in previous message (# 7), edit "default.LUA" in ...\Config\Input\CommandMenu\keyboard. return { keyCommands = { {combos = {{key = 'Num1'}}, name = 'Command menu item 1', down = ICommandMenuItem1}, {combos = {{key = 'Num2'}}, name = 'Command menu item 2', down = ICommandMenuItem2}, {combos = {{key = 'Num3'}}, name = 'Command menu item 3', down = ICommandMenuItem3}, {combos = {{key = 'Num4'}}, name = 'Command menu item 4', down = ICommandMenuItem4}, {combos = {{key = 'Num5'}}, name = 'Command menu item 5', down = ICommandMenuItem5}, {combos = {{key = 'Num6'}}, name = 'Command menu item 6', down = ICommandMenuItem6}, {combos = {{key = 'Num7'}}, name = 'Command menu item 7', down = ICommandMenuItem7}, {combos = {{key = 'Num8'}}, name = 'Command menu item 8', down = ICommandMenuItem8}, {combos = {{key = 'Num9'}}, name = 'Command menu item 9', down = ICommandMenuItem9}, {combos = {{key = 'Num0'}}, name = 'Command menu item 10', down = ICommandMenuItem10}, {combos = {{key = 'Num-'}}, name = 'Command menu item 11', down = ICommandMenuItem11}, {combos = {{key = 'Num+'}}, name = 'Command menu item 12', down = ICommandMenuItem12}, {combos = {{key = 'Tab', reformers = {'LShift'}}}, name = 'Command switch dialog', down = ICommandSwitchDialog}, }, } Curious is that I post after in that topic that have tested changing COMM for keypad keys e joystick buttons, and work OK. But now... I don't remember anything about. :megalol: I know what you mean! Thanks DCS World OpenBeta\Config\Input\CommandMenu\keyboard/default.lua is the only file in the folder and matches script. I'll try it out, can I use a modifier like shift in front of the key I choose as I'm running out of empty keys? So to make sure I have it clear...do I change the F1-F12 for any other unused key? Edited March 6, 2019 by fitness88 1
Sokol1_br Posted March 6, 2019 Posted March 6, 2019 Yes, in the above example was use Numpad keys instead F1-F12. Make a backup of your actual default.lua and test with modifier.
fitness88 Posted March 6, 2019 Author Posted March 6, 2019 Yes, in the above example was use Numpad keys instead F1-F12. Make a backup of your actual default.lua and test with modifier. I see there is mention of reformers at the bottom of the script: {combos = {{key = 'Tab', reformers = {'LShift'}}}, name = 'Command switch dialog', down = ICommandSwitchDialog}, }, I suspect reformers is = modifiers, I wonder how the syntax would be using LShift with another key? 1
fitness88 Posted March 7, 2019 Author Posted March 7, 2019 Just tested it, works fine...thanks again!
fitness88 Posted March 7, 2019 Author Posted March 7, 2019 No it doesn't work. The Config\Input\CommandMenu\keyboard/default.lua doesn't map directly to the joy stick it can only reassign the keyboard command to another key which means you would still need a keyboard mapping software...which I have 2 but don't want to use.
fitness88 Posted March 7, 2019 Author Posted March 7, 2019 Why when using the keyboard does F1-F12 work for both comms menu and 'views'...whichever one is active, but when mapped through DCS F1-F12 commands only work for 'views'?
Sokol1_br Posted March 8, 2019 Posted March 8, 2019 (edited) For map in joysticks buttons open the "default.LUA" in MOD/Aircraft/"aircraft name"/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')}, Not sure about "general section", but think is top of "default.LUA" inside joystick folder, where are entries for start procedure cheat. Don't forget to make backup before change.:thumbup: EDIT - Test adding code in plane > joystick and work, and don't affect F1-F12 default assignments. Test changing _('General') with _ ('Communications') and place under ---Communications will be more easy to find for change joy buttons. Tested (offline) OK: Edited March 8, 2019 by Sokol1_br 1
fitness88 Posted March 8, 2019 Author Posted March 8, 2019 Mods\aircraft\FA-18C\Input\FA-18C\joystick/default.lua Please post your default.lua file so I can see exactly what you are doing.
Recommended Posts