DJ_9mm

I find the radar antenna elevation to be very difficult to adjust precisely. Even the quickest press of a button moves the antenna too much. Even with a 4 bar scan, I find it much too hard to get the elevation just right in order to illuminate a datalink target that I know is there. I have worked around this problem by assigning the antenna elevation axis to the flaps slider on the base of my Virpil throttle, which lets me smoothly adjust the elevation. This is a poor workaround though, because that slider is not on the throttle itself, so I have to take my hand off it to use it. It seems to me that the speed that the antenna elevation moves while the button is pressed should be cut down to about 1/4 of what it is now.

I love flying the Apache on Blue Flag when my buddy can join me. Unfortunately, the incredibly maddening bug where George says "engaging" but never fires keeps me from using the Apache in MP alone.

Thanks, that was it.

Thanks for the suggestions, but boresighting didn't help. See track. https://drive.google.com/file/d/11QgYeZcN77wojLhPV0elm1FSRL6KT513/view?usp=sharing

Here's a seemingly related clue. After a cold start, slaving George to the PHS is bugged. He slaves to a spot up and to the right of where the PHS LOS reticle is aimed. George slaves the TADS with the exact same amount of error as the gun has. In fact, if I fire the gun while aiming with the pilot sight, then slave george to the same spot, he slaves to the exact same place where the gun erroneously fired. With a hot start, this problem doesn't happen. Clearly, these bugs are related. Here's the problem happening on a cold start: https://drive.google.com/file/d/1174585GTnVHkHyQcrO9bmbgJCj1fDy7H/view?usp=sharing Here's the problem NOT happening on a hot start: https://drive.google.com/file/d/11FUQd2NaBXpb4g4KTuEGAmz81WnPopMg/view?usp=sharing

Here are two tracks from a generated fast mission. First, I use the mission as-is and start airborne. I go into a stable hover, engage attitude hold, and take some shots at the ground. The aim is fairly close with manual range set to the default 1500, then I turn on auto ranging and the aim gets much better. Everything works as expected. https://drive.google.com/file/d/10oFmdQXqs_vEOJJEQb8IZ0EBTTOm9S2K/view?usp=sharing Then I edited the mission to start cold, from the ramp at an air base. I go through the cold start. I wait for the INU to do it's thing, then I go into a stable hover and shoot at the ground. As you can see in the track, the aim is way off, even with auto ranging. I mean, it's not even close, and it's a night and day difference from the mission where I did a hot start. In case you think I forgot to turn on the radar altimeter, you can see on the HUD that it is working. Also, the radar altimeter is now on by default in cold starts. You don't have to turn it on manually. https://drive.google.com/file/d/10qJQsJL2SJKrWzSak8HKh3XPqczDuwAM/view?usp=sharing Here's the mission file, in case it matters. https://drive.google.com/file/d/1161nKSRN3YE8V65H23_FV-G9Nl1_K7_Z/view?usp=sharing

Thanks for your reply, Bignewy. I'm a bit confused about your statement about me giving George permission to fire. I put him in the green state to allow him to engage. I never use the "consent to fire" button. I don't even have it mapped. Were you thinking I was pressing consent to fire? If George needs time to think and can't respond to a command, it would be very helpful for him to say something about it, like "standby". It sounds like you only watched my first flight in the track. That's not the one with the more serious problem where George won't fire the hellfire. Please watch the second flight where I'm attacking the air base on the island. That's where you will see George saying "engaging" but never firing. This is the more serious of the two problems because there is no workaround for it.

There are actually two separate issues that prevent George from using the hellfire. One is that after the first time, he no longer slaves the TADS to your helmet sight. He will do it the first time I ask, but after he successfully fires a hellfire, he won't slave again. That means you can't tell him to attack any other targets. I think I've found a workaround for this. If you short press W (up) he will say "roger ceasefire", and then he will slave again. The second issue is that he will say "engaging" but will never fire. Like others have said, the constraints box does not appear. Again, this happens some time after the first few hellfires have been used. This problem seems to be unique to, or at least much worse, in multiplayer. Here is a track from me playing on BuddySpike Blue Flag, Persian Gulf. The first flight, I'm attacking a FARP from a position in the mountains. George slaves the TADS at first, and shoots a hellfire. Then he refuses to slave again. He does say "slaving, deslaving", but the TADS doesn't move, or only moves a tiny bit and not to where I was looking. Then I tried the ceasefire workaround and he starts slaving again. Then I'm shot down by a jet. The second flight in the track, I take off at Sharjah and fly over water to Abu Musa. George attacks a few targets with hellfires, then I start having the problem where he says "engaging" but doesn't. I'm in range and have a clear shot. Even if I didn't, it's a bug that he says "engaging" when he clearly is not engaging. I never got him to fire again, and I quit to desktop. This problem is extremely frustrating. The Apache is unusable in multiplayer. https://drive.google.com/file/d/10cXVf8x2ur2H_Tyu0KSkQAD_oblV9L7a/view?usp=sharing

I have the same problem. So far, I have only seen in it in cold start instant action missions. Cold start fast missions do not seem to have it. It happens regardless of whether I use manual start or auto start. A boost pump fail message is shown, which seems to be a clue. I spent hours trying to figure out a way around it and failed.