key_stroked

Engine sounds are still missing from some vehicles, like the Leopard MBT.

Is this a function that is INOP in the real AH-64D? Or are we getting something later in early access that uses this part of the weapon actions switch on the cyclic?

Whatever the default is in the editor.

Understood.

If these fixes didn't make it into today's patch, then I'm not sure how useful my tracks will be.

Was any of this fixed in today's patch? I'm still experiencing really bad acceleration and speed issues with tanks on flat ground.

Haven't made a track yet because I want to make sure I'm not the only one experiencing this. I tested the gun against ground targets this morning after patching, and the rounds are shooting off way above the reticle while in range, closer to the heading tape on the top.

The OP's screenshot shows the gun is in FXD mode, which means it's not following the TADS crosshair but rather the fixed crosshair that appears in the HUD. Wouldn't that be more crucial than being outside of 2900 meters?

DCS taxpayers take care of that. I'm just the bus driver

Pfft I start both at once. Equal wear and tear! And 1/2 the time spent starting up.

If that's the correct behavior, why was the thread marked "unable to reproduce" ? Any cold & dark start Apache will have it off by default and it will never come on unless the user manually turns it on. It wasn't this way before the last patch.

I don't understand how this helps me as a pilot. Can you explain what we're supposed to do with this info?

I did another test and waited another full 30 seconds after pushing RDR ALT on the FLT page. This time, it came on. I think what confused me is that prior to this patch, if I used a cold & dark aircraft, the radar altimeter was already on by default when the aircraft got power. But now, there's an extra step of pressing RDR ALT and having to wait a good 25-30 seconds for the FLT page and the IHADSS to show 0 (if on the ground). Nothing was said about the radar altimeter in the patch notes, so it caught me off guard when I didn't see it right away. I'm going to mark this as solved, but I'll leave the title unedited in case someone else runs into the same issue I did and finds this thread. Thanks for testing all! @NineLine There is one issue remaining with the radar altimeter, which I just verified (it's really minor). A hot started aircraft can't turn off its radar altimeter. I tried using RDR ALT on the FLT page, but the altimeter stays on. This was also shown in one of the screenshots towards the top of the thread.

I can't save track files. My track file system is broken, even after a DCS_Updater.exe repair. Edit: I had disabled track file recording in the autoexec.cfg file. Did it a while back and forgot about it. My bad! I did the Caucasus cold and dark instant start scenario. After the engines were started, I pressed RAD ALT on the FLT page. The radar altimeter never came on, but the dot was solid. I'd provide a track file but DCS won't save track files for me.

Auto ranging is for using the gun with the IHADSS helmet sight, and is a less accurate way of using the gun. If you're using TADS with the gun, you should be lasing so it's more accurate.

I tried generating a track file today to show a bug in the Apache, and I got this screen: Ran a repair using DCS_Updater.exe in the command line, but it didn't fix anything. *edit* RESOLVED. A while back I had disabled track files in the autoexec.cfg file and had forgotten about it. Oops

It isn't working for cold and dark starts. If I choose a hot start, the RAD ALT is on, even though it's not selected "on" in the FLT page. Pressing the RDR ALT button also won't turn it off, either. It's stuck in the "on" state. If I choose a cold and dark start, the RDR ALT button can be manipulated (you can see the dot full/empty), but it doesn't actually turn on the radar altimeter.

(this screenshot was taken from an aircraft that was Cold/Dark started)

I'm specifically interested in the AH Mk 1 variant the British created out of the base D model. Those Rolls Royce-Turbomeca RTM322 engines supposedly added 30% more power according to the Apache book by Ed Macy.

LMC. Works fine in single player, but it's horribly bugged in multiplayer and will cause desync.

@dresoccer4 I suspect it has something to do with auto-consent. Your George AI wheel text is green instead of yellow, which means you held the "UP" key of whatever you mapped the George navigation controls to which switches from manual consent for firing to full auto. I've seen that George will get "stuck" in a zoomed position using TADS, and sometimes he can't see targets in that state. A workaround is to disengage using the George A.I. "DOWN" key to clear targeting and lasing, and start a fresh search using "UP". I would also avoid auto-consent for now (green text) and keep it on manual (yellow text) and tell him to fire for every target with the consent keybind.

Are you a SME? Just curious.

These aren't George A.I. issues, which is what the OP is talking about.

Laser arming is only done from the CPG seat. The pilot won't have that in their WPN UTIL page. If you're flying with George, he will do that automatically, and you can see that it's on in the screenshot because the "X" is over the crosshair, indicating active lasing.

I'm trying to figure out which side my TDS page is supposed to be on. For any warnings or critical messages, like low rotor RPM, it's always my left MPD that gets autoswitched to show the warning. I haven't found a way to get the right MPD to be the default "warning MPD". I like having my TSD on the left because the keypad is there, and entering waypoint and target information is a lot easier when I can see both the keypad screen and the MPD at the same time. But when that MPD gets overridden constantly in flight, it's a bit annoying. Do real Apache crews run into this issue? Or are they able to specify which MPD is the "warning MPD" so they can customize their MPD pages how they like?