Any way to 'slow down' binds? HSI course and Heading too crude on switches

[imacken]

I have the HSI Course and Heading knows bound to 2-way switches.  A slight touch of the switch and the headings change by 10 degrees. That is way to crude!

Is there a way - edit a lua? - to 'slow down' the responsiveness of these controls?

[Zabuzard]

Yes. Open your input lua, locate the bind and change our knob_inc_dec(...) function used there to the knob_inc_dec_variants(...) function (and add the slow/fast speed values accordingly).

You can also wait for the next patch where we fixed that already :)

[YSIAD_RIP]

One of the many things I enjoy about DCS is "Patch Day".  Experiencing when Early Access Modules and even older modules improve over time as the receive new features keeps me coming back to try out the upgrades and test things out. 

Good luck with the next update for the F-4E @Zabuzard

[imacken]

31 minutes ago, Zabuzard said:

Yes. Open your input lua, locate the bind and change our knob_inc_dec(...) function used there to the knob_inc_dec_variants(...) function (and add the slow/fast speed values accordingly).

You can also wait for the next patch where we fixed that already

Which input lua file are we talking about?

[Zabuzard]

The one that defines what you can bind in the Phantom.
Sth like DCS/Mods/F4E/Input/Pilot/keyboard/default.lua

[imacken]

Thanks. I was looking at the joystick default, not keyboard.

So, there is good news and bad.  The good news is that changing to variants and by binding to Course/Heading (Slow) and setting a value of 0.0008, I can get a 1 degree change with a press of the switch. The bad news is that makes holding the switch to move continuously round VERY slow to the extent that it is unusable. I would have to make another bind (to normal or fast) for that, which is not good.

The same bind on the same switch/device, works perfectly in other modules, e.g. Hornet, without any fast/slow options.

[escaner]

17 hours ago, Zabuzard said:

You can also wait for the next patch where we fixed that already

Hi, while you are at it, please check also the Reticle Depression bindings. It is way worse than Heading/Course.

[Zabuzard]

Hi, while you are at it, please check also the Reticle Depression bindings. It is way worse than Heading/Course.

These are included in the same patch

Thanks. I was looking at the joystick default, not keyboard.
So, there is good news and bad.  The good news is that changing to variants and by binding to Course/Heading (Slow) and setting a value of 0.0008, I can get a 1 degree change with a press of the switch. The bad news is that makes holding the switch to move continuously round VERY slow to the extent that it is unusable. I would have to make another bind (to normal or fast) for that, which is not good.
The same bind on the same switch/device, works perfectly in other modules, e.g. Hornet, without any fast/slow options.

There isn't much we can do here besides the already planned self-accelerating binds (which are a bit complex on the technical level since DCS doesnt support that natively)

[imacken]

13 minutes ago, Zabuzard said:

There isn't much we can do here besides the already planned self-accelerating binds (which are a bit complex on the technical level since DCS doesnt support that natively)

Interesting. As I said above, the exact same device buttons/switch and binds work perfectly in other modules, e.g. Hornet.  Quick left or right makes degrees go up by one, and holding the switch makes the dials rotate at a 'normal' rate. I appreciate that the Hornet is a switch, and the F-4E is a knob, but still.  In the F-4E, the holding speed is way too slow and pretty much unusable.

Edited June 2, 2024 by imacken

[Zabuzard]

Interesting. As I said above, the exact same device buttons/switch and binds work perfectly in other modules, e.g. Hornet.  Quick left or right makes degrees go up by one, and holding the switch makes the dials rotate at a 'normal' rate. I appreciate that the Hornet is a switch, and the F-4E is a knob, but still.  In the F-4E, the holding speed is way too slow and pretty much unusable.

There is plenty of modules or knobs where it wont work "nicely" either. The examples you brought up are such manually coded self-accelerating binds where the actual behavior of "first slow, then fast" is coded manually on the backend.

As soon as you use the key_pressed instead of key_up/key_down system, you are using DCSs internal logic where it accumulates the input over time.

[imacken]

I don't fully understand that, but why can't you use the same logic as the ones that do work well?

[DSplayer]

On 6/2/2024 at 3:39 AM, imacken said:

I don't fully understand that, but why can't you use the same logic as the ones that do work well?

The reason why other modules it has self-accelerating binds is because those modules have it coded as such and such behavior is realistic to how it works in the aircraft IRL. For example, the HDG and CRS switches work in a way such that if you hold it down for ~>1 second, it will speed up (as it does IRL I presume). In the F-4, you can't have that since the knob is a knob that moves at a fixed rate. The thing that is changing here with the slow vs fast is the rate that it is moving.

[imacken]

I get that. However, it would be useful to have a self-accelerator option. 

[escaner]

I just wanted to report that for me sight depression, heading and course selection are perfectly usable now after the patch. Thanks a lot!

[LeCuvier]

On 6/1/2024 at 6:05 PM, Zabuzard said:

Yes. Open your input lua, locate the bind and change our knob_inc_dec(...) function used there to the knob_inc_dec_variants(...) function (and add the slow/fast speed values accordingly).

You can also wait for the next patch where we fixed that already

I didn't understand this when I first read it. But looking at the file after today's update I think I get it. Heatblur has a very different approach in the "default.lua". With a single line in that file, using the function "knob_inc_dec_variants",  they can create 6 bindings. I used to be very confident editing these files, but for this module I have to re-learn "my trade".
The good news is that the people at Heatblur do a strling job with bindings so I will have much less editing to do.

[Zabuzard]

I didn't understand this when I first read it. But looking at the file after today's update I think I get it. Heatblur has a very different approach in the "default.lua". With a single line in that file, using the function "knob_inc_dec_variants",  they can create 6 bindings. I used to be very confident editing these files, but for this module I have to re-learn "my trade".
The good news is that the people at Heatblur do a strling job with bindings so I will have much less editing to do.

Yeah, we have created some form of shortcuts to the binds (defined in bind_dsl.lua)

The good thing is that the system still supports the "classic style" as well, so one can still put in manual binds and it would pick them up (as seen for the standard pitch/roll inputs somewhere at the top of the file)

[LeCuvier]

9 hours ago, Zabuzard said:

Yeah, we have created some form of shortcuts to the binds (defined in bind_dsl.lua)...

That's impressive stuff! I have done a lot of VB programming, but I struggle with Lua. It will take me some time to understand your logic to the point that I could apply  it.
I wonder if it will work with bindings under "...\Saved Games\..." using the Command Injector developed by @Quaggles.

[JOEM423]

I use a little app called JoyToKey! its wonderful and you can slow down the input of any button or Axis! the learning curve is vertical though!