The instant trim setting on rudder would overeact at very slow speed& hovering&landing

[Ddg1500]

Recently, i became a attack helicopter.

I find a comfortable trimming mechanism extremely important to fly apache at any situation.

I used to use the central trimmer setting for both cyclic and rudder, but i immediatly realize that it is very uncomfortable and imprecise, especially during hovering and low speed landing, and could be very dangerously uncontrollable.

So i use the instant trim(ffb friendly) setting to fly the apache, the cyclic trim works ok in this setting on both curising and hovering, the trim control acts well and it would control the flight path and sink rate just well, and it also acts good in hovering and low speed landing.

However, it is not the case for rudder trim on instant trim setting, it works well during cruising, but would slightly over react during hover or very low speed flying close to the ground while trying correct the direction with rudder. 

The rudder trim(instant trim setting) acted a little more than it should at low speed & hovering, and it sometimes it overeacted so much, it would move quite away in direction. And i have to rudder trim again and again to correct that.

I use a full virpil set with rudder, stick,base and throttle.

And i wish there is also a cross check between all the helo module in dcs about this problem

I have a track file,but i didn't do track file often so it could clumsy.

 

 

Low speed&hover.miz

[Tholozor]

Yaw instability in the rotor model has been reported and is being worked on, is this thread similar to what you're experiencing?

 

[Ddg1500]

10小时前，Tholozor说：

Yaw instability in the rotor model has been reported and is being worked on, is this thread similar to what you're experiencing?

 

Exactly, I have the same issue as this thread

[Ddg1500]

12小时前，Tholozor说：

Yaw instability in the rotor model has been reported and is being worked on, is this thread similar to what you're experiencing?

 

But this problem is not being fixed, even til now,and it has been month since this thread being posted, what's the problem

Edited yesterday at 03:51 AM by Ddg1500

[Ddg1500]

I have spent at least 2 hrs testing the trimming with "instant trim (ffb friendly) setting" on rudder

I have realized that the "over reaction" in rudder trim has been much improved at hovering or low speed(>40knots), the trimming is much more accurate with significantly less over reaction (happens when there is only very small movement in rudder) .

However, i find that there is still some occassional trim over reaction at certain state such as during transition (rare but exist) or when there is a need to trim with significant rudder movement during low speed or hover(apparently more frequent).

The major issue of trim over reaction has been basically fixed, but there is still some loose end, i wish it could be solved.

Apache is a sensitive aircraft to fly, although not as much as gazelle, it still need a lot of trimming to keep it stable, and those over reaction is annoying 

Trim test 2.miz TrIm test.miz

Here is my track file

Edited yesterday at 12:11 PM by Ddg1500

[Raven (Elysian Angel)]

20 hours ago, Ddg1500 said:

But this problem is not being fixed, even til now,and it has been month since this thread being posted, what's the problem

That’s because the underlying cause is quite complex, and takes time to properly implement.

The reason why people have so many problems with yaw control is because of the rotor model that’s currently being used. There have been plenty of problems in the past with torque and torque onset rates, with varying degrees of fixes being made, but until we get the new rotor model, these problems will persist.

We need the cause to be fixed instead of patches for symptoms.