Elevator trim 27Nov

[MIDWAY]

The 11/27/25 Update reversed the elevator trim.   Not enough authority now to land on a carrier properly.  

[Roadhouse]

Indeed. seems symmetrically reversed. 10 degrees nose down behaves like nose up and vice versa. 

Edited Thursday at 09:10 PM by Roadhouse

[Scotch75]

Yes, I have just noticed this apparent reversal as well. I had to bind Nose Up and Nose Down trims opposite to what they were.


Sent from my SM-G998B using Tapatalk

[Razgriz10]

Yes elevator trim is completely reversed even with FFB.

[TehWiz97]

Cosign. Elevator trim is reversed and authority is reversed along with it. Somebody misplace a (-) sign somewhere?

[AG-51_Razor]

Doesn't anyone on the developer's side or the DCS folks even test fly this plane before sending it out of the hanger??!!

[Stevecat]

LOL I just tried it tonight and was hoping it wasn't just me.

[Holbeach]

Interesting one this.

Leaving buttons as is, the trim tab and cockpit indiacator are working correctly, but the effect is now opposite to the indication.

Reverse the buttons and the opposite occurs.

The worst of it is, the tab now does not have the same authority. Full nose up (indicating nose down) is not enough for a proper carrier landing.

I don;t mind a bit of work round, but I'm not using this.

Hopefully M3 will provide a hot fix soon.

..

[GTFreeFlyer]

OK, what i'm finding is that trim is backwards if bound to my hat switch on my stick. 

However, when using keyboard bindings it works correctly, tabs move in correct direction, cockpit indicator moves in correct direction, AND it also moves my FFB stick in the correct direction.  I think this might be how the devs tested it, because it is 100% correct if using keyboard binding.  I am deleting my hat switch binding until its fixed so I don't get confused in flight.

Again, it's working with the keyboard binding.  The bug is in the definition of other input bindings.

[MAXsenna]

OK, what i'm finding is that trim is backwards if bound to my hat switch on my stick. 
However, when using keyboard bindings it works correctly, tabs move in correct direction, cockpit indicator moves in correct direction, AND it also moves my FFB stick in the correct direction.  I think this might be how the devs tested it, because it is 100% correct if using keyboard binding.  I am deleting my hat switch binding until its fixed so I don't get confused in flight.
Again, it's working with the keyboard binding.  The bug is in the definition of other input bindings.

Excellent find!

Sent from my SM-A536B using Tapatalk

[nirsch]

same here - nose trim is revese

[MIDWAY]

I'm still having the same problem using the keyboard trim.   Not enough deflection since it goes the wrong way 

[GTFreeFlyer]

54 minutes ago, MIDWAY said:

I'm still having the same problem using the keyboard trim.   Not enough deflection since it goes the wrong way 

That’s strange indeed.  I did more flights later in the day after finding this and all is working normal for me.  I’ll try to grab screenshots of my settings later when I’m on my PC next. 

[Art-J]

Nah, I've been using keyboard for all trims since the module release, and the patch brought me pitch trim reversal as well. So - no, keyboard and non-FFB guys are affected too.

Didn't bother to swap bindings, though. Since there's a hotfix in the cooking with first C-130 tweaks, I hope M3 guys will throw in a quick fix for Corsair trim as well.

Edited 15 hours ago by Art-J

[ac5]

Here also my 5 cents…: only after the latest DCS update

2.9.2217790 I was also obliged to wrongly assign in the settings elevator

trim up to down and elevator trim down to up.

Taking off is not a problem with this workaround, but landing has turned out as quite impossible…

Why? Because the trim has larger setting up (20) than down (10)!

This being said, it is exclusively a bug that concerns the Corsair. 

All my other WWII birds, jets and helicopters (13) are NOT concerned by this newly introduced bug).

Please advise, Magnitude 3 LLC, please be so kind and correct this asap......

 

Mainboard: ASUS Maximus X Hero Intel Z 370

CPU: Intel 12-Core i7-8086K @ 4.0 GHz

Memory: 32GB Corsair DDR4-3000 MHz

Graphics Card: ASUS NVIDIA GeForce RTX 4090 24 GB

Monitor ASUS - Oled PG42UQ 41.5" @ 4K

1 SSD Samsung 860 PRO 256 GB

1 SSD Samsung 990 PRO NVMe M.2 4 TB

1 SSD Samsung 860 PRO 2 TB

Windows 11 Home - 64

CH Products Combatstick, Throttle and Pedals

[GTFreeFlyer]

Strange indeed that it isn't working for some keyboard users.  I went back to check everything, and what I said above still holds true, which makes it strange why it works for me but not others.  Here's my setup:

• Everything is very vanilla (using all the defaults)
• Trim, nose down: Rshift + ;
• Trim, nose up: Rshift + .
• ALL OTHER TRIM BINDINGS REMOVED from the other inputs, and from the axis category as well
• The only mods on my system are Tacview, SRS, and Vaicom Pro.  NO OTHER MODS installed.  Mods are known to mess with things.
• I have never in all my years playing DCS touch the lua file that contains binding info where you can customize your bindings.  I'm not even sure where this file is.
• Yes, I am using the latest update that came out a few days ago.

 

Screenshots below:

