GrEaSeLiTeNiN

I see what you mean after following the Apache's trim indicators more closely. Hope it is fixed by a hotfix as it does spoil the flight experience. Can't imagine why it was released in this state. Did they even test it?

Tried it with central position trimmer as well as fade in/out trimmer modes on both pedal and stick. As I understand it, the bug is actually in the representation of the indicator for the stick. The white indicators are the positions of the sim stick and rudder following a trim. The red indicators are the positions of your physical stick and pedal, which should always be in the centre after recentering the physical stick and pedal. But it is not happening in the case with the stick. The stick's red diamond follows exactly where the white diamond lands after a trim which defeats the purpose of showing where the two are in relation to each other. The other problem (bug?) I find is that a left pedal trim seems to have a compounding jerking effect unlike a right pedal trim. Also, this new FM makes you lose altitude quite easily with a full load esp if you do not have translational lift unlike before. (The Apache has the red and white indicator colours in reverse plus the green SCAS indicators.)

Based on this Reddit poll, seems the SP base isn't actually that far off in numbers from the MP base granted it's a small sample size 3 years ago.

You need to put in the keyboard binds for labels in the Gazelle controls. Just copy the standard label binds like those for say the F16. I wonder why they left it out. The Gazelle's keybinds are not the best. Lots of missing hotas friendly binding options when compared with other modules.

I agree. Seems circular or curved parts of DCS cockpits often look jagged. It's ok if the jagged part is only glanced at occasionally like something on the side. But not so for those frequently in your FOV, like canopy rails (eg AH-6J mod) and aiming sights.

It’s the trees. Try targets in treeless areas and the hit rate should improve. Don't know about MP but that’s been my experience in SP.

Open Beta latest as of today, Apache, laser hellfires, laser tracker mode, solo as CPG, unlimited ammo, Normandy 2: I set up a Reaper to lase two target groups. All goes well with the first target group - destroyed. But with the second target group, AFAC says it is lasing and my laser spot tracker picks up the target but there's no lasing as the hellfire cannot track it. Then my laser also stops working if I try to lase manually. In fact I have noticed lately that the Apache laser will sometimes stop working like it burned out or something. But a check on the Utility page shows the laser is on and codes are correct. (have to turn off laser spot tracker first) See attached track. I noticed the Reaper will often lase some other target not tasked in the advanced waypoint actions. There is also no option to restrict it to lase only designated targets (I think the ROE option is only for when it is assigned to attack targets with its own hellfires). Is this a known problem with AFAC? UPDATE: Figured it out. Needed to put FAC Engage Group right on top of the list (in Advanced Waypoint Actions) with target Priority "0" (1st Group) and "1" (2nd Group) if you want AFAC to hit your selected targets in that order first. Only then comes FAC-a where AFAC selects its own targets. DCS APACHE REAPER LASING PROBLEM.trk

Just a casual simmer, for what it's worth - Did more testing in (South Atlantic map, coastal where there is less ground clutter like trees). Unlimited Limas, active pause hover, stationary targets > 2.5km, within firing parameters, playing as CPG, no LMC or IAT. Pretty good hit rates like 80-90%. If it missed, it might hit a target nearby but it could also hit the intended target at the 2nd try (it did not keep missing or hitting the same wrong spot). At one time, the second target fired at in succession was hit even as it moved away after the first target was hit. So at first, I thought some coding logic was off but it seems quite fine to me at the moment, as in the Lima's radar appears to be 'searching' (smart) and doesn't get stuck in some logic. I have used IAT and LMC with the Limas in earlier tests and if I recall correctly, results were similar but hit rates were lower with moving targets as one might expect. Trees and buildings in built-up areas like Normandy 2 were what really reduced the hit rate for me.

When beyond 2.5km, if you move your TADS cursor manually even when the crosshairs are just pointed at the ground (no target, let alone IAT or LMC), it transitions from LOAL to LOBL after lasing for target data is completed. Not sure how it is IRL though.

