Trim Too Fast

[aphill]

 I would like to be able to slow down the rate that the trim wheels turn with the hat switch on the joystick, it moves too fast. (too sensitive)

I remember having to do that for the Mosquito early on and it was with a lua file. I just don't remember all the details. Anyone remember that?

 

[JupiterJoe]

Wouldn't each update erase any changes you made?   I suspect we'll see more nuance added to the flight-model and improvements to the FFB model as development continues, as we did with the Mustang. 

[aphill]

Well yes but you just make a copy and paste it back in after the update. I can't remember if I duplicated the folders in saved games or not. It work very well though. DCS did fix the issue in an update.

Its no big deal I just enjoy tweaking things.

Thanks for the reply.

[LeCuvier]

13 hours ago, aphill said:

 I would like to be able to slow down the rate that the trim wheels turn with the hat switch on the joystick, it moves too fast. (too sensitive)

I remember having to do that for the Mosquito early on and it was with a lua file. I just don't remember all the details. Anyone remember that?

 

I have added LUA lines for slower versions of the trim functions (rather than modifying the existing ones). As I'm using the "Command Injector" by @Quaggles, I entered them in a "default.lua" file under Saved Games. This eliminates the rework associated with changes/additions in the stock file at the time of updates. Here are the lines I added:

{pressed = device_commands.iCommandElevatorTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.001, name = _('Trim, nose down SLOW'), category = _('Flight Control')}, 
{pressed = device_commands.iCommandElevatorTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.001, name = _('Trim, nose up SLOW'), category = _('Flight Control')}, 
{pressed = device_commands.iCommandEleronsTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.001, name = _('Trim, left bank SLOW'), category = _('Flight Control')}, 
{pressed = device_commands.iCommandEleronsTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.001, name = _('Trim, right bank SLOW'), category = _('Flight Control')}, 
{pressed = device_commands.iCommandRudderTrim, cockpit_device_id = devices.CONTROL, value_pressed = -0.001, name = _('Trim, yaw left SLOW'), category = _('Flight Control')}, 
{pressed = device_commands.iCommandRudderTrim, cockpit_device_id = devices.CONTROL, value_pressed = 0.001, name = _('Trim, yaw right SLOW'), category = _('Flight Control')}, 

As you will see, I only needed to change the value for "value_pressed".

Note I tested only one of the lines; but as they all follow the same pattern that should be safe. If you run into a problem let me know.

Edited Monday at 04:41 PM by LeCuvier

[aphill]

So drop the default lua file in saved games?

[_Hoss]

I'm lucky I have a trim box with wheels, so I don't have to use the trim hat on the stick. I had to really de-tune mine because they moved to fast. I have that problem with other modules, too. The F-86 is a pain because I use the stick trim hat. It does move way too fast. 

[aphill]

I wish they would give us the ability to set a curve on the trim.

[motoadve]

2 hours ago, _Hoss said:

I'm lucky I have a trim box with wheels, so I don't have to use the trim hat on the stick. I had to really de-tune mine because they moved to fast. I have that problem with other modules, too. The F-86 is a pain because I use the stick trim hat. It does move way too fast. 

I also have a trim box, how did you de tuned it?

[LeCuvier]

6 hours ago, aphill said:

So drop the default lua file in saved games?

No,not that simple. Go to this post to get the info: https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v109-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#comment-4651461

[MAXsenna]

I wish they would give us the ability to set a curve on the trim.

You can if you use an analog wheel, while I'm not sure if you want to do that with such an axis. What we need is to be able to set the trim speed, like in the free A-4E-C community module, and what we had in the free MB-339 community module. I don't remember, but I think they were gonna implement it in the paid version too.

Sent from my SM-A536B using Tapatalk

[Wrench]

I'm drawing a blank on the name, but there is a JSGME/OVGME mod that handles custom control binds, should be able to add a custom bind that like

"Trim 1/10" pretty sure I've used it for that in other A/C before. 

 

Edit

 

https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/?do=getNewComment

Edited 5 hours ago by Wrench

[LeCuvier]

15 minutes ago, Wrench said:

I'm drawing a blank on the name, but there is a JSGME/OVGME mod that handles custom control binds, should be able to add a custom bind that like

"Trim 1/10" pretty sure I've used it for that in other A/C before. 

 

Edit

 

https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/?do=getNewComment

JSGME is an older program, and OvGME is more recent. I use OvGME to back up and restore modded files like cockpit glass etc, and the one file @Quaggles had to modify in the game folder structure. Unfortunately, @sedenion no longer supports this tool. Also, OvGME does not help you with the issues that arise when the developer adds new bindings to the "default.lua". This happens quite often especially with new modules that are in Early Access. You are then obliged to compare the new version with your modded version, and add your additions to the new file, except when some of the developer's additions do the same as your additions in the modded file. 
The Command Injector avoids these issues.

[fargo007]

I feel the opposite, and wish they were actually a bit faster.