Tested in multiple aircraft. I just got a brand new controller and thought perhaps that might have had something to do with it, but even with my old one the problem is still there.
Depending on the aircraft you choose, look at the trim # and then hit escape.
When you re-enter the sim, your trim # will be drastically different than it previously was.
Some add +25 to the trim, some do -25. Those are drastic trim #'s so I imagine this is a new problem because if you do not think to check this, your aircraft will all of a sudden have a climb or dive to it and that will directly affect the user.
Check your entire control settings across all the hardware that you have connected. How’s the Trim being bound. Here’s a few rules to follow:
Never bind the same command from multiple hardwares (ie. Trim Axis on a slider on your Yoke, then also on your throttle quadrant slider.) This will feed the sim with conflicting inputs to the same function, making it misbehave. So check on all your hardware controls make sure only 1 function to the same thing is bound to only one hardware. And remove it from the other hardware that you don’t want to use.
Never bind similar commands from multiple hardware (ie. Trim Axis from your throttle quadrant slider, but also Trim Up and Trim Down command on a button your keyboard). Same with rule no. 1, this will introduce conflicts. So only use one command for the same thing, (ie. Either you use the Trim Up and Trim Down button, by removing the Trim Axis. Or you use the Trim Axis on the slider, then you have to remove the Trim Up and Trim Down button from all of your control profiles on all your hardware).
Never bind the incorrect type of command to the wrong type of controls. MSFS has multiple types of control commands that only works for a certain type of input.
Toggle = This is only used for buttons that you press and instantly release. It will operate by changing states from one state or the other depending on when the button was pressed. (ie. if it’s off, pressing the toggle button will turn it on and it will stay on until you press it again which will turn it off and it will stay off until you press it again to turn it on, and so on). If you bind this to a switch that doesn’t return to a released position. The sim will continuously operate the switch on/off multiple times per second. You don’t want to bind this command to this type of switch.
Set = This is only used for switches that are persistent. When you press/move it keeps being in that position until you interact it again to release it. Good for switches with an ON position that feeds the sim with an input signal and a OFF position that stops the input signal from being sent to the sim. If you bind this SET command to a button that is instantly disengage, you can never keep it on as it will always turn off immediately after you release the button. You can only get this working on a button if you keep pressing the button.
Set * On/Off = Similar to the SET command above the difference in this type is if your switch has both an ON position. Like Position 1 and Position 2 that both feeds input to the sim. For this you need to bind the ON command to Switch position 1, and the OFF command to the Switch Position 2.
Axis = This command type is used for levers and sliders that stays in place within a range of motion. This is an analog signal used for your Yoke, Sidestick, etc to control the primary flight controls such as Ailerons, Elevators, and Rudders. There are other commands like Trim Axis but you should only use this command to a slider that you have.
Do not have command bounds to a non-existent hardware. Here’s an example. If you use the Thrustmaster TCA Quadrant Airbus Edition. It comes in at least two configurations. The Throttle Quadrant itself, or with the Spoilers and Flaps addons attached. But these two configurations are part of the same device. So in order for MSFS to be able to make the Quadrant with Addons work properly, the default profile needs to have the addon commands bound (Landing Gear, Flaps Axis, Spoilers Axis, Rudder Trim, Parking Brake, etc). But if you only have just the Quadrant without the Addons, these default bindings will go to a non-existent hardware. So the Quadrant is feeding the sim with “Phantom Inputs” Meaning it thinks that the hardware is feeding the sim with a Flaps position (since it was bound in the control profile) but there’s no actual flaps to do the input. So the sim will apply weird flaps and spoilers behaviour.
If you’re not using a particular command. Don’t bind it or remove it. For example, the Airbus A320neo has an Autotrim function under normal law. Meaning you most likely don’t need to trim at all for the entirety of your flight. Let the aircraft manage the trim, so you need to remove any trim command from your active profile to avoid it being overridden. If you do need the trim under a very rare and unlikely scenario, you can just use the mouse cursor to do the manual adjustment directly in the cockpit instruments.
So based on all this information. You need to go through all your controls that you have connected to your PC that MSFS has detected. Pick one way for you to manage your Trim based on the hardware and the type of buttons and switches or sliders that you have. Then set your control profile to bind the correct Trim command type (as I explained above) to the correct button/switch type and commit to it. Then go through your other controls and Remove everything that is bound to the Trim function (Set, Toggle, Axis, everything). This way you only have one thing that controls your Trim, and as long as you set this correctly. The Sim will not misbehave and getting “phantom inputs” that changes the Trim, Flaps, Spoilers, everything when you pause the sim with ESC.
Sorry for the long explanation, but I hope that this gives you a better understanding on how the control options work in the sim, so that you can set your control profiles appropriately without it giving you any issues. If you do have issues, this post should give you enough knowledge to troubleshoot what is happening in your controls.
Yeah, the T.16000M profile looks good. But you need to check your TWCS throttle, then Keyboard, and Mouse as well. If you see any Trim commands on them Remove them all.
Fairly sure Neo’s suggestion was right in that it was multiple bindings. I hadn’t messed with the throttle aspect of my new controller. This thing has lots of binding options which is really cool. Obviously though there are some duplicates that I will need to sort out. When I unplugged just the throttle part, the trim #'s were no longer out of whack so that pretty much confirm’s Neo’s theory.
I can’t seem to get it right. I can’t figure out what bindings I have that are duplicate. I eliminated buttons on my stick and put the bindings that were on there to the throttle part.
Can someone help me figure out how to locate the specific problem?
Can you post a screenshot for everything that you have in your control profile by searching with the “Trim” keyword for each and every hardware you have connected.
That means we need a screenshot of your Keyboard with the “trim” keyword being searched. Then also your mouse, then T.1600M, then your TWCS as well.
Remove all your trim bindings from your keyboard. They should all be blank.
Mouse is okay.
Joystick is okay.
As for your throttle quadrant just Pick one trim. Either you use the Elevator Trim Axis, or your Nose Up and Nose Down trim. Don’t use both.
That being said, I’m not sure how the Elevator Trim Axis works with Joystick Slider X as I don’t know how to use it. Can you check to make sure your Joystick Slider X is not bound to any other command.
If you pick the Elevator Trim Axis, remove the Elevator Trim Up and Elevator Trim Down. If you pick the button 2 and Button 3 for the Elevator Trim Up and Elevator Trim Down, then remove the Elevator Trim Axis.
Also, do you have TFRP rudder connected to the throttle quadrant? If so, just make sure they’re bound properly to the rudder axis and not the trim. If you don’t, make sure you remove any of the axis that would have been connected to them.
However more stronger than that, I feel that @Neo4316 is a super great person to help out a complete stranger. If I’m wrong, it’s probably on the former.
You helped me. However since SU8, I have been having major lag issues. My buddy helped me and I thought the problem was fixed, but it’s freezing again. I think I saw a thread on it though so I’m going to read that thread.
