GrEaSeLiTeNiN

What I've found is As CPG, create WP|TG with TSD in NAV|ATK using (a) HDU sight + WPN auto range + LHG Store (b) TADS sight + lase once + LHG Store As Pilot, create WP|TG only with TSD in NAV|ATK + STO + NOW

Yes you can enter it using the keyboard unit (KU). But A/FAC only gives 3 by 3 MGRS numbers. So you'll need to add a zero at the end to make it 4 by 4, which is what the KU accepts. RedKite has a good tutorial here.

But isn't LMC a button on the LHG and not axis assignable?

Might be in the sim LMC is modelled too sensitively. Let’s see if auto track is good.

I see LMC used quite often in real TADS footage on YouTube.

Did you try special options. It removes the rim but can’t recall if it removes the reflection too.

Yep working. With "AT" status, SKR followed a moving tank lased by AFAC in my test mission though the crosshairs will not necessarily be on the target

Got it to work (no Aborts) by putting the AFAC behind me.

Yes! So I added the missing zeros (underlined) to the six numbers given by the FAC = CN14005480 and now it's accurate (see left pic). I think earlier on I keyed in the FAC's six numbers straight in but did not check the last two digits at the end which were probably the default last two digits of my own ship coords. So that threw off the location of the crosshairs. I tried "5" instead or zero just to compare. The crosshairs ended up a several meters closer to the road (see right pic). I guess it's not going to make much difference when locating the targets since the resolution is 10m and so it would still be within the vicinity of the target. But does anyone know why the AFAC sometimes calls out "Abort! No permission" after giving me a "Cleared hot"?

Well, I keyed in the six number FAC.coords and used it as ACQ, slaved. They were no where near the lased targets, at least not in any meaningful or useful way. There should be 8 numbers in MGRS, perhaps I forgot to add the zeros.

Some questions here: a) Single player CP/G. FAC was lasing some MLRS targets. For each target, hellfires successfully track FAC's laser (status "AT"). ACQ was set to helllfire SKR. But screenshot shows dashed cross (SKR/ACQ) always points at road in front of targets and never at the target currently lased. Missiles still impact all lased targets each time. Is it right to conclude that the SKR/ACQ just points in the general direction it's looking and not necessarily at the currently lased target? b) Occasionally, AFAC calls "Cleared hot", I fire and get an "Abort! Abort! You have no permission" What went wrong? c) Apart from using a mod, is there anyway for the A/FAC to give more precise coords than a six number MGRS? Thanks!

I don't suppose there is a way to turn off the green cross SCAS indicators? Kind of distracting. But with trim reset now, I guess I could fly without the controls indicator altogether.

Problem with long press down ("to search again if a target was found" according to manual) for me is that it sometimes activates short press down. To take out say 4 targets at a specific location (reasonable scenario) with hellfires, one would have to bring up that list 3x more. And you might get a different list.

Wags' video tutorial discussed this. He showed a fully loaded Apache having trouble taking off at a MSL>6000 in 41degC. There is a weather cloud icon on the top left in the Mission Editor screen. You can try the Syria map near the coast (low MSL) and then at the centre (high MSL), in summer. You'll find it difficult to hover at high MSL. Then change the month to Dec and temp to 0 deg. And hovering (at that same location with the high MSL) becomes easier. The service ceiling of the Apache according to wiki is 21,000 ft at 15degC. Got to try but I think that is probably with a light load. Wiki - "On a standard day, when temperatures are 59 °F (15 °C), the AH-64 has a vertical rate of climb of 1,775 feet per minute (541 m/min), and a service ceiling of 21,000 feet (6,400 m). However, on a hot day, when temperatures are 70 °F (21 °C), its vertical rate of climb is reduced to 1,595 fpm (486 m/min), and service ceiling is reduced to 19,400 feet (5,900 m) due to less dense air."

Could they not leave the list there and let us cancel it on our own? That’s the point of a list isn’t it? If it’s a group of tanks in that list, I’m sure we’d want to take out a few.

Me Googles "servos"...

Yeah, this directory for skins.

I see. So ACQ never guides the SAL hellfire in any manner but serves merely as a reference point for the pilot’s aim. The missile only ever flies to wherever the laser is pointed (within parameters).

The green symbols seem to lag or are off set a little. I am not sure what that means, or how it might be useful to the player. The previous red and white symbols where more intuitive.

So trim reset is available now. What do the green "+" symbol and green lines (rudder/ collective) mean?

Great info thanks. I was just doing some testing and trying to make sense of all this, then chanced upon this post and the OP. Some mental notes for myself (correct me if I'm wrong): 1. LOBL happens as long as you lase first and it will have its own traj and disregard HI/LO/DIR. 2. LOBL doesn't seem to need an ACQ. I mean I can select ACQ as FXD (looking at the sky) or as PHS (AI is just looking at the empty ground). As long as I can lase and track the target before launch (within parameters), the missile will hit the target. 3. You will only see the HI/LO/DIR traj working if you fire without lasing first (LOAL). Yes, DIR can have a 'flatter' traj than LO but I guess it depends on the helo's altitude. 4. LOAL requires a stored target point (ACQ) as a fly-to point and the missile will fly over that point if lasing is too late. But I noticed I can hit a target way off to the left or right of the stored point so long as I lase the target early enough for the missile to change course. Correction: ACQ never guides the SAL hellfire in any manner but serves merely as a reference point for the pilot’s aim. The missile only ever flies to wherever the laser is pointed (within parameters).

Future improvements to the flight modelling (if any) to make the Apache more stable, plus auto hover, might make this trim thing less of an issue. One can get use to whatever trim suits you. It's in those weird situations when you move the controls too much, things get out of hand and whatever trim option you have 'fails' you. I am all for the trim reset option. I never understood how the game options I select on my PC would degrade another player's realism experience thousands of miles away. Unless it gives me an unfair advantage in MP. The module is just too well made and complex to have it dumbed-down by a trim reset option. Furthermore, there are already a number of 'unrealistic' in-game options that no one is up in arms about.

I was thinking of sacrificing “disengage hold for all” for ‘trim reset’ in my 4 way hat since Alt hold and Att hold can each be disengaged by reselecting them, if I am not wrong.

Am I right to say that for the current laser Hellfires, the 'sight' can only be the TADS since lasing is involved when firing is involved? I mean HMD as 'sight' is only meaningful for guns and rockets right?