Jump to content

Recommended Posts

Posted

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

  • Like 1

W10 Home 64Bit, Intel Skylake I5 6600K 3.50GHz, ASUS ROG Stryx Z270F MoBo, 64GB G.Skill RipJaws V DDR4 3200 RAM, Samsung 960 Pro 512GB M.2 SSD (OS), Samsung 850 Pro 512GB SSD, 2TB Seagate SDHD, 2TB WD Green HDD, Gigabyte 3060 12GB VRAM

Posted

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.

..

  • Like 2
ASUS 2600K 3.8. P8Z68-V. ASUS ROG Strix RTX 2080Ti, RAM 16gb Corsair. M2 NVME 2gb. 2 SSD. 3 HDD. 1 kW ps. X-52. Saitek pedals.


..
 
Posted

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.

  • Like 1

I enjoy creating content for the community.  Missions, lua scripts, and kneeboards.  Follow my content on my Discord, GT’s Runway.  https://discord.gg/GHH7bVZ7K6

 IRL: Private Pilot, UAS Test Pilot, Aircraft Designer, and... eh hem... DCS Enthusiast

 

Posted
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

Posted

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

Posted
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. 

I enjoy creating content for the community.  Missions, lua scripts, and kneeboards.  Follow my content on my Discord, GT’s Runway.  https://discord.gg/GHH7bVZ7K6

 IRL: Private Pilot, UAS Test Pilot, Aircraft Designer, and... eh hem... DCS Enthusiast

 

Posted (edited)

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 by Art-J
  • Like 2

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted

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

Trim-max.jpg

Trim-wrong.jpg

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
Windows 11 Home - 64    CH Products Combatstick, Throttle and Pedals

  • Recently Browsing   1 member

×
×
  • Create New...