Prior to taking the screenshots, I held down the trim up binding (RShift + .) until the stop.

1. Bindings shown for keyboard only.  All others cleared out to make sure there are no conflicts.
2. Trim indicator moved to +20 degrees and trim wheel animation rotated the wheel backwards (pilot would pull backwards on the top of the wheel)
3. Before enabling my Moza AB9 FFB base, I took this picture showing correct movement of the elevator trim tabs.  Yes! They are supposed to move down for an up-elevator trim.
4. After enabling my Moza AB9 FFB base, I retook the picture because FFB will actually move my stick backwards, so you can see it here showing down trim tabs, and up elevator.

I can't think of any other related setting or screenshot to share.  If you need more info from me, just let me know.

I'm just as perplexed as everyone else why it won't work this way for others.  If you find out what the fix was for you, please share it here.

Again, I am experiencing exactly what everyone else is describing, but only when I used my preferred binding on the joystick hat switch.  Moving it to the keyboard fixed it.  Moving it back to the hat switch broke it again.  Settled on the keyboard binding for now.  I haven't tired using an axis for trim.

Cheers all.

Edited 7 hours ago by GTFreeFlyer

[Art-J]

^ Mind you, It's not about trim animations. Animations are indeed perfectly fine, both for trim wheel, indicator and tabs. It's the flight model physics that is reversed.

Swapping trims is a walkaround, but because of aforementioned different up/down movement ranges, it's not always sufficient.

Edited 7 hours ago by Art-J

[GTFreeFlyer]

19 minutes ago, Art-J said:

^ Mind you, It's not about trim animations. Animations are indeed perfectly fine, both for trim wheel, indicator and tabs. It's the flight model physics that is reversed.

Swapping trims is a walkaround, but because of aforementioned different up/down movement ranges, it's not always sufficient.

Thanks for adding this.  I knew I missed some detail.  Yes, in flight the physics and model are also working properly in the correct direction, for me.  Nose trim up, brings the nose up and allows me to fly nice and slow hands off, just modulating the throttle gently for climb/descent rate.  

[ac5]

29 minutes ago, GTFreeFlyer said:

Thanks for adding this.  I knew I missed some detail.  Yes, in flight the physics and model are also working properly in the correct direction, for me.  Nose trim up, brings the nose up and allows me to fly nice and slow hands off, just modulating the throttle gently for climb/descent rate.  

Hi, we can do everything we want at our end, but only Magnitude 3 LLC can fix this...

As Art-J correctly stated, there is something seriously wrong with the elevator trim / flight model 

of ONLY the Corsair, introduced after the latest DCS update 2.9.2217790. 

Before then, Takeoff - Landings on land were perfectly possible, even Carrier landings with struggle.

Now it is indeed possible to take-off but pretty much impossible to land........ !

[Art-J]

1 hour ago, GTFreeFlyer said:

Thanks for adding this.  I knew I missed some detail.  Yes, in flight the physics and model are also working properly in the correct direction, for me.  Nose trim up, brings the nose up and allows me to fly nice and slow hands off, just modulating the throttle gently for climb/descent rate.  

Now that's crazy. Are these RShift ; nad . bindings default ones as they come from M3 or are they yours? I changed them right after installing the module and setting it up. I don't want to click "reset to default" because it will restore everything.

I'll re-binding pitch trim only again and see what happens.

[GTFreeFlyer]

1 minute ago, Art-J said:

Now that's crazy. Are these RShift ; nad . bindings default ones as they come from M3 or are they yours? I changed them right after installing the module and setting it up. I don't want to click "reset to default" because it will restore everything.

I'll re-binding pitch trim only again and see what happens.

I don’t remember ever changing the bindings.  They should be default.  I was always using my hat switch for trimming all of my modules up until this moment with the Corsair.  

[GregP]

It's easy enough to compare the old and new joystick and keyboard Lua files to look for what sounds like a swapping of plus and minus somewhere; as I haven't updated yet, I'll do that tonight and report back.

In the meantime, for those who have this issue, I would imagine that using an external app like Joy2Key would let you assign the key combination (rather than the actual trim command) directly to the joystick hat, and that should work.

One other thing that occurred to me: the changelog notes that FFB pitch trim was modified, so I wonder if those that have "FFB Enabled" checked in the options menu are seeing different behavior than those who do not.

[Art-J]

Rgr that, must be defaults then.

Well, I rebound to RShift ones, tried Caucasus free flight mission, then changed them to my preferred cursor keys and loaded the mission again. In both cases, back to square one, unfortunately, ie. animations are correct, physics is reversed. That's puzzling.

[Art-J]

4 minutes ago, GregP said:

One other thing that occurred to me: the changelog notes that FFB pitch trim was modified, so I wonder if those that have "FFB Enabled" checked in the options menu are seeing different behavior than those who do not.

Good suggestion. You mean "Force Feedback" window in Misc options? Yup, I've got it off (not being FFB joystick owner). Turned it on then just to see what happens, but it didn't help. Bummer.

[ac5]

Sorry Guys, but in my opinion you are all struggling for nothing...

As I mentioned, we can do everything we want at our end,

but ONLY Magnitude 3 LLC / ED can fix this,

because they introduced this bug after the latest DCS update 2.9.2217790.