Just out of curiosity I tried it several times but managed to hit my target only a couple of times. The Lima will fly and turn 90deg but has a slim chance of hitting the target though often near it. (2nd trigger detent to override yaw limit firing parameter.) Tried it with the K too but it just flies straight ahead.

I have experienced similar results - it occasionally misses or hits another target. I get better results at higher altitude and with less trees and buildings near the target area. If you follow the trajectory of the missile, you'll see it flies quite a low profile near the end, even passing below treetop level if there are trees along the way. I'm thinking ground clutter might play a part here. (I experienced more misses in Normandy 2 map - lots of trees and buildings.) Hit and miss results can be expected and the radar HF has quite a few limitations. Update: As expected - How the Lima Works (CasmoTV)

From the few attempts I’ve tried at OGE hovering, does seem to hold the hover now even with hands free. If it does oscillate for some pilot induced or SAS reason, I turn off ATT hold for a sec or two then re-engage it.

Got it, thanks!

So I tried the new Laser Tracker with JTAC and it's good. BUT could the JTAC pause like two secs before "shifting"? I'd like a couple of secs to enjoy watching the target destroyed before the TADS jumps to the next target. Right now it's so instant I barely get to see the target destroyed.

Ok I see your point. Thanks. Just for discussion - should it not (as a safety feature for example) prevent me from WASing up a K and firing it 'accidentally' (when CPG George is in TADS RF HF mode)?

As pilot, we can fire the K (after WAS-ing right for HF) at what CPG George has lased. So can't we likewise fire the L at what George has acquired in his TADS and when the AI command rose is showing that a RF HF is currently selected? It's really just pulling the trigger on behalf of George (as he sometimes doesn't). But what happens instead is that I can fire a HF (after WAS-ing right) but it will always select a K even if I have the Ls on the left pylons and the Ks on the right pylons - and of course the K misses because George is still in RF mode and not lasing. I was thinking since it defaults to selecting the left pylon it might work if I put the Ls on the left side but it will just pick a K on the right. Is this meant to be?

Yup, Wags mentioned LOBL as the default for moving targets and stationary targets under 2.5km. Have to wait a sec or two though for the small box to become big.

Flew as CPG with unlimited Limas in manual mode to test against multiple targets near or next to each other in Normandy 2, using active pause hover with LOAL and LOBL. Might be the many houses and trees obstructing? though TADS had a clear view. Having better success in less cluttered South Atlantic with LOBL. I would say the K is more certain of 100% hits. I've had the L hit another target just next to the one I lased and acquired target data for, on a few occasions. With buildings, I find it could hit way off quite often (due to ground clutter?). If the L is seeking a target with its radar based off target data from the TADS/laser (which I understand could be off by several meters?), would it not on occasion hit something else? I mean it is not as certain to hit as an active laser constantly guiding the K. Update: As expected - How the Lima Works (CasmoTV)

I thought Ctrl EEE would have included opening of the canopy like in the warbirds. Guess not.

Had a go with it just now - I find the hit rate of the radar HFs to be quite erratic whether LOBL or LOAL. For now, the Ks are far more reliable.

I tested with unlimited radar HFs at many targets and I find the hit rate quite erratic - can't quite figure it out. You can stop lasing (after Target Data is acquired) before firing but it seems if you move the crosshairs away you might miss the target. Then again, sometimes you'll hit the target. (Did not use IAT.) With buildings it's even worse - it just hits the next building or somewhere else. If you have multiple, say vehicle targets next to each other, it's a hit and miss situation - sometimes it hits a nearby target you did not lase and sometimes it hits the one you lased. Also, within 2500m, sometimes it says LOBL but gives me the small square - might be an unlimited ammo bug? It's an early version so it's probably WIP.

As far as I know, he can't. He only engages targets you select on the target list. Maybe later on they might give him some AI initiative.

Best way to survive the sudden roll is to complete it 360 [emoji16] https://media.tenor.com/zpSU_noxqVYAAAAd/rolling-olympics.gif

I flew it the other day without any rockets or missiles loaded and got myself into uncontrollable rolls. I suppose it is easier to enter a roll when the aircraft is light.