Emme

What about Steam users, do we need to opt out of beta at one point or will it automatically make the switch?

Thank you guys for the replies. Completely missed out on that top right corner box, but that does help a lot to clarify what's going on. O7

Hey there. I was wondering if the FCR will have some sort of declutter or zoom function at one point? Not sure if I'm missing something on my end, but I find it very hard to tell how many returns in total the radar is showing due to the symbology being cluttered all together. How to tell how many targets there are when using the FCR? Another thing I don't seem to understand fully, shouldn't the returns disappear after destroying a certain target? Actually I did not find a way to really tell what target has been engaged already due to the FCR cycling through already engaged targets. So it often happens that I'm shooting at the same target twice, while other targets stay completely ignored. (btw I know there's a little cross showing what target has been engaged, but that's often just completely impossible to read) Thanks for any input. Best regards.

A track file is not needed, this was all a mistake on my end just by trying to lift a max weight helicopter here. I reduced the fuel like others have mentioned and now I'm all fine again. But anyways, thank you very much for the help. Appreciate it. o7

It's just that I never had any issues with the setup, but maybe it's just modeled more accurate now than it was before. Ok, so I'll just have to adapt to this and lower my weight then. Anyways, thank you guys for the quick replies. o7

Anyone else noticing issues with the Apache not being able to gain enough lift? When flying missions I often find myself in situations where the Apache can not gain enough lift anymore. For example I'm in a manual hover @95%-100% rotary power, but the Apache just refuses to lift up. Using standard loadout: 8x AGM-L - 1200x 30mm rounds - 2x hydra rocket-launchers - 100% fuel Before 2.9 I never had any issues in getting enough lift with that setup. A TrackFile will be uploaded later today.

I was checking out the new update with the "Pretense" Caucasus and Syria sp missions. Hot started on an airfield right at the frontline, so ToT was like a few minutes into the mission. In both missions I ran into the same situations of having perfect conditions for Hellfire shots, completely within' launch parameters, in steady hover and clear LOS on the target, like I already said in my previous post. I know how the engagements work, both as pilot and co-pilot, I'm almost exclusively soloing the Apache since it launched and had hundreds of successfull engagements since then on- and offline. So the procedures and settings are well known. The strange thing about all of this is that today when I tried to make a track file everything worked absolute fine like it usually does. I did not ran into any similar problems. So there must be some circumstance or condition that is causing a "high" chance of Hellfire's to miss that I'm yet not able to reproduce. But I will investigate this further and will upload a track file as soon as possible.

The problem I have with the Limas right now is that they've been working fine for me before the patch. Now I seem to regularly run into the situation of them going off somewhere else that's not even close to the previously lased target. For example, I had a moving convoy of 2x BMP's and 2x T90's right in front at about 5km. I was within' launch parameters, had clear LOS and was in a stable hover. Multiple Limas that were fired at the convoy went straight into the ground after not even half the distance to these targets. They didn't even come off the rails like regularly, instead of going up and doing a turn they immediately went straight down to the ground. Unfortunately I forgot to save the track file, but this happened multiple times in different missions now. Also George more often seems to refuse lasing when being within' parameters and clear LOS on the target. I did not try the Kilos yet, but engagements with the Lima have def gotten much worse since the last update at least on my end. Maybe someone else can confirm such strange behavior after the update?

Anyone else having trouble getting George to lase the Lima correctly? They hit anything but the actual target after the last update.

Nope, there's def been a change to the ranges of some axis inputs of the AH64d just a few updates ago. I completely had to reset my rudder settings and they are very different now compared to what they used to be before that update. Maybe that does not apply to people who config their controls through any kind of 3rd party input device software, but it's def true for people who do these settings inside of DCS exclusively.

