Rongor

Now I had George (CPG) see an array of AD stuff in 20 km distance, yet the T-90 in open field which was ahead of us in 2 km was invisible to him. There are targets I can perfectly see as a human player which George just refuses to notice. This is a problem, because I cant attack obvious targets close to me and may be unaware of other close targets I didn't spot myself but should have been picked up by George. Especially with a hostile helo close by, it's a complete lottery. Of course I have tracks, yet as we all know you wouldn't like to review 40 minutes long trackfiles so there is no that much I can provide to assist in solving these issues.

I am currently frustrated by "my George" not being able to pick up an enemy helo not even within guns range, not even when I make him slave while placing my LOS reticle precisely over that incoming aircraft. He still only lists ground units. The weird thing is that my wingman (we fly on a MP server) flying right next to me has "his George" noticing that very same enemy helo from afar and also has no issue "locking" and guiding Hellfires towards it. Is there anything I might do wrong? Is there some specific bug causing this or a workaround to deal with this?

They generally do work for me yet often (after repairs and restarts) I have to unrest both levers out of the OFF detent once and put them back into OFF to make them work again.

I can confirm this is the complete behavior with it. Reason for my report was the difference to the preceding builds, when we could arm the chaff on the ground, regardless of master arm state, when now we can only do this with master arm on in gnd override. If this is the correct behavior and the recent patch in fact 'fixed' it, then all is good.

This wasn't the case with earlier versions. For some reason we can't un-safe the chaff anymore with T1 on the WPN-ASE format page. Only works when master arm is on. If you switch master arm off, chaff automatically returns to safe as well. Seems a bit counterintuitive. I may want to defend against (often longer range) radar missiles even in situations I am not engaging targets (master arm off). Is this intended to not work anymore?

This appears suddenly and in these moments the green SCAS line in the indicator display instantly jumps to the left limit. It's triggered by wind coming from the left. It's easily reproducable so at this point I didn't attach a trackfile (yet). You need wind in the mission. Take off into a stable hover, nose into the wind (10 kts will do). Then slowly give a little right pedal to gradually turn the nose right. The moment you have the wind at 270° relative to your nose, yaw control is running wild for a moment, violent yaw to the right sets in, SCAS yaw will be at its left limit. Apparently it does not happen while yawing left around a complete circle.

What is to do in your opinion?

Buying a map allows you to enter servers running this map.

the blue border of the thumbs up image shows us he already did so.

Why do you want to gain write access to the rules channel? This is not the channel for discussions...

Unfortunately DCS has no capability to create short track files. Things happen suddenly during flights. I understand that the current replay system makes reviewing tracks a chore but to avoid enduring this I am afraid ED needs to improve the track system.

can anybody comment if he ever experienced this? I just had this and there was no way to exit ACM. NWS didn't help, selecting different weapons didn't help, DDI inputs where ignored. I think it started while switching to AIM-9 while already in ACM mode. At first the selection of AIM-9 quit any radar/ACM symbology on the HUD. When I then tried to cure it by switching around ACM and also NWS back to RWS/TWS, I noticed I am stuck in ACM on the DDI and no ACM/radar symbology on the HUD... I have a track file but its very long and while I tried to review it, but the necessary fast forwarding obviously desynched the track with what really happened (air2air refueled flying 200 ft above the tanker, then later fell into the sea, which never happened...)

Doesn't mean people shouldn't maintain to express their interest to give ED reasons to reconsider some time into the future.

This is the crappiest radar I saw in any of my DCS module so far. I can't even detect a MiG21 which is in visual range ahead of my nose. It's basically blind. Can we get rid of it to enjoy a lighter aircraft This way we then maybe can at least make flying this brick a bit more enjoyable...

Whenever I receive any damage, I always lose engine power and this means game over.

Razbam found an efficient way to do it in their Mirage: giving the increase direction much higher speed than the decrease direction...

sounds great, thank you!

I think the stability during landing approaches has decreased. You have to adjust throttle constantly in APP mode and still the AoA-guide brackets will run up and down erratically, no mater how gentle you apply adjustments. Also the necessary throttle to keep her on the glide slope at approach speed seems to have increased. I am always short of pushing throttle into afterburner to maintain angle on speed.

This is how it looked until recently. You could somewhat conveniently simply open the F10 map, switch to MGRS coord display and then locate these sites (Hawk sites for example) Now the MGRS coords have been sacrificed for some random unit ID numbers. So you can't really locate them anymore.

It was so convenient to see the MSGR "XY12" coordinates in the kneeboard for friendly radar sites outside of airfields. Now this has changed and there are only some 4 digit numbers added. What is this about? Is that an intentional change or a bug? How am I supposed to quickly see where this station is located?

please watch: 20220726_010506.mp4

It doesn't matter if SP or MP. If you don't use easy comms (which you stated you don't) you need to set the correct frequency

actually it was explained to you by an automatic kneeboard pop up after the recent 2 patches...

You were on the wrong frequency then I guess