Radar antenna elevation a little too sensitive

So when I press the keys for antenna up or down the highest and the lowest scanned altitudes change very quick which makes minor adjustments hard. Is there any way to make the controlls a little more sensitive?

Give your "Expand FOV" button a try while using the target designator cursor.

Antenna elevation by binary (e.g. keyboard) input is not affected by expand option.

As far as I know... no. Any change of how rapidly the axis-type value changes based on binary input if it's possible at all would have to be done semi-deep in the game's script files.

{combos = {{key = '='}},                            pressed = hotas_commands.THROTTLE_ANT_ELEV_UP,                                                        cockpit_device_id = devices.HOTAS,    value_pressed =  1.0,                    name = _('ANT ELEV Knob - CW'),                                            category = {_('Throttle Grip'), _('HOTAS')}},
{combos = {{key = '-'}},                            pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN,                                                    cockpit_device_id = devices.HOTAS,    value_pressed = -1.0,                    name = _('ANT ELEV Knob - CCW'),                                        category = {_('Throttle Grip'), _('HOTAS')}},

You could try changing the 1.0 -1.0 values to smaller amounts but I have no idea if that would work (mods\aircraft\F-16C\Input\F-16\keyboard\default.lua).

There might be some other file that determines how fast the knob axis value changes when subjected to the "CW" or "CCW" inputs but I don't know where you'd find it.

Personally I'd like an accelerating input so I could do large and small changes. If you happen to be using a scriptable joystick (which any device is if you use a 3rd party program) you could bind the two buttons to virtual axis movements and then you'd have control over how much axis movement per unit time those buttons commanded.

Oh he meant it literal when saying "keys"...

Antenna elevation by binary (e.g. keyboard) input is not affected by expand option.

 

As far as I know... no. Any change of how rapidly the axis-type value changes based on binary input if it's possible at all would have to be done semi-deep in the game's script files.

 

{combos = {{key = '='}},                            pressed = hotas_commands.THROTTLE_ANT_ELEV_UP,                                                        cockpit_device_id = devices.HOTAS,    value_pressed =  1.0,                    name = _('ANT ELEV Knob - CW'),                                            category = {_('Throttle Grip'), _('HOTAS')}},
{combos = {{key = '-'}},                            pressed = hotas_commands.THROTTLE_ANT_ELEV_DOWN,                                                    cockpit_device_id = devices.HOTAS,    value_pressed = -1.0,                    name = _('ANT ELEV Knob - CCW'),                                        category = {_('Throttle Grip'), _('HOTAS')}},

You could try changing the 1.0 -1.0 values to smaller amounts but I have no idea if that would work (mods\aircraft\F-16C\Input\F-16\keyboard\default.lua).

 

There might be some other file that determines how fast the knob axis value changes when subjected to the "CW" or "CCW" inputs but I don't know where you'd find it.

 

Personally I'd like an accelerating input so I could do large and small changes. If you happen to be using a scriptable joystick (which any device is if you use a 3rd party program) you could bind the two buttons to virtual axis movements and then you'd have control over how much axis movement per unit time those buttons commanded.

Yes, this works. I've set the values to 0.1 personally, which is both precise and fast enough for me.

It also works for the lua files in the joystick folder (I've bound it to the POV1 on my WH throttle), where the same lines are found. Be advised that you might have to re-bind the antenna elevation controls in-game after changing these files.

I am using the rotary axis and simply built in a curve.... YMMV

I am using the rotary axis and simply built in a curve.... YMMV

Oh, ofc! Mapped to my rotary dial on my throttle and always think it is a bit too sensitive around the middle - never thought of curves, only use those for flight controls lol. Doh, ta.

You can also try unmapoing the rotary...saving it...the. Remapping it. I find sometime if my hardware gets twitchy this fixes it.

Why is ED ignoring this? Isn't this something really easy to fix?