Floyd1212

With the current behavior of the aircraft and hold modes, what works best for me is option 3. Disable ATT Hold (you can keep ALT Hold enabled) and control the hover manually, then swing the nose around slowly, then settle at the new heading and re-enable ATT Hold. You used to be able to coax it around gently with the pedal while keeping ATT Hold enabled, but that technique doesn't seem to work as well anymore. And for me, pressing and holding FTR is asking to lose control in all axis very quickly.

Any info on how to actually accomplish this? If you can get him to use IAT, he won't drift off of targets like he tends to do.

I don’t think that is an Apache thing, but a DCS-wide issue. here’s a great thread about upgrading to higher quality chart maps, but one of the most recent posts mentions the “holes” in the Caucasus maps at certain scales.

Ah, thanks for the correction. So, I can still hope to use the FTR hold method in the future, not because there will be more rate damping in play when FTR is held, but because the helo in general will be more stable when there is no rate damping being applied? I'll keep doing what I am doing until that day comes, then reset my brain to relearn how to use FTR properly.

To me, this was the biggest compromise to make with a sprung cyclic. I never liked the idea of having to "unwind" the trim you have built up in order to get back to a zero state. Seems counter intuitive, and not at all what you do in a real helo (as you know). I came up with a solution using Joystick Gremlin to temporarily "disconnect" the signals from my cyclic to be able to use Force Trim Reset for a smooth transition back to a zero-trim state. I'll link to it here as it has been a while, and there are probably some new Apache pilots that might find it useful.

With the current progress of the module, FTR is not working as it should be. I am not a SME, but from what I gather from other posts, when you press and hold FTR the system is supposed to continue to assist in keeping the helo stable, but relax the way it fights back at your inputs so you can make minor adjustments. However, in its current state, it appears to completely disable any assist, and the aircraft gets super wobbly in all axis, all at once. You can see in the Controls Indicator for as long as you are holding FTR, the red and green marks follow your controls 1:1, and as soon as you release FTR the green mark starts to deviate again and apply inputs in an attempt to keep the aircraft at a stable heading. If the system were working as intended, you should still see the green marks working to stabilize the aircraft while FTR is held, though not as aggressively. I personally use the tap method, but not frequently. I will trim when I am in a hover (and use the ATT and ALT Hold modes as needed), then when I am ready to get moving again I won't trim again until I am in stable flight with the flight path vector where I want it, then tap FTR and relax my stick to center. When I am transitioning back to a hover, or coming in to land, I use the Force Trim Reset command to zero out my controls and manually come to a hover or land. I look forward to the day when I can hold the FTR and have it not get completely squirrely, but for now I will keep using the occasional tap method.

The PrtScrn button works for me. I guess this is the default key for taking screenshots in DCS? It will put them in your [user]\Saved Games\DCS.openbeta\ScreenShots folder

So this means you aren't using FTR again for the rest of your flight? Meaning you aren't able to take your hand off the cyclic to do something in the cockpit? Have you tried holding the FTR while making your small pedal adjustments? As long as you are holding FTR, the SAS will not "fight" against your inputs.

I posted a short video in this other thread (before it got locked) demonstrating a sure-fire way to induce a snap roll. https://forum.dcs.world/topic/324117-uncommanded-catastrophic-rolls/?do=findComment&comment=5202767 With the tail rotor applying forces above the CG, giving it a lot of left pedal will create a rolling moment to the right. Combine this with a left turn, and a quick drop of the collective and you can induce a roll to the right. Be gentle with the inputs, and you can avoid situations like this. It's like the Porsche 911 of the 80's. It would only take you one time to learn not to lift while the tail is getting loose...

This is a known bug that has been discussed in other threads. https://forum.dcs.world/search/?q=tail&quick=1&type=forums_topic&nodes=780

Here is an example of what can induce an uncommanded snap roll. This is being way to aggressive on the inputs while the aircraft is in an unbalanced state. I'm not a SME, so I can't say if this behavior is accurate, but with the current way the Apache is modeled in DCS, this will get you into trouble every time, so don't do it. Notice I have quite a bit of left stick, trying to bank left toward the "target", but the other forces at play easily overcome my left stick and I end up making a full 360 roll to the right. This is the track from the above clip as well. Induced_Roll.trk This can also happen when aggressively side-slipping while trying to keep the nose pointed on-target. For example, I'm in a hover and my CPG has a missile in the air on a T90, and the T90 fires a sniper at me. If I aggressively slip to one side or the other to dodge the sniper, while trying to keep the nose on target, the aircraft can easily be upset and roll over.

Do you have any examples of this? I don't think I have seen anyone saying they are just flying forward in a straight line and the helo suddenly rolls on them for no reason.

