Bind a button to autopilot altitude hold.

[ScottyBS]

Hi,

 

Great module really enjoying it.

 

I seem to have an issue with binding a joystick button to the Autopilot Altitude hold. I can click the switch and get it to hold but when I push the button on my joystick to hold it shows altitude quickly on the control position indicator but then disappears and doesnt lock.

 

Any ideas?

 

Scott

[Mud]

Yeah, it seems you actually have to set that one to a toggle switch rather. I've set mine to the AP of my Warthog.

[HoneyBadger]

I've set Altitude and Speed to the Autopilot 3 position switch on my Warthog. Works very well as the Gazelle can read the center of the switch as off just like the in-game switch.

[ScottyBS]

ok - thanks

 

good to see great community support too...

[Fishbreath]

I set two buttons on my hat to AP mode switch up and AP mode switch down. Mode up gets me to altitude AP, 2x mode down gets me to speed AP, one tap away from either position goes back to neutral.

[bart]

I've set Altitude and Speed to the Autopilot 3 position switch on my Warthog. Works very well as the Gazelle can read the center of the switch as off just like the in-game switch.

 

This is what I did, first time I tried it I noticed it copied the function of the in-game switch perfectly......nice touch Polychop :thumbup:

[Fakum]

Im searching for a resolve to this, this is a thread that, although old, its relevant. Both the Altitude Hold and Speed Hold work fine if you click on it in the cockpit. However, if you press the key bindings for either from the keyboard, they only switch position for a second and the switch returns to center position. This action is creating havoc for me with my Cougar Hotas & Foxy software. I know people will try and tell me to switch to Target software, but if I were just using the keyboard, I would imagine when you hit the key command for it, it would hold? I dont see a command for the center position, otherwise I could program it easily. Please help, thanks.

[davidp57]

It works well when assigned to a 3-position switch.

[Chic]

With VoiceAttack you can program a button or switch to hold a key press. Key is released with another push of the button.

[Gizzy]

With VoiceAttack you can program a button or switch to hold a key press. Key is released with another push of the button.

 

 

Personally I would not hold, or use software to hold, a keyboard character down for any significant time period. It can play havoc with some keyboard buffers and disallows that key to be used with any modifier.

 

Hi,

Any ideas?

Scott

 

 

Im searching for a resolve to this, this is a thread that, although old, its relevant. ...... Please help, thanks.

 

The PC SA342 bindings have been made for latching toggle switches that normally are engaged via DX codes which is perfect. TARGET software will allow you to enagage DX codes to latching or momentary switches in any manner you wish... however realising you do not want to use TARGET (and I get that - its a bit buggy with me anyway) there is another way.

 

Edit your C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\SA342\Input\keyboard\default.lua and add these lines...

 

{down = device_commands.Button_9, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 0.0,name = _('Autopilot  Altitude Mode'), category = _('MODDED')},
{down = device_commands.Button_19, cockpit_device_id = devices.AUTOPILOT, value_down = -1, value_up = 0.0,name = _('Autopilot  Speed Mode'), category = _('MODDED')},
{down = device_commands.Button_19,  up = device_commands.Button_20, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 1,name = _('Autopilot  Sp/Alt Cancel'), category = _('MODDED')},

and you will have a couple of extra bindings for your keyboard under the category 'MODDED'.

 

Assign spare keys to these, say, LSHIFT + A - LSHIFT + B - LSHIFT + C and you're done.

 

'Momentarily' engaging these bindings will move the switch to the relevent positions AND they will stay there... :)

 

Best to have this edit as a MOD as each DCS update deletes the changes.

 

If you wish I could easily make up a OvGME or JSGME small MOD if you are unsure.

 

Hope this helps...

Edited February 21, 2019 by Gizzy

[Fakum]

Well, I solved the issue. 1st off, I found in a bug report that should not use the Altitude and Speed hold outside of clicking the switch from your mouse in the cockpit. If you wish to bind that function to a HOTAS, you are to use the MODE up/MODE down. This certainly worked and I implemented it to my profile and it works just fine.

 

 

BTN T7 /I

/O /P Mode_Down /R Mode_Up

BTN T8 /I

/O /P Mode_Up /R Mode_Down