trim the F-16

[jack333]

Dear colleagues, just an appreciation and a question, it happens to me that when I try to trim the plane, it is too sensitive and I can never leave it completely straight, in the F-18 if it is less sensitive and it is possible. Is there a way to make the trim less sensitive? thanks and greetings

[LeCuvier]

Yes, there is - if you are willing to do a little edit of the "default.lua". In my experience it was mostly the pitch trim that was too "fast" and I adjusted that down.

Edited November 23, 2021 by LeCuvier

[jack333]

hace 9 horas, LeCuvier dijo:

Yes, there is - if you are willing to do a little edit of the "default.lua". In my experience it was mostly the pitch trim that was too "fast" and I adjusted that down.

 

Thanks for the answer, but how do I do it? With the elevation of the antenna I have succeeded, but with the trim I do not know how to do it.

 

[LeCuvier]

In the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" , look for these lines below "-- Manual Trim Panel":

{pressed = control_commands.RollTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed =  0.3,	name = _('ROLL TRIM Wheel - L WING DN'),		category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{pressed = control_commands.RollTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed = -0.3,	name = _('ROLL TRIM Wheel - R WING DN'),		category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed =  0.3,	name = _('PITCH TRIM Wheel - NOSE UP'),			category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed = -0.3,	name = _('PITCH TRIM Wheel - NOSE DN'),			category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{pressed = control_commands.YawTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed = -0.3,	name = _('YAW TRIM Knob - L/CCW'),				category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{pressed = control_commands.YawTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed =  0.3,	name = _('YAW TRIM Knob - R/CW'),				category = {_('Left Console'), _('MANUAL TRIM Panel')}},

The original lines have lots of tabs after the "{" which I removed as they have no function and take too much space.
You can reduce the "value_pressed" parameters and that will make the trim value change more slowly. I only changed the pitch trim:

{pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed =  0.1,	name = _('PITCH TRIM Wheel - NOSE UP'),			category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1
{pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed = -0.1,	name = _('PITCH TRIM Wheel - NOSE DN'),			category = {_('Left Console'), _('MANUAL TRIM Panel')}},-- modified value_pressed from 0.3 to 0.1

You obviously have to bind your POV hat to the modified commands. Personally, I use the "normal" trim commands for aileron and rudder (like "TRIM Button - LEFT WING DOWN") as we have the luxury of two sets of trim commands (not counting the axis commands).

Notes:
1. you need to make a backup copy of the modified file as updates and restores will restore the original file.
2. you should make the same change to the "default.lua" under "...\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard" in order to avoid getting duplicated orange lines in Options/Controls.

[Funflite]

Hi LeCuvier;

This mod pass the integrity check?Did I remake all bindings for the controllers?

Thank's a lot.

[LeCuvier]

1 hour ago, Funflite said:

Hi LeCuvier;

This mod pass the integrity check?Did I remake all bindings for the controllers?

Thank's a lot.

This kind of mods passes IC. No need to re-bind anything except the commands you have just modded.

Edited November 24, 2021 by LeCuvier

[Funflite]

HI Lecuvier,

I follow all the procedure discribed;but,I lose everything in the axis command and some of function/axis diseaper or missing and all others joysticks command missing too...hum,what i mess in your procedure.Can you make a better way to show how?

Thank's

[Funflite]

HI Lecuvier,

I do a full repair because all my key bindings are corrupted...even my axis too.Even i back-up my default.lua in the directory that you pointed earlier.

[jack333]

Thank´s Lecuvier,but I have it mapped on the keyboard, is it the same?

Edited November 25, 2021 by jack333

[LeCuvier]

9 hours ago, Funflite said:

HI Lecuvier,

I follow all the procedure discribed;but,I lose everything in the axis command and some of function/axis diseaper or missing and all others joysticks command missing too...hum,what i mess in your procedure.Can you make a better way to show how?

Thank's

I don't know what you did. If you had simply overwritten the original values with smaller values, this kind of problem would never happen.

[LeCuvier]

@Funflite: I suspect you copied & pasted the last 2 lines of code from my post. I just see that I lost some characters when I copied & pasted from my file to the forum. And if you pasted that into your file that would have corrupted it.

Here are the full lines:

{	pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed =  0.1,	name = _('PITCH TRIM Wheel - NOSE UP'),	category = {_('Left Console'), _('MANUAL TRIM Panel')}},
{	pressed = control_commands.PitchTrim_ITER,	cockpit_device_id = devices.CONTROL_INTERFACE,	value_pressed = -0.1,	name = _('PITCH TRIM Wheel - NOSE DN'),	category = {_('Left Console'), _('MANUAL TRIM Panel')}},

Anyway, as I said, you should simply overwrite the values in the original lines.

If you prefer to copy & paste the modified lines, you must previously either delete the original lines, or inactivate them by inserting two hyphens ("--") at the beginning of the lines.

Also, don't use something like Word. Use Notepad++ or equivalent!

And, I apologize for my negligence.

[LeCuvier]

46 minutes ago, jack333 said:

Thank´s Lecuvier,but I have it mapped on the keyboard, is it the same?

 

Yes, and as I wrote in my post above you should make the same changes in both "default.lua" files to avoid duplicated orange lines.

[jack333]

Thank´s Lecuvier

[Funflite]

Hi LeCuvier;

Sorry for MY mistakes on this.I appreciate a lot your tips on it.It works very well.Thank's a lot men.

 

[LeCuvier]

26 minutes ago, Funflite said:

Hi LeCuvier;

Sorry for MY mistakes on this.I appreciate a lot your tips on it.It works very well.Thank's a lot men.

 

glad to hear that you got it sorted!