Ddg1500

I do tried central trim mode, honestly its even worse, so i would still stick to instant trim, and that's better yet still problematic

Thank you, and please take notice of my track file and response

Here, sorry for my mistake as i been raw on track file, please notice the excessive steer after rudder trim during taxing and increasing & reducing collective, which is due to a inadquately tuned rudder trim model that set the new center of the rudder excessive to the torque that casue it to continously over steer, furthermore, all my rudder trim performed in the track file is intended to hold the aircraft straight, i pick a rudder spot that I feel is right to keep the apache straight intead of oversteer, compenating the twisting force of torque，yet when I trimmed the rudder, the apache always oversteer, and that where the problem is, as i don't encounter any of those issue on mi24 Ground taxi trim 1.trk Ground taxi trim 2.trk Ground taxi trim 3.trk

Here is it, do you see the overreaction after rudder trim during taxing on the ground , or the oversteer during rapid reduction in rpm( and is also corrected by rudder trim yet it still overeact due to rapid reudction in torque) and i know that when "tailwheel unlock" is selected the apache would be very sensitive in yaw and need to be immedately trim after increasing collective, and I flew dcs mi24(which also have a road wheel) or huey(which don't have a rudder trim) without encountering any of the issue of apache on ground taxi trim, those two helio performs comfortably nice on trim(espeically mi24) on any situation(transistion, hovering taxing etc), where apache would just like to over yaw or steer after rudder trim. which is probably due a not well tuned algorithm that set the center of the rudder after trim excessively left or right that ultimately keep it oversteer during taxing, real helicopter use a mechanical system to keep the new trimed rudder position as the new center, whereas in dcs, many players use only spring loaded rudder with no damper, as a result, using a algorithm to tune and compenate to simulate the rudder trim was produced, and that's where the problem is. i know that the ED Beta Tester say it is my perosnal issue of control and understanding of aircraft that lead to this problem, which i respectfully disagree, and before having a sudden fervent passion on apache, i have flew mi24 for a considerable while, while using both "instant trim(ffb friendly) setting on both cyclic and rudder using full virpil base and rudder(spring loaded no ffb no damper) , the rudder trim(or both trim) never overeact and was right on spot. I have realized that many of my previous post on this issue has been worked and i am very grateful, but there is still some loose end left, I will continue to accmulate my experience on ah64, and i hope issue can be solved. rudder trim taxi 3.miz rudder trim.miz taxi rudder trim .miz Rudder trim taxi 4.miz

There is stil some rudder trim problem during ground taxi, and i don't rely on SAS to fly the aircraft, could you take a look?

Okay, I’ll try it when I got my damper,

Okay, great thanks, but there is a problem, in ah64, when you trim the rudder, the control automatically consider you new rudder position as the new “center”, which is not that well simulated with damper, as it only keeps you in position instead of center it, how is that suppose to behave in damper?

If I remove the rudder springs, just only keep the damper while tighten up a bit, and set the rudder trim to other option, will the ground taxi rudder trimon ah64 be better?

I decide to buy a rudder damper, will the damper help improve ah64 ground taxing?

virpil ACE spring loaded rudder, haven't change it for a considerable while Agree, hope they slove it someday, which already takes considerable while, i probably no going to fly ah64 until the issue got fixed

The problem is noting being solved, have anyone notice?

Hello, there is some rudder trim problem during ground taxing when then tail wheel unlock is selected. I know when tail wheel unlcok selected, apache will be very sensitive in yaw even on ground, that's why it need to be immediately trimmed to prevent oversteer And with the increase in collective to 30%rpm(as instructed in the tutorial), the increased torque will twist the aircraft to left or right. It was at the moment that the rudder trim overreacted. Here is my file rudder trim taxi 3.miz rudder trim.miz taxi rudder trim .miz

3.miz

Thank you, i don't know there isn't SAS ofduring transition, There is still some rudder trim problem during ground taxing, other part its been much better ground taxi trim 2.miz ground taxi trim.miz

Got it,there is still some rudder trim overeaction during transition, occasionally during rapid change from crusie to hover, the rudder trim during transition still need some work

Hello,i'm fervently grateful of the correction of trim overeact problem during transition, hover and other situation, thank you i have done at least 4 test recently, each lasting at least 1.5hrs to test the trim especially rudder trim at different state. There is still a salient trim overreaction during take off, just after the wheel leaves the ground with collective increasing, it's at this state that there would need a immeidate and massive rudder trim to counter and correct the turn force of the main rotor due to increased rpm, the rudder trim would overeact significantly, and its troubling. Also, i hope there is also a more comprehesive and general review about the trim behaviours (both cyclic and rudder) at different state of ah64, i wish it could be more comfortable and safe to use. Real life heli pilots don't have such issue as their controls will be remembered in position right after the press the trim button, and they trim highly frequently, with their trim don't result in overeaction unless they intent. The dcs guys, however, rarely have that luxury, so the trim mechanism need to be well tuned to the spring loaded device. Here is my track file TrIm test takeoff.miz

Hello, recently i feel that the rudder trim is much better improved, with much less "overeaction" in many situation, this include low speed hover, cruise etc, those improvement make flying apache much more comfortable However, there is still some situation that still cause rudder trim overreaction. Like during transition from curise to hover close to the ground, the rudder trim would still overreact significantly that could shift the nose to another direction dangerously. the rudder trim and cyclic trim performs comfortably well, expect at this situation. Here is my track file TrIm test transition.miz

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

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

Exactly, I have the same issue as this thread

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

Phoenix is not so good against fighter, nearly every fighter in this game can shake it off easily

I do trim, in fact

Still pretty sensitive, maybe even more, sweeping wings back would make tomcat more easy to sink down, I don’t like that

Tomcat is like a Dodge Viper, very powerful,very fast, but not much safety, no FBW, no G limits, little glass cockpit. With some pretty analog fly control, it's clearly functional, but not very effective, and it's optional, you could switch it off if you want(just behind the throttle). Due to this reason, tomcat is pretty naughty at aerial refueling, precision control is HARD to say the least, and maintaining connected for long time is even harder. The fly control won't correct it for you if you oscillate, you would need a lot of hand + throttle work to correct that. Furthermore, due to the fact that there is no g limits, with a variable sweep wing mechanism, you could actually tear off the wing if pulled too hard. Overall, a pretty hardcore aircraft.