QNH Setting Without Using Mouse

Flight Sims DCS F/A-18C Hornet
1

Hi everyone,
I recently came back to DCS after a long time away from simming. I’m trying to set up my HOTAS and a button box so that I don’t have to use the keyboard or mouse to operate the systems. I’m trying to map controls to the standby altimeter QNH nob by sending key presses from the device. This results in the nob turning far too much for each press, and it is impossible to set accurately.

Is there a way to change this, or work around so I can use a rotary control?

Thanks for any help,
Gareth

2

Hi Goon, welcome to Mudspike!

Which module are you trying this with? And are you sending keypresses from your controller or is it an encoder of some sort?

1 Like
3

Well, this would be the Hornet section of the Mudspike forums so I assume it is for that.

Any control from inside the software? In certain versions, you can set up that the key is hold for only a short amount of time regardless of how long you hold it. Maybe you could use this to gain some finer control.

3 Likes
4

Of course :man_facepalming:t2:

3 Likes
5

Too much movement per button press is sadly an issue with DCS as a whole. You can edit the “speed” in lua files–I’ve done it to get finer trim control on the Mosquito. There’s a line in the joystick or keyboard default.lua with “value_down” for that command, and they’re typically set to 1.0. The closer to 0.0, like 0.25 or something, the finer control you can get. The Hornet’s is in:

DCS World/Mods/aircraft/FA-18C/Input/FA-18C/Joystick → default.lua

The problem is that when I looked into it, it doesn’t have that value_up or value_down entry, yet all the other cockpit knobs (like the SAI) do.

-- Altimeter
{	pressed = iCommandAltimeterPressureDecrease,	name = _('AAU-52 Altimeter Pressure Setting Knob - CCW/Decrease'),		category = {_('Instrument Panel')}},
{	pressed = iCommandAltimeterPressureIncrease,	name = _('AAU-52 Altimeter Pressure Setting Knob - CW/Increase'),		category = {_('Instrument Panel')}},

I bet there’s a way to add that value in there somehow, but I’m not smart enough with code to know how.

1 Like
6

I’m not certain this is the same issue, but there seems to have been some discussion about this on the ED forums that refer to a third-party Git project that seems to have some answers, here is the link and hopefully it can help you?

Link to DCS forums

It seems like the fix gets overwritten with every DCS World update (until maybe ED just steals the fix and claims it as original work in the patch notes… we’ll see :wink: )

2 Likes
7

Hi Everyone,
Thank you for your assistance. I haven’t searched the DCS forums yet so Torc’s link might prove useful.

Thanks again.

3 Likes
8

Hi Again,
Just to say the links were very helpful. I haven’t quite figured it all out to perfection yet, but hopefully I can get there.

Thanks again for all your help,
Gareth

2 Likes