reported Radar elevation way too sensitive on button

[Lowlyslows]

Just purchased the F16, this issue still is ongoing? I am using the VIRPIL CM3 throttle and a dial for the thumb is there just for this purpose (IMO). I even tried an axis and the jump in altitude blocks is huge..

 

Anyone have an idea?

[Temetre]

The radar elevation is still very difficult to control. On digital buttons its extremely sensitive, even on a (VKB Gladiator) digital decoder wheel its inconsistent how much a single step changes. And the "steps", even on the wheel, are so big that theyre sometimes skipping areas between min/max angle.

Ive tried putting it on the VKBs throttle just for testing (not really useful in closer range combat), and even that hardly works because it doesnt have enough moving space. Curves dont really help,

 

So for suggestions, I think these things could help improve antenna control:

 

1. Digital sensitivity needs to be way lower. Preferably adjustable, or with seperate low/high sense keys. But even high sensitivity keys needs to be way lower than the current rate.

2. Digital sensitivity needs to be more consistent, or work more in steps. Currently it controls so fine (or maybe inconsistent) that even a digital decoder wheel doesnt work consistently. For humans its just impossible to work it accurately.

3. For axises, there needs to be a slew option to be usable with spring loaded axis controls.

4. We need a 'recenter key' almost regardlessy, since digital controls and slew make it finnicky to recenter the switch.

Currently, the antena is hardly possible to operate with anything that doesnt perfectly replicate the F-16 antenna control disc. Which is almost nothing does.

Edited May 6, 2023 by Temetre

[=BoB= David]

Hey guys,

 

A while ago I reported on discord bug of controls issue on F-16C and P47 (other topic) about rate of some controls. https://discord.com/channels/542985647502393346/1193250513689530509

Track is self-explanatory, just to be sure - I binded controls of keyboard to eliminate HOTAS etc..

Radar elevation is not able to set at specific altitude and jumps about 15k ft for 20nm and zoom level of TGP jumps for 2-3 zoom levels instead of 1.

Module is unflyable for me in every situation when I need radar (which is almost every situation), and this patch did not fixed it, I demanding quick hotfix or atleast some walkaround (and no, I will not bind radar elevation on axis, other modules as far as I test it works fine). Like I said, module for 60usd is unflayable for me for two months now..

Few patchs back it works good and without such a big jumps...

Thanks.

f16_tgpzoom_and_rdrelev_rate_2.trk

Edited February 22, 2024 by =BoB= David

[BIGNEWY]

I am not seeing any issue when I test. 

please ensure you have no double axis binds for the radar elevation. 

thank you 

[=BoB= David]

I don't, I will make video if it will be helful, but @Archer.xd managed to replicate this issue..

[=BoB= David]

14 minutes ago, BIGNEWY said:

I am not seeing any issue when I test. 

please ensure you have no double axis binds for the radar elevation. 

thank you 

 

[=BoB= David]

Attaching logdcs.log

[=BoB= David]

@BIGNEWYIs in DCS folder any file, which describe convertion rates / sampling, I dont know how to call it correctly, of these inputs? Can you send me your file? Or name of it, I would try to experiment with it? 

[=BoB= David]

This seems like same issue 

 

[=BoB= David]

@BIGNEWY Any news regarding to this topic?

[BIGNEWY]

Hi, I have merged the thread with the older one, and asked the team to take another look at the report about using button press on axis. 

thank you 

[kylekatarn720]

Issue reported in 2019, its 2024. Button presses on "ANT ELEV Knob - CW" and "ANT ELEV Knob - CCW" still producing huge jumps on radar elevation. Just add a duplicate low sensivity command with like a 10:1 input output ratio. I honestly dont get why it couldnt be done in 5 years. 

For people with the TM Warthog throttle and use the slider1 for camera zoom here is my work around for the radar elevation and tgp manual zoom. Add the left throttle big red button ( button 15) as a modifier, assign left throttle axis + button 15 to "MAN RNG Knob", assign left throttle axis to "ANT ELEV Knob". With this you can use the left throttle for both of the antenna elevation and tgp manual zoom. Tgp manual zoom part will only work as long as you hold down the button 15 but since its a modifier now you wont be able to use any other buttons while holding the button 15 down.

Its an inconvenient workaround but a workaround nonetheless. Hopefully ED will fix the issue in the next 5 years.

Edited June 27, 2024 by kylekatarn720

[Exorcet]

A sensitivity option should exist regardless of whether there is a bug or not. It would be a nice feature to have.

[hx5791]

The aircraft in FC3 is very comfortable to adjust the altitude with a button radar, why is the F-16 not good? It is highly recommended to use the JF-17 to adjust the height of the radar, and three modes (axis, axis with back center, button) are available for players to choose from, suitable for all types of equipment.

[Viper1031]

This is still happening, whether it's a button press or an axis. It's a bit of a pain

[Tenkom]

This has been an issue for 5 years. The fact that you can fix this in 5 minutes yourself by editing a .LUA file, as shown by LeCuvier on the second page of this thread, tells me that they simply don't consider this an issue.

I wish they would just add a second bind that is less sensitive.

[hx5791]

Is it possible to set the button to only adjust the radar pitch angle to a fixed value without taking over the continuous signal of the button being pressed? This should solve the problem of values changing too quickly.

[=BoB= David]

@BIGNEWY Still not fixed...

 

[Tenkom]

Still a problem. More than 5 years later....
It is easily fixed with a simple edit to the .LUA file so there is no excuse for this.
If for some reason you are actually happy with this crazy sensitivity at least add a ant-elev slow bind. It has nothing to do with realism since in RL this is an absolute analog control.

[REL]

Hi

 

you can hotfix that yourself by backup & editing "default.lua" file in to DCS World\Mods\aircraft\F-16C\Input\F-16C\keyboard.

The change you're looking for is in 101-102 lines: "ANT ELEV Knob - CW" section from 1.0 to 0.1  &  "ANT ELEV Knob - CCW" section from -1.0 to -0.1.

No effect on multi-player "Integrity Check" as far as I know.

 

Good luck