fixed Problem with Tacan mode selector ussing button mappings

[correca]

Hello, I apologize if this issue has already been reported before.

According to my tests, the problem is common to all Mirage F1 modules and in the case of the BE model, the incidence occurs in both cockpits.

Action bindings:

    TACAN mode selector - Clockwise
    TACAN mode selector - Counterclockwise
    
Erroneous behavior detected:

Using these assignments, either with the controller buttons or with the keyboard keys, when reaching the extreme positions (OFF - A/A) the TACAN mode selector is locked in them. In these extreme positions, only the mouse can be used to change the position of the knob.

This behavior is reproduced in the latest version of DCS without mods, after doing a slow repair and creating a new configuration within saved games.

Best regards

[Vibora]

Thanks for your report. Fixed internally.

[correca]

Thank you for your immediate support.

[LeoS.72]

Is this a bug or does something need to be configured? Why is it that when I try to set the required distance (when setting the values for TACAN) and use the Additional Vector Bearing/Distance Adjustment Selector for this, the values on the Distance Indicator scale jump, and there is no way to set, for example, the exact value of 11? Very high switch sensitivity. Maybe there is a solution to fix this?

[scoobie]

The TACAN mode knob got bugged as described in this thread, but what you're talking about is unrelated.
Overall I quite like how these self-accellerating controls are programmed in F1 (there are more of them than those you mention), but I'd agree their "initial speed" is a bit too high, i.e. when you just briefly tap a button/key.
Maybe with the keyboard they would feel fine/ish, but I'm using spring-loaded toggle switches and these are a bit slower to work with than keyboard, so yeah - setting precisely 11 miles of offset or an exact course of 347 is somewhat hard, I agree.

As for the solution, I haven't tried myself, I'm not bothered with it too much. I suspect that tinkering with Lua files may not work in this case because these are accellerating controls. This accelleration must be done in code, maybe C++ code, in which case it's hard-coded for us, the users. If that's the case the controls probably treat "value_down" in default.lua as strict binary input, zero/non-zero for off/on, respectively, so any attemps to tune value_down probably won't change anything.

EDIT: Wait, I was talking about F1-CE (I fly mostly this version), I think you might have had F1-EE in mind - it has this "IDN" instrument different, with this little  bearing/offset switch turned left or right, not a "real knob" as in the CE version, correct? If so - yes, if I recall correctly it's very fast, pretty hard to use with precision.

Edited November 29 by scoobie

[LeoS.72]

yes yes, exactly F1EE. It's just not realistic to use the pen softly