Pixel of Life

So the bold part is the issue then. Why does it do this? What's the purpose of it suddenly switching to assist mode with no warning, instead of simply maintaining full left or right trim once it runs out of control authority, and expecting the pilot to override it which would be much more predictable and controllable? If realistic, in what situation would this behavior be useful? If I'm just trying to make a slow turn, I don't need or want it to "assist" me because it's actually doing the opposite by making unexpected inputs. And if I need to make a quick turn to evade an incoming missile or whatever, that little blip of left or right yaw it gives me makes little to no difference because I'll be giving it a lot of pedal anyway.

I don't think any of those timestamps are relevant. Again, look at the exact moment the heli starts yawing. Watch it in full screen and slow motion if you need to. Look at the control overlay when that happens and watch what the autopilot yaw channel is doing. You can clearly see it more or less matching my manual inputs until 0:44 where it suddenly jumps to the left of my current pedal position. 1:14 is much easier to see. The yaw channel indicator is all the way at the left edge of its range of movement, and when I apply enough right pedal, the autopilot suddenly just gives up and removes some of the left yaw trim it was previously using, which causes the nose of the heli to snap to the right. And again at 1:42, you can see it matching my inputs and then suddenly jump to the left. If it had only happened once, it might've been an accidental input on my part. But three times in a row, with alternating left-right-left turns, and with the autopilot yaw channel making the same weird movement every time? No way. I'm 100% convinced that the heli itself is doing something it shouldn't be doing (or something that's not properly documented).

But if you look at the behavior of the heading hold system (like I said, pay very close attention to the green indicator just before the nose swings to the side), it doesn't simply disengage and stop trying to maintain the heading. It suddenly switches from fighting my inputs to amplifying them and actively tries to nudge the heli in the direction I'm trying to turn. It's this behavior that throws me off and causes the terrible wobble, and it shouldn't be happening if, as you say, the heading hold disengages (i.e. turns off and stops doing anything, which is the only way you can interpret that word) when you give it enough pedal input. It's completely unexpected and there's no way to anticipate it.

I don't have a track I can post right now (I have one but the file is too big), but I did a simple test where I came to a hover a few feet off the ground, engaged position hold mode, and then made a few very slow and gentle left and right turns. What I noticed is that the yaw autopilot seems to be making a sudden erroneous input in the direction I'm trying to turn which destabilizes the heli. Luckily I also recorded a video of this: Pay close attention to the green autopilot yaw channel indicator on the controls overlay when I start my first turn at 0:30. I'm very slowly and carefully applying left pedal and the autopilot keeps fighting me, and then at 0:44, you can just about see the autopilot make an unexplained yaw input to the left which causes the nose to snap to the left. And then again, at 1:14 when I'm trying to make a right turn, the autopilot makes a sudden input to the right. And again, at 1:42 when I'm trying to make another left turn, the autopilot makes a sudden input to the left again. Can anyone else test this and verify? This is on latest Open Beta.

Yes, I know that, but I was asking what the difference between holding and tapping is. In both cases the magnets are disengaged and re-engaged and the center point is reset to the current position. So why does the manual specifically call for holding the trim while you raise the collective, instead of tapping it when you reach the desired torque value? Is it just to make the controls easier to move since you're not fighting the magnets?

What exactly does holding the trim do compared to just tapping it? The manual doesn't say.

When you tell George to search for targets, he moves the TADS at a constant rate until it lines up with where your helmet sight reticle is pointing. This means you need to keep looking at the target until George is done. If you look away too soon, he'll point the TADS in the wrong direction. This should be changed so that George doesn't try to chase the helmet sight, but instead remembers the direction you were looking in when you pressed the button.

According to the manual, George should verbally report the type of the target if he only finds one, so I guess it's either broken or not implemented yet.

There is. Not in the heli itself, but if you go to the module's special settings, you can set the rudder trim mode to "no springs or FFB" to turn it off.

I also started having this issue today when I switched from stable to open beta, but for me, it doesn't work in the pilot's seat. The hat on the cyclic stick moves, the indicators on the on screen trim overlay also move, and I can hear the motors running, but it doesn't actually do anything. The stick just returns to the center position no matter how much I mess with the trim. EDIT: Nevermind, I had force feedback turned on in the options. It's working now.