reported Radar elevation way too sensitive on button

Hotfix for radar antenna elevation?

Is it possible we could get a hotfix for this?

Asking as this bug alone kind of rules out flying the Viper online for anyone without a free axis atm.

Bump, as for M2000 RWR.

This bugs should have to be fixed with an hotfix in a very quick time (fixed internally), without waiting for the next update. In this way is a neverending story also for a beta.

Yeah kind of absurd this even got out, it's like they didn't do a single test on using the radar, and still no fix, I'm not programer but sounds like a pretty easy fix to lower the gain of an input

What is the problem?

If the antenna elevation increase/decrease are bound to KEYS rather than an axis since the latest update one short press slews the radar a huge amount making it virtually impossible to use.

It may not be easy but, I have to say the sould do more testing before updating

Radar antenna elevation control STILL too sensitive

As the title says the radar elevation sensitivity is still way too high for button control, and thus it's very hard to be accurate with using buttons.

Please do a quick hotfix for this.

Radar antenna elevation still not fixed

See title: contrary to claims the button sensitivity is still way too high. There do seem to be some changes from the previous open beta version, but it's nothing like it used to be. I'm using the POV hat on a Warthog throttle.

Included are two tracks: one for current open beta and one for current stable version. The difference is huge.

F-16 antenna elevation beta.trk

F-16 antenna elevation stable.trk

+1

Radar elevation slowed down

The rate of elevation change via button commands is determined by these two lines in the file "default.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick":

{    pressed = hotas_commands.THROTTLE_MAN_RNG_DEC,                                                        cockpit_device_id = devices.HOTAS,    value_pressed = -1.0,                    name = _('MAN RNG Knob - CCW'),                                            category = {_('Throttle Grip'), _('HOTAS')}},
{    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')}},

More specifically the numbers following "value_pressed". If you change them to 0.1 and -0.1 you can set the elevation quite precisely. Instead of modifying the original lines, I added two new lines and bound the added commands to the coolie switch on my TM WH throttle:

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

You can use values like 0.2 or 0.3 instead of 0.1 to make it a bit faster.

Not an ideal solution of course because the next update will replace the modified file with the original again. I use OvGME to manage my modified files and prevent loss of my modifications.

was This issue fixed? I still having trouble with it bound to my Warthog throttle INCR/DECR as axis command..... just seems real buggy. I spend way too much time bugging a target due to this problem

was This issue fixed? I still having trouble with it bound to my Warthog throttle INCR/DECR as axis command..... just seems real buggy. I spend way too much time bugging a target due to this problem

It was fixed with the December 24th update. It is working well with the TM Cougar controller on my end.

I find it still a bit fast with normal switches, so I continue to use my little mod with values of 0.2 and -0.2,

This is still a problem after all this time, really hoping for a fix soon cause it's frankly infuriating to operate.

I'm having issues as well.I have no axis to assign it to so i assign it to a 4 way hat and if i touch it even quickly it jumps all over the place. Not usable for air to air at the moment.Tried individual switches and it made no difference.

...Tried individual switches and it made no difference.

Individual switches cannot make a difference except if you use a rotary encoder which produces very short pulses. If it's such a big problem for you,why don't you apply the change described in post #35?

I didn't see that i will give it a try ty.

The rate of elevation change via button commands is determined by these two lines in the file "default.lua" in the folder "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick":

[...]

Thanks, that looks interesting for some other cases that I will try out probably, like trim or TDC slewing...

Individual switches cannot make a difference except if you use a rotary encoder which produces very short pulses. If it's such a big problem for you,why don't you apply the change described in post #35?

Ooor, ED fixes it?

Still not addressed... come on ED, it's impossible to properly use the radar without this.

Press the up or down button once and it changes 10-20kft in elevation, it's crazy.

Same issues on a warthog, anyone know how to assign the "antenna elevation up/down functions to the throttle friction control.

At the moment it does not show me the option to assign them to "joy_slider1"

Bump cause this is really annoying.

I'm already sturggling so much with binding the inputs on my crappy X52 , and the naming scheme in the 'adjust controls' section.

The slightest tap will send the elevation to the moon instantly , the sensitivity is just WAY too high.

I'm no expert but this should not be hard to fix , but it's very vital

I just installed the F-16 module and set up the controls. Testing things out I came across the very rapid radar elevation change. Thought I had it set wrong or something... guess not.

I see it has been reported (in 2019) but has there been any feedback on addressing the issue?

Why is the control via digital controls not an accelerating adjustment? The rate of change increasing over time will allow for both fine and coarse control.

Have to dig this out.

I and many others still experience the radar elevation control via buttons to be way too fast. It's nearly impossible to fine tune the scan elevation.

Please consider fixing this, since not everybody has a free axis for elevation control.