Trimming Sensitivity

[PlayBoy]

I'm using the TM t.16000 HOTAS. I have the hat switch set to manipulate the A/C's trim (elevator/rudder).

 

In the P-51D: One click moves the Trim too much for elevator and rudder. Cannot get the plan to trim out to level flight using the HAT-SWITCH - works fine in P3D

 

IS THERE ANY WAY TO REDUCE THESE A BIT?

 

 

 

:pilotfly::pilotfly:

[Ant0ine]

It might be possible to modify some game config file to do that but I have no experience in doing so.

 

To do that I would use a 3rd app configuration software like Thrustmaster Target or Vjoy+Joystick Gremlin.

 

With those I could make the hat control an axis, and adjust the rate and scale of change of the virtual axis.

 

Let me know if that solution is ok for you and I'll try to explain how to do so.

[LeCuvier]

The file "default.lua" in the folder "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\P-51D\Input\P-51D\joystick" defines the commands.

These two lines define the elevator trim:

{pressed = device_commands.Button_12, cockpit_device_id  = devices.CONTROL_SYSTEM, value_pressed = 0.05, name = _('Trim Elevator Down'), category = _('Flight Control')},
{pressed = device_commands.Button_12, cockpit_device_id  = devices.CONTROL_SYSTEM, value_pressed = -0.05, name = _('Trim Elevator Up'), category = _('Flight Control')},

The numbers following "value_pressed" determine the trim sensitivity. To reduce the amount of change per click you have to reduce these numbers.

Personally I have no problem with the trim but I added these two lines to the file:

{pressed = device_commands.Button_12, cockpit_device_id  = devices.CONTROL_SYSTEM, value_pressed = 0.02, name = _('Trim Elevator Down Fine'), category = _('Flight Control')},
{pressed = device_commands.Button_12, cockpit_device_id  = devices.CONTROL_SYSTEM, value_pressed = -0.02, name = _('Trim Elevator Up Fine'), category = _('Flight Control')},

They create two new commands which I bind to LCtrl + POV_UP resp. POV_DWN. You could do the same with the elevator and rudder trim.

Don't forget though: every update or repair will restore the original file. So you have to either make a backup copy of the modified file manually, or use a program like OvGME.

If you have a spare axis on your HOTAS you could bind that for the elevator trim. That would be much easier for you.

[Fri13]

I think that ED should revisit all the trimming settings and all knob turn rates etc in all modules and get them less sensitive.

 

As now so many aircraft is nearly impossible to be trimmed easily for speed and altitude as it is constantly going past the wanted level regardless how quick and tiny inputs you are giving.

 

(and off-topic but same time check the joystick axis, as in cockpit often stick doesn't move past some axis range like past 85-90% and so on you have so much "dead zone" in real stick travel.)

[wolfstriked]

Omg beautiful to read that its an easy tweak.Funny or maybe not funny but I seen many complaints in many different modules over many years here and not one mention of a simple fix

[PlayBoy]

Wow! thank you very much. I will try this and I appreciate you insight and help

[PlayBoy]

What Program do you use to edit the LUA files?

[Chapa]

Visual Studio Code is a good one

Notepad++ do the job

[LeCuvier]

I use Notepad++

[arb65912]

Anything has changed after 2 years in this area? Is there a way to lower trim settings without lua files?

 

[Munkwolf]

On 7/15/2022 at 5:55 AM, arb65912 said:

Anything has changed after 2 years in this area? Is there a way to lower trim settings without lua files?

Nope. I have the lua edits for different trim speeds available in the keybinds project though: https://github.com/Munkwolf/dcs-community-keybinds

Files are formatted for use with Quaggles mod: https://github.com/Quaggles/dcs-input-command-injector/releases

Bf 109
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/Bf-109K-4/Input/Bf-109K-4/joystick/default.lua#L37

FW 190 A8
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/FW-190A8/Input/FW-190A8/joystick/default.lua#L121

FW 190 D9
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/FW-190D9/Input/FW-190D9/joystick/default.lua#L128

Mosquito
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/MosquitoFBMkVI/Input/MosquitoFBMkVI/joystick/default.lua#L96

P-47
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/P-47D-30/Input/P-47D-30/joystick/default.lua#L22

P-51
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/P-51D/Input/P-51D/joystick/default.lua#L272

Spitfire
https://github.com/Munkwolf/dcs-community-keybinds/blob/e5efc10fff0a77d398cb83f1dcfc320fcfcd54a1/InputCommands/SpitfireLFMkIX/Input/SpitfireLFMkIX/joystick/default.lua#L6

[MAXsenna]

Thank you @Munkwolf
And yeah, it's a real pain that a simple thing like this isn't implemented for every module through the special settings, like the free A-4E-C community module, and the free version of the MB-339. Hopefully the full paid version of the MB-339 will have it and become a forerunner for other modules 3rd parties in this regard.
Cheers!

Sent from my MAR-LX1A using Tapatalk