This must be a configuration issue local to your machine. When I run your track, the George UI shows up in the proper locations for me. I'm running 3440x1440 on my main monitor, with additional displays below my main one for exports. (3440x2040 combined) You will also notice that other aspects of your cockpit environment are not carried over in the track, like the default zoom setting. And you can see I have centered my CPG's default view on the TEDAC, so when I replay your track, I still get my view settings. Are you running multiple monitors?

I think calling the changes since the last OB patch "dramatic" is being a bit over-dramatic. Go watch the video I posted further up on this page. Toward the end I replay a track recorded in the previous OB version, and in the current OB version the helo lifts up and starts to drift back and to the left. It doesn't suddenly roll over on to its side. It would appear you don't need as much left and aft stick when you pick up in the latest build. This is also confirmed when I pick up for the first time after patching and she wants to slip left because I was giving it the same left stick I was used to. The changes in the behavior of the aircraft are subtle, but they are there. It might not have been a change to the " core flight model" as ED discussed on page 3 of this thread, but to say the changes make it impossible to fly now (as others have implied) is a bit much. Post a track of what you are experiencing and let the community try to help figure out what's going on.

In the second track, it looks like you are trying to gun a target below you, and as you fly over it and try to get eyes on it again, you end up slipping sideways a bit. I noticed last night when flying (and trying to keep my nose on some infantry on the ground) that just a little bit of pedal while side slipping can induce a rolling tendency. This has always been the case, but it does feel more pronounced now after the recent patch. CTRL+Z to accelerate time SHIFT+Z to return to 1x speed (Not always recommended when a lot is going on, but just to skip past the data entry, and admiring your 1-foot hover in 3rd person, it's fine.)

I hadn't applied the most recent patch from 4/13/2023 yet, so I thought I would try an experiment... I recorded a short video with some basic maneuvers around the airfield, then applied the patch, then immediately recorded another video flying the same short exercise again. Then, just for grins, I tried replaying the track from before the patch back again after I applied the patch. (Spoiler alert: the replay didn't get very far before things got out of hand.) In general, I felt like the aircraft did behave a little differently upon first pick-up, but nothing major. Then while performing a 180 degree rudder turn with ATT Hold enabled, it got away from me for a moment, but I was able to get it under control. That is the only flying I have done since the patch, so it's hard to say what other differences I will notice after flying in a longer "combat" setting, and repeating the same maneuvers I am used to doing over and over. Note: The first flight does not have a voice-over, then there is one for the second flight, so I'm sorry if I startle you when I start speaking.

Please post a track or a video (with the Controls Indicator visible) so others can see what you are experiencing. I'm not sure how much or how fast you are dropping the collective, nor do I know how much a wild horse rolls, having never ridden one. (Yes, I understand capturing a video and hosting it is not a trivial matter, but recording a track is quite easy.)

Did you see the roadmap thread?

I only use Attitude Hold when in a hover. When in fwd flight I just trim to maintain my attitude. I use trim to reduce the workload when cruising, but when flying NoE or when coming in to land, I reset trim and don't set it again unless I want to take my hands off the stick, or establish a hover. When I do trim, I use the tap method (center trim mode). I would try the hold method more, but the hat I use on my Warthog is way to stiff to keep it pressed long-term.

I think the answer is: fly more and you will get used to it. All of the changes that have been made over time have ultimately been for the better. Yes, there is some short-term "this feels different" condition when a change is made, but keep flying and it will become the new normal. I personally haven't felt huge differences between patches. Yeah, when they messed with the tail rotor a while back, it took some adjusting, but after a couple flights your muscle memory is reset. If you are flying other stuff and coming back to the Apache every now and then, give it some time to settle back in.

Yeah, mine occasionally act up, too, and when I touch them I get phantom presses on the main screen. I run the utility again, which takes a few seconds, to sort it out again.

Why do you say the touchscreen has to be monitor 1? There is a utility in Windows that you go through and touch the screens that are touchable and skip over the ones that aren't. Does this method not work for yours? I run a configuration that looks like this, where monitor 1 is my main display at 3440 x 1440 non-touch, and the two smaller screens are 1024 x 600 and are touch-enabled for Helios.

Sounds like you haven't set your ACQ Source to TADS. In a hot start aircraft, this has already been set for you. In a cold start aircraft, you have to set this yourself. TSD > R6

If you are referring to this one, be advised you might need additional weights. I purchased that balance kit for my Virpil collective (with an Alpha grip on it), and the optional weights are barely enough to balance it on the furthest hole.

Maybe Virpil will also release a counter-weight accessory when this thing comes out, otherwise I expect the dry clutches will need to be quite stiff to keep it from drooping.