I find the engagements with "George A.I." to be the one and very most frustrating thing about the Apache. Best way to describe it as a "Gamble"! I'm exclusively soloing on- and offline with the Apache and I find myself way too often in a 50/50 chance situation, when George again doesn't recognize his target and just refuses to engage. Missiles and rockets work best, but when it comes to George making a use of the "Cannon" I find myself dying like almost all the time. Flying in a straight line towards "AA infantry" with George being right on target and within optimal range, is almost a 100% chance of us getting K.I.A, because George refuses to pull the trigger. I think I've read somewhere that the cannon is used for suppression, so how come George doesn't seem to know how to suppress with the "Cannon" and instead is waiting for the perfect shot? Besides that when giving manual fire command he should actually pull the trigger, no matter what. That's imho what "manual" is all about when being the pilot. The Apache is very much useless as a solo player that way, because you simply can't effectively engage with it especially in motion. Also the way how George seems to lose LOS is just completely unrealistic imo. As soon as you spot a traget IRL you know where it's at and you are able to anticipate. If George is aiming at a target all it needs is a single tree to break LOS sometimes. Switching to CP/G doesn't make things easier, because you die the very moment you hop back to the pilot's seat due to crashing. And if not you'll die at some point with George A.I. as pilot, when again he magically manages to get in a vortex. I was thinking about making my own thread about my own experiences with George A.I., in hope that some official would give a short feedback about planned changes of George A.I. But I think I'm gonna' leave it with this post for now. Seems like it's recognized that many of us are very frustrated with George. From a sp perspective I really hope that George A.I. will be more capable at some point. I just hope it doesn't take so long as changes to George are essential for soloing the Apache.

No it's not. DCS Beta is basically the "up 2 date" version of DCS and the majority of the community exclusively use the beta branch to play, because there are basically no downsides to use that branch. I can't remember ever using the stable of DCS and never had any game breaking bugs or other problems in the Beta. So my advice would be to just hop over to the Beta and enjoy all the new content early.

I use the "Gun/MRM else SRM" option on the WH Boat Switch. Works as intented.

Yes, something's different with the controls. You guys should def check out the "in" and "out" of your axis input! For example I've had to completely change my rudder settings after the last update, but curiously only for the left pedal, due to it's range somehow completely changing after the update. I'm using Logitech G29 racing wheel pedals for rudder input and set them up in a way that makes the clutch (left) and acceleration (right) pedals act like one axis. To do this I need to invert one axis and tune the saturation in a way that makes both axis meet in in the middle at 0 input. So before the update both settings looked like this: Axis A - left pedal: X100, Y50, curve -25, set as slider Axis B - right pedal: X100, Y50, curve -25, set as slider + inverted After the update the input of the left pedal was "overshooting" so now i've had to change the Y setting to: "Axis A - left pedal X50, Y50" to make both axis meet right in the middle again. Had to do this for all modules and I absolutely don't understand why, because everything was working fine before the update... So maybe that bit of information does help some of you to figure out your control settings.

Everything fine and working on my end so far. Playing almost exclusively mp sessions where I was rearming and using HF again without any issue. Got to admit tho that I'm always selecting a different lasing channel on my first startup, just to prevent from beeing interrupted by other players lasing targets. Usually I'm using preset channels Oscar and Papa. So maybe this is something related to the standard preset or you've just been interfered by other players lasing targets.

It seems like George has problems firing at targets that have slight cover especially when it comes to buildings. I often find myself in situations where George simply refuses to shoot a missile at targets that are not standing in an open field. And it doesn't really matter if sp or mp. So when looking at the OP's picture you can see the target is behind or at least close to a building. So that matches exactly what I'm experiencing myself quite often.

I'm using TrackIR to align my boresight and I tried it in two different ways. I was aligning by just looking down right at the center of the receiver and also by exactly lining up with the yellow dot in the center of the two yellow circles, by moving the head down. After trying for days now the first solution where I completely ignore the yellow symbology and just align with the center of the receiver dev gives me the best accuracy. But in the end both alignment variants won't result in perfect hits even when in a calm and steady hover. There's no chance for me to really anticipate where the shots will go either way. That's why I think that there's probably something wrong that mabye has to do with the sync problems that seem to be present currently.