Rongor

At initial rearming and refueling a slick Apache after spawning, the numbers in the rearming window are wrong. Since we don't have access to these anymore since last patch (and I totally understand and support the idea behind this), we can't correct these and flares/chaffs are stuck at 64/0. After rearming is complete, 63/0 are loaded. Only a second rearming cures this. Numbers then are correct in the reaming window and are correctly taken on board.

Problem: regardless which module I am in, opening up the controls setting now calls up the alphabetically first module in the list, not the one you are currently using.

It will certainly launch at you within 22 seconds and with the current accuracy of player and/or George launched Hellfires, there is a decent chance you won't kill the SAM system before its launch hits you. Killing the SAM at max Hellfire range before it kills you is nowhere safe enough to be counted on. Counting on your Hellfire killing the SAM before the SAM counter missile hits you is a huge gamble you will often lose. Actually I would totally recommend to launch from a distance behind the hill tip. It doesn't affect the time you need to break LOS, you get a ballistic advantage and you gain a lot more space in front of you for your evasion (or hectic contingency maneuvers) in case other threats surprise you. Staying close behind a tree, hill or other obstacle reduces your space to maneuver and increases your chance to hit something. Keep some space, retain flexibility.

maybe elaborate a bit what you mean with "never work"? Don't the yellow rings appear in the BRU? Is your key press not recognized the moment you have it aligned?

If you press VID again, it will show PLT HMD selected on R5, although we pressed R6, only a second press of no video (R6) will then get rid of the TADS recticle. The current way to workaround this bug in one single flow is from the TADS repeater view you select T6 (TADS) followed by R5 (PLT HMD) then R6 (no video).

So far we had to flip all these squelch switches up at cold start to silence any radio static. Now since the recent patch, if you don't do this, the static is only audible when the ground crew is talking to you or when TSD>MAP>UTIL>INST>ADF is enabled. You will then still have to flip up all the switches to silence the static completely. Basically if you stand by your checklist and still enable all the squelch switches, you won't ever notice.

both rotating dials on the PVTz-800 and the one on the PVI-800

It might rather be the sun looking through your rotor disc and occasionally casting a shadow by the blades into your cockpit The shape doesn't make any sense though

Dials and switches don't cycle anymore. You have to go back and/or forth.

works on my end

1. same for LWS 2. the ABRIS max brightness is way lower than before the patch 3. IT-23 is green

I am playing this on a dedicated 24/7 MP server, so basically the host could have unintentionally set this option for some slots and not for others, I will check this. So the inability of George not seeing a T-90 out in the open in 2 km is a different issue....

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.