Jump to content

Recommended Posts

Posted

Hello,

 

 

Since DCS doesn't allow you to bind separate commands for switch press and release, the Special For Joystick commands are essential. However, I find it confusing that while the roll AP switch has them, the pitch AP does not; similarly, the Master Arm has one, but the Laser Arm does not. Please add commands for these switches (or allow us to bind keypress and keyrelease to different commands ourselves).

Gigabyte GA-Z170X-Gaming 7, i5 6600K @3.5ghz, GTX 1070, 16GB ram, Windows 10 Home x64 https://pcpartpicker.com/b/JH9J7P

 

Modules: A-10C, FC3, F/A-18C, UH-1H, MI-8MTV2, Ka-50, SA342, AJS-37, AV-8BNA, M-2000C, MiG-21, F-14A/B, JF-17, F-16C, Supercarrier

Maps: Caucasus, NTTR, Persian Gulf

 

Awaiting: DCS: F-15E

Posted

while its not hard to do them on your own, its a bit of a pain to restore them after every update since the file gets overwritten even if there is no change.

 

+1

  • 4 weeks later...
Posted

You can add these two lines in Dcs World\Mods\aircraft\F-16C\Input\F-16C\joystick\default.lua

 

{ 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 / A/P OFF (Multi-pos switch)'), category = {_('Instrument Panel'), _('FLCS')}},

{ down = control_commands.ApPitchAtt_EXT, up = control_commands.ApPitchAtt_EXT, cockpit_device_id = devices.CONTROL_INTERFACE, value_down = -1.0, value_up = 1.0, name = _('Autopilot PITCH Switch - ATT HOLD / A/P OFF (Multi-pos switch)'), category = {_('Instrument Panel'), _('FLCS')}},

Posted (edited)

Can the middle line be correct (which is currently DCS standard):

 


{down = control_commands.ApPitchAlt_EXT,			up = control_commands.ApPitchAlt_EXT,			cockpit_device_id = devices.CONTROL_INTERFACE,	value_down =  1.0,	value_up = 0.0,	name = _('Autopilot PITCH Switch - ALT HOLD'),		category = {_('Instrument Panel'), _('FLCS')}},
{down = control_commands.ApPitchAlt_EXT,															cockpit_device_id = devices.CONTROL_INTERFACE,	value_down = -1.0,					name = _('Autopilot PITCH Switch - A/P OFF'),		category = {_('Instrument Panel'), _('FLCS')}},
{down = control_commands.ApPitchAtt_EXT,			up = control_commands.ApPitchAtt_EXT,			cockpit_device_id = devices.CONTROL_INTERFACE,	value_down = -1.0,	value_up = 0.0,	name = _('Autopilot PITCH Switch - ATT HOLD'),		category = {_('Instrument Panel'), _('FLCS')}},

 

I think the -1.0 for value_down can't be correct ... any thoughts about it?

Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G 4.4 GHz | NVIDIA RTX 3080 10GB | 32 GB 3.2 GHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TRP | Rift CV1

 

Posted
while its not hard to do them on your own, its a bit of a pain to restore them after every update since the file gets overwritten even if there is no change.

 

+1

If new commands could somehow be written in the .diff.lua it would make it more practical to create and persist custom controls from version to version.

Posted
If new commands could somehow be written in the .diff.lua it would make it more practical to create and persist custom controls from version to version.

 

That would be awesome. But currently i dont think it works that way.

Posted

How about including 'press' and 'release' as modifiers for all setups. This would satisfy many threads I have researched as well as rounding out perfect native support for every controller available (sic).

 

I admit I have no idea how easy this is to do.

 

Sent from my SM-G975F using Tapatalk

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...