Floyd1212

That is probably just a DCS map zooming LOD anomaly. It also occurs on Sinai with parts of the Nile River Delta; when zoomed out they look green like land, then at some zoom step the land goes away and you see patches of water where they should be.

Correct. Set the MAN range and you're good to go.

It looks like when you edited the MGRS coordinates of your current position that come up in the KDU and changed them to the new coordinates, you didn't change the Grid Zone from 34W to 35W, and there is no MU within the 34W Grid Zone.

Will it let you boresight again if you want to? Yes. Has it already been done for you? Yes. On a cold-start aircraft you will see the "IHADSS B/S REQUIRED" message at the lower left of the High Action Display until you perform the boresight. On a hot-start aircraft you should not be seeing this message.

If you spawn in a hot-start aircraft, where the boresight is already done for you, is your gun accurate then? If you set your MAN to Auto it will do its best to calculate the range to the target based on your altitude and look-down angle, but it assumes you are on level terrain, so it isn't so good in hilly areas. I personally set mine to 500, and when I am in close to gun trucks and infantry, it is dead-on. Setting it to 1000 should give you similar results. I let George lase and "snipe" with the gun using the TADS if I want to engage something much further out. Can you record a quick track of your boresight procedure and share?

It's flyable, for sure. I would not say that the change in yaw behavior is likely to cause anyone to crash into the ground. But it does impact slow speed hover taxing, aligning for rockets, heading changes while in a hover to engage a new target, trying to land on a small FARP pad, etc. And the sad part is that engaging ATT Hold isn't that much better as a result of the change that was made.

And the even more obvious (and less subjective) bugs, like George's poor target tracking, and the ACQ not working when FCR is active, points to a clear problem. Not sure what the threshold is for deserving a hot fix after a bungled update like this, but I guess we didn't quite get there. I'm looking forward to these issues being resolved in the next patch... Right?

Do you have a track file you can share of this (not) happening? From my experience, George will spot infantry just fine with the TADS when close enough, but there is some distance (unknown to me) where he won't be able to spot them.

You may not be aware of the Coordinate Converter Tool by FalcoGer that helps with this type of setup. Not quite the same as doing it in the ME and having it already loaded in the aircraft when you spawn in, but you can capture all those points with the crosshairs on the F10 map, then hit "Transfer" in the tool and sit back for a minute or two while the data is entered in the KDU automatically. You can also save those coordinates as a file that can be distributed to other players for them to load into their aircraft. So these 8 coordinates captured in the tool: Become these points on the TSD: And I agree that having more navigation assistance from George would be nice to see in the future.

Sometimes DCS will remap controls after an update, often for devices with axis that you never even intended to use that way. You can see in this screenshot just after you "lose power" your throttles have been pulled back to idle. That's when George starts complaining and tries to repeatedly arm the aircraft.

George saying “Armed” over and over again happens when the aircraft loses power while he wants it to be armed. When power is lost, the aircraft is no longer armed, and he tries repeatedly to rearm it. This sounds like a binding issue. Maybe an axis on your pedals or an Xbox controller?

I'm guessing ED is not advertising that the Apache can be flown solely from the CPG seat at this time. So, until ED fleshes out George as PLT to include startup and shutdown, your best bet is to get things up and running from the back seat, then switch to the front and go from there.

I think everyone can agree that the FM is still a WIP. ED has said it, and those of us that fly it have said it. Every so often we get a patch where ED has worked on the FM and made improvements, and we adjust to the new changes and life goes on. Over time, the FM has gotten much better, and I found the Apache quite enjoyable to fly. It had some quirks, but it was manageable if you put time in to practice and develop muscle memory. I don't think I am out of place to say the reason this specific thread was created 10 days ago by DaveTC is that after the last patch there was a noticeable change in the behavior of the tail rotor or SCAS that seemed like a step in the wrong direction. Instead of an improvement to the FM, this feels like a regression. And because there was a patch around Christmas time that specifically improved the behavior of the tail rotor and SCAS in low-speed flight, and while in a hover, there was concern that whatever changes that were made for that patch got "undone" with this one.

So you are saying this should be “Joystick Without Springs or FFB”? That sounds like one change they could make to make things clearer.

It means there is a bug...

If you are seeing file size restrictions, you are bumping up against your attachment limit of 200MB for the forums. Go to your user drop-down menu at the top-right of the page and view your attachments. Delete the biggest/oldest ones first, as needed to free up some space. (Moderators: It would be nice if users could earn more storage based on some metric, like number of posts, or solutions provided, or "liked" content. Something to allow users to build more storage capacity to continue providing rich (and helpful) content for the community.)

Thanks!

Just so we are all on the same page, the behavior of the tail rotor and the yaw channel of the SCAS was improved in patch DCS 2.9.11.4686 - 24.12.2024, and everybody was happy. This was a great improvement to the way the aircraft handled in low-speed flight, and while in a hover. Then, with the release of DCS 2.9.14.8222 - 19.03.2025, the improvements made in December seem to have been "undone", without any mention in the patch notes about other changes to the FM. The only thing mentioned in the changelog was relating to the Position Hold oscillations. I think everyone is trying to understand why this would have changed so drastically again, and if the tradeoff is worth it for the slightly improved Position Hold activation? Hopefully this can be restored back to the improved state we had been enjoying for months now in the next patch, and not have to wait during what can be a very long Early Access period.

Yes, as noted in this other bug report:

Thanks for the update

Since the recent patch to 2.9.14.8222, George is not getting a good IAT track on the center of mass of his target. The patch prior to this update (the one that forced him to switch to FLIR every time you told him to track a target) seemed to improve his tracking. But now, he will get his IAT lock on a target, but you can't tell how good of a track he got unless you switch him to DTV for a better look, or you tell him to rifle a Kilo and he misses. I can't post the track file, but here are some screenshots of his more questionable tracks from tonight.

Back when the Apache was getting FM updates on a more regular basis, I used to record a video of a short flight before installing an update, then record another video of the playback of the same track after applying the update. This would often result in the helo crashing after takeoff, or flying off somewhere completely different, as the same inputs made during the track playback before and after the update would result in very different behavior. Unfortunately, I didn't do this ahead of applying this update. Maybe I will start doing this again, as you never know when we might get a regression of some function or FM change.

Just flew for a couple hours and it is definitely a regression back to before they improved the yaw channel stability. While in a hover with Position Hold enabled, trying to use the pedals to rotate left or right results in over-correction and oscillations.

I feel like the yaw is twitchy again, as well. Prior to this patch they had greatly improved the behavior of the tail, but I feel like they have regressed to a previous state when they messed with the position hold in this last patch.

You can still set it up in the cockpit, but the MBR DIR may not be the best option. Depending on how the mission is setup, or if there are dynamic spawns, the MBR DIR may not know about the other Apaches in the mission. You can set other members up manually by entering their C/S and ID, instead of using the MBR DIR.