Will trim ever be good?

I love so much about this simulator except for the awful trim. I have a Honeycomb Bravo with the trim wheel and it’s not a good experience. The trimming is not linear and there’s a delay when you roll it. In some aircraft the up-trim is faster than the down-trim and it makes it super difficult to trim it out.

The button trim on the yoke is more consistent and linear but there’s still this weird delay between when you press it and when it happens in the sim.

Are you guys dealing with the same struggles or have you found a solution to the awful trim situation?

5 Likes

I use an app to control mine. Much better experience for my honeycomb.

https://authentikit.org/atk-html/tuning/

Yeah, but that’s another 2 external programs I need to run, configure, keep up to date and check.

Only for a perfectly functioning piece of hardware that has been bugged during an attempt to fix a trim wheel issue on 1 specific plane (since SU7 SU4 iirc)

2 Likes

As they will fix the annunciator and autopilot lights for the Honeycomb throttle in SU12 I really hope they will look at the trim wheel issue of the device also. Keeping my fingers crossed. In the meantime I will resort to the solution @OneFang666 mentioned. Thanks for that.

Only one app for me and I have it auto start with MSFS. Ive never updated it. Ive used it so long now it’s just part of the process of flying.

The problem is that trim wheel I think is a button like signal. Really should be an axis.

1 Like

I have tried this in the past but I found that the axis option made the adjustments too big and digital making it hard to trim out the aircraft precisely.

The button option comes with a huge lag and continues to trim after you stopped.

Ha, well, that would cause problems. For GA, sure, it could be an axis. For airliners like the 737, you want it to be as it is.

The main problem is that during release of MSFS and the Bravo, the trim worked mighty fine.

Then during some update, I believe the 172 or 152 had a bug where the trim would be ridiculously sensitive.

They then solved that in the next update by numbing the trim for all planes. So it never got fixed correctly. In the mean time some models got their specific fixes again, but in the core of the sim, it’s still not as it should be :slight_smile:

3 Likes

That’s exactly how I recall it as well. It worked like a charm until Sim Update 4, where a change led to the current (IMO suboptimal) change.

1 Like

Ooh that’s odd not noticed that issue. There is a sensitivity setting in the app.
My big issue with it is when you come out of autopilot and touch the trim wheel. Goes crazy.

I have played with a setting using spad next I found for some aircraft and that’s fine. If you use spad I’ll dig out what I’ve done.

Just in case it’s helpful, here are my spad.next settings. Be sure to remove the wheel trim button actions within your MSFS profile. for me with the honeycomb, it’s button 22 (trim down) and 23 (trim up).

You can adjust the .003 as you prefer sensitivity.


2 Likes

So you are using the axis option for the trim? Can you share what type of settings you have in Authentikit, please?

See below. I’ve started to test with spad as described above as I would prefer not to have an extra app running and there is that issue out of autopilot I mentioned.

Screenshot 2022-11-18 094031

1 Like

Great point!
The thing is, however, that the the current behaviour accidentally matches the plane that I fly quite good. So imho the trim behaviour really should be adaptable for each plane individually.

2 Likes

Some planes work better than others. For example, the Arrow III trims really well with the Bravo but the new DC-3 is a nightmare.

I think the ideal setup would be that the in-game trim worked like an internal virtual axis. Controls and autopilot would all adjust that same “axis”. There would then be ability to map it to controls by:

  1. Adjusting the trim axis with buttons, by how much per click should be adjustable.
  2. Adjusting the trim with an axis (e.g. analog ministick on your joystick or Xbox controller) with relative method. I.e. pressing the ministick down would adjust elevator upwards at rate depending on how much you press it down. Once you stop pressing it retains the set position.
  3. Absolute axis, e.g. hardware trim wheel. This would work same as before, unless someone makes FFB trim wheel or something.

The method 2) in particular would combine granularity of an axis with autopilot compatibility, I’d use it for trim over the other options. Relative axis trimming is currently pretty good since trim axis ideally needs long travel and relative axis can fake long travel even with a ministick, but without a virtual axis that’s internal to MSFS software it’s not autopilot compatible.

There is still the lack of feedback in your stick which prevents you from feeling the right trim adjustment.

I still dream of the 1-button method :
1- hold your stick in the needed position for a steady flight.
2- hold the magic button while releasing the stick.
3- release the magic button. Tadaa, trim is set.

Problem as far as I can tell is that the trim inputs are simply bog-standard digital repeats. The minimum input from a quick tap is far too large, and holding a button is just linear. If your aircraft is currently trimmed slightly nose-down, even the shortest press of trim-up will make it nose-up. It’s only luck or coincidence if you successfully manage to get it level.

If done properly, a quick tap should be barely noticeable. A longer tap slightly more so etc., up to a maximum rate when a button is held for a certain length of time (1/2 second or something). None of that should be programatically difficult, just requires a bit of forethought (which we’re obviously way beyond now) and time to implement.

1 Like

Ohhhh why didn’t I think of that myself? :smiley:

I thought it was in SU5 when they changed it so it would work with an XBOX Controller for the XBOX launch?

To illustrate the post above. In red is how I think trim currently works, in green is how I think it should.

image

The curved portion only needs to be a very short amount of time, but you can see how much it reduces the size of the initial input.