Sokol1_br Posted March 8, 2019 Posted March 8, 2019 Just add the lines "ICommandMenuItem1... in -- Communication section of joystick default.LUA, after the last existing entry, that is _('COMM Push to talk'), -- Communications {down = iCommandPlaneDoAndHome, name = _('COMM Dispatch wingmans - complete mission and RTB (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneDoAndBack, name = _('COMM Dispatch wingmans - complete mission and rejoin (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneFormation, name = _('COMM Toggle formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneJoinUp, name = _('COMM Join up formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneAttackMyTarget, name = _('COMM Attack my target (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneCoverMySix, name = _('COMM Cover me (easy communication only)'), category = _('Communications')}, {down = iCommandAWACSHomeBearing, name = _('COMM Ask AWACS home airbase (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageGroundTargets, name = _('COMM Attack Ground Targets (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageAirDefenses, name = _('COMM Attack Air Defenses (easy communication only)'), category = _('Communications')}, {down = iCommandToggleCommandMenu, name = _('COMM Communication menu'), category = _('Communications')}, {down = ICommandSwitchDialog, name = _('COMM Switch dialog'), category = _('Communications')}, {down = ICommandSwitchToCommonDialog, name = _('COMM Switch to main menu'), category = _('Communications')}, {down = iCommandPlane_P_51_PTT_on, up = iCommandPlane_P_51_PTT_off, name = _('COMM Push to talk'), category = _('Communications')}, {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('Communications')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('Communications')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('Communications')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('Communications')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('Communications')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('Communications')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('Communications')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('Communications')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('Communications')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('Communications')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('Communications')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('Communications')}, -- View
Mr_Burns Posted March 8, 2019 Posted March 8, 2019 Im thinking of hardwiring this voice commands option into my sons XBOX, then when he randomly loses it and the neighbours can hear him shout "FCUK" at the top of his voice, his XBOX will shut down. Thanks for the suggestion. How do you tell voice commands what to do, do you just record F1-F12 and "Backspace" into viacom and map it to F1-12 / etc?
Drac Posted March 8, 2019 Posted March 8, 2019 Im thinking of hardwiring this voice commands option into my sons XBOX, then when he randomly loses it and the neighbours can hear him shout "FCUK" at the top of his voice, his XBOX will shut down. Thanks for the suggestion. How do you tell voice commands what to do, do you just record F1-F12 and "Backspace" into viacom and map it to F1-12 / etc? You can set "Menu" and "Foxtrot One...Foxtrot Two...Foxtrot Three...etc" via Voiceattack. Then you can say "Menu"..."Foxtrot One"...Foxtrot Six...etc" as an example. This could be a backup if all else fails.
fitness88 Posted March 8, 2019 Author Posted March 8, 2019 Just add the lines "ICommandMenuItem1... in -- Communication section of joystick default.LUA, after the last existing entry, that is _('COMM Push to talk'), -- Communications {down = iCommandPlaneDoAndHome, name = _('COMM Dispatch wingmans - complete mission and RTB (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneDoAndBack, name = _('COMM Dispatch wingmans - complete mission and rejoin (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneFormation, name = _('COMM Toggle formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneJoinUp, name = _('COMM Join up formation (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneAttackMyTarget, name = _('COMM Attack my target (easy communication only)'), category = _('Communications')}, {down = iCommandPlaneCoverMySix, name = _('COMM Cover me (easy communication only)'), category = _('Communications')}, {down = iCommandAWACSHomeBearing, name = _('COMM Ask AWACS home airbase (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageGroundTargets, name = _('COMM Attack Ground Targets (easy communication only)'), category = _('Communications')}, {down = iCommandPlane_EngageAirDefenses, name = _('COMM Attack Air Defenses (easy communication only)'), category = _('Communications')}, {down = iCommandToggleCommandMenu, name = _('COMM Communication menu'), category = _('Communications')}, {down = ICommandSwitchDialog, name = _('COMM Switch dialog'), category = _('Communications')}, {down = ICommandSwitchToCommonDialog, name = _('COMM Switch to main menu'), category = _('Communications')}, {down = iCommandPlane_P_51_PTT_on, up = iCommandPlane_P_51_PTT_off, name = _('COMM Push to talk'), category = _('Communications')}, {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('Communications')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('Communications')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('Communications')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('Communications')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('Communications')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('Communications')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('Communications')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('Communications')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('Communications')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('Communications')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('Communications')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('Communications')}, -- View I've tried as close as I can to what you suggested but with no success. You have now changed the code from your first post. I don't have the same code to follow like you have in your default.lua file. Attached is my default.lua please put the code in so I see where you are talking about and color the code red so I can easily find it. default.lua Thanks again.default.lua
Sokol1_br Posted March 8, 2019 Posted March 8, 2019 I change the code because I move "Menu Items" from General to Communications category, just for convenience. But test your attached code with lines added - option for set joystick buttons for "menu items" will appear in General - don't find Communications category in this plane. I don't have this module to test. https://forums.eagle.ru/attachment.php?attachmentid=205929&stc=1&d=1552072108default.lua
fitness88 Posted March 8, 2019 Author Posted March 8, 2019 I replaced the DCS file with yours into DCS World OpenBeta\Mods\aircraft\FA-18C\Input\FA-18C\joystick/default.lua Unfortunately it still does not show up in the controls options under the 'General' or the 'All' drop down options. controls.JPG --------------------------------------------- -- General ---------------------------------- --------------------------------------------- { down = iCommandCockpitShowPilotOnOff, name = _('Show pilot body'), category = _('General')}, { down = iCommandPlaneShipTakeOff, name = _('Catapult Hook-Up'), category = _('General')}, { 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')},
Sokol1_br Posted March 9, 2019 Posted March 9, 2019 Perhaps something in LUA change for this new plane... If you make a test with TF-51D can confirm. The only jet I have installed is MiG-21, test with then too and work. By "test" I mean start a mission and use COMM pressing stick buttons.
ron533 Posted March 9, 2019 Posted March 9, 2019 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. Ive been using this mod once for the very reasons you mentioned, was very good... https://forums.eagle.ru/showthread.php?t=187330 Give it a try. Callsign SETUP
fitness88 Posted March 9, 2019 Author Posted March 9, 2019 Ive been using this mod once for the very reasons you mentioned, was very good... https://forums.eagle.ru/showthread.php?t=187330 Give it a try. Thanks for the info but is this mod still functional? I went to the link, it's quite old and there are lots of confusion/questions.
fitness88 Posted March 9, 2019 Author Posted March 9, 2019 Perhaps something in LUA change for this new plane... If you make a test with TF-51D can confirm. The only jet I have installed is MiG-21, test with then too and work. By "test" I mean start a mission and use COMM pressing stick buttons. I appreciate your effort Sokol1_br...thanks.
Sokol1_br Posted March 9, 2019 Posted March 9, 2019 (edited) Thanks for the info but is this mod still functional? I went to the link, it's quite old and there are lots of confusion/questions. Still working, I did a test - had some occasional unwanted F-12 view camera. Like author say is for guys that want keep hands ON stick or throttle, although seems nice at start, navigate between F1 and F12 - e.g select an ATC, with HAT became boring fast. :D Since is an external program - an AutoHotKey script, use ~2/3% of CPU; IMHO better use Voice Attack. Edited March 10, 2019 by Sokol1_br
fitness88 Posted March 9, 2019 Author Posted March 9, 2019 Well if I'm going to go back using software, I'll use the X52 pro SST that works fine for the F1 issue.
Recommended Posts