Moxica Posted November 12, 2022 Posted November 12, 2022 Is there a way to activate the middle position (off)? It won't bind.. ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - Pimax crystal light - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar - Audient EVO8
tomcat_driver Posted November 12, 2022 Posted November 12, 2022 Yes, but it requires third party software and can be unreliable. The best solution is to use the provided DCS keybind options like: Up = Path > Else Alt/Hdg Down = Alt > Else Alt/Hdg If your module doesn't have those you can wishlist ED to create these keybinds. You can also create custom keybinds if you can code some lua; there's a thread about this in the forums, but you'll have to search for it cause I don't have it here, sorry. 1
LeCuvier Posted November 12, 2022 Posted November 12, 2022 (edited) Unless you choose to go down the "wishlist" path (good luck!), there are two solutions: 1. Use TARGET Thrustmaster's software (which I have stopped using so I cannot provide details but it's not difficult) 2. Edit the "default.lua" adding these two lines of code: {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, I bind (Pitch Autopilot) Altitude Hold to the upper position (PATH) and Attitude Hold to the down position (ALT). The middle position switches the Autopilot to OFF, no binding required. Link to tutorial for editing this file: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu Edited November 12, 2022 by LeCuvier 2 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
Moxica Posted November 12, 2022 Author Posted November 12, 2022 (edited) 8 hours ago, LeCuvier said: Unless you choose to go down the "wishlist" path (good luck!), there are two solutions: 1. Use TARGET Thrustmaster's software (which I have stopped using so I cannot provide details but it's not difficult) 2. Edit the "default.lua" adding these two lines of code: {down = control_commands.ApPitchAlt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = 1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ALT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, {down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAlt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = -1.0, name = _('Autopilot PITCH Switch ATT HOLD/OFF'), category = {_('Instrument Panel'), _('FLCS')}}, I bind (Pitch Autopilot) Altitude Hold to the upper position (PATH) and Attitude Hold to the down position (ALT). The middle position switches the Autopilot to OFF, no binding required. Link to tutorial for editing this file: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu I could not get that to work.. Tried to paste it under a couple of sections in default.lua; No joy. (Pun intended) Edited November 12, 2022 by Moxica ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - Pimax crystal light - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar - Audient EVO8
rob10 Posted November 13, 2022 Posted November 13, 2022 You're not seeing the new bindings in your bindings? what section you have it under does matter. Double check that you're not missing a character or have an extra character and you have it in the correct file.
Solution LeCuvier Posted November 13, 2022 Solution Posted November 13, 2022 13 hours ago, Moxica said: I could not get that to work.. Tried to paste it under a couple of sections in default.lua; No joy. (Pun intended) 1. I'm referring to the file "default.lua" under "K:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" (K being the Drive). 2. The best place for adding key commands is just below these lines at the top of the file so you can easily find your edits. local cockpit = folder.."../../../Cockpit/Scripts/" dofile(cockpit.."devices.lua") dofile(cockpit.."command_defs.lua") local res = external_profile("Config/Input/Aircrafts/common_joystick_binding.lua") join(res.keyCommands,{ 3. Make sure you don't miss any of the commas, parentheses, curly braces. Syntax errors may invalidate the entire file 4. Use a program editor like Notepad++ (no office program!) 2 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
Moxica Posted November 13, 2022 Author Posted November 13, 2022 Aha! I found (Pitch Autopilot) Altitude Hold/off. That worked. Thank you so much! ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - Pimax crystal light - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar - Audient EVO8
Recommended Posts