Floyd1212

I had someone hop in my front seat after I had been flying for a bit last night without a crash. This was in a hot-start aircraft. Are you seeing this with hot-start, cold-start, or both?

We were seeing this for a while, but not currently.

We didn't experience this when running rockets in a multi-crew setting the other day. Are you saying when you both WAS'ed rockets you didn't get the COOP indicator in the back seat?

This happens on other maps, as well. It has been discussed before, but possibly related to the date the mission is set to take place? The solution is to enable “Unrestricted SatNav” in the mission, or for your local options.

We still see lots of desync issues in multi-crew. FCR returns not displaying in both crew-stations CPG not seeing waypoints that were loaded with the Route Tool prior to a dynamic spawn PLT seeing the TADS drift on the video feed when the CPG uses IAT (intermittently) DL not being configured (and not working) for CPG when everything looks fine for the PLT

One of the changes made in the last patch is that George does not automatically start up his crewstation in a cold-start aircraft like he used to. After starting up the battery and APU from the back and power is available, pull up the George Interface and give him the command to startup the front seat by pressing your "consent to fire" button. This may not be your issue, but just throwing that out there as a possibility.

As you approach the targets and have George lase the target and then have him WAS missiles, he loads the target data to the missile and then stops lasing. This is roughly at 8600m. It's easy to miss because he was already lasing prior to you WASing missiles, so it didn't take the normal delay for the data to be loaded, but you do see it flash in white at the bottom-left of the High Action Display. And then, as mentioned elsewhere in other threads, he will not lase again until you de-WAS missiles, or fire the missile, or switch him to SAL, etc. You see the distance to the target continue to count down for a few seconds, but then it stops at 8400m, and George never never indicates he is in range (below 8km) and ready to fire. I took over after you got another few km closer to the target and when I gave George consent to fire, he said "out of range" and wouldn't rifle. I'm not sure why the distance to the target stops counting down at 8400m. Is this a bug, or is there some reason why it stops estimating the distance? Regardless, it confuses George into to thinking you are still out of range. So, the fix is either have George continue to lase even after the target data is loaded, or at least have him periodically squirt the laser to update the range so at least he is aware of when he is in range and can fire. Or if you really don't want George to lase ever again, give him some magic ability to know the distance to the target so he realizes he has crossed the magic 8km bubble and is in range.

You're not aligning the rings to be concentric inside the BRU tube. You want them centered in the tube, and your crosshairs centered on the rings.

This seems unrelated to the OP's problem with Acquisition Sources, but more to do with how you are boresighting the IHADSS. You should do some research on that, and maybe post a video of your boresighting process in a new thread if you still need help. (In a Hot Start, the boresight is already performed properly for you.)

It's tricky with Limas if you are flying around and hunting a SAM or something. You want periodic spurts for ranging data, but you may not want to lock in the Target Data until right before you are going to take the shot. Not sure how you manage something like that through George.

I was launching Limas at radar returns from the back seat last night. I don't think anything has changed with that regard.

Have you removed the springs from your pedals yet?

In addition to arming the aircraft, did you power up the laser from the WPN > UTIL page?

The updated manual is in the install folder of the AH-64D module. For example: G:\Eagle Dynamics\DCS World\Mods\aircraft\AH-64D\Doc\

I was also having issues with George not firing the gun after saying "engaging". I'll do some more testing next time I go up. In general, I like the new tricks George learned, but it will take a bit to master the menus and sub-modes, etc.

I haven't had a chance to fly yet after the patch. You see "COOP" in the high-action display indicating you have both WAS'ed rockets at the same time?

Maybe you are running into this known issue mentioned in the patch notes? Sounds like you aren't actually in COOP mode?

Yes, this has been frustrating for a while now, but improvements are on the way. We will see if George is better with the initial track after the next patch, but it also sounds like additional features are coming to get George to reposition his track on command. From the announcement about the upcoming "George" patch:

It looks like you have the Pedals Trimmer Mode set to Instant Trim on the Special Options page. In this mode, when you set the trim position the input in-game gets briefly doubled, which can cause the over-correction until you take your foot off the pedals again. You might try the Central Position Trim mode instead, which will not double the inputs after trimming. But, like was stated before, you will see the greatest difference in control and stability by removing your springs, optionally adding a damper, and using the Pedals Without Springs mode.

I'm excited to see the new George AI features getting ready to roll out. Any update on the issue with George detecting targets that he shouldn't be able to detect? Like behind hills, trees, buildings, etc.

Removing the spring and selecting the appropriate "Pedals without springs" mode in Special Options is the most important step. Adding the damper on top of that improves precision and fluidity to your inputs. Ground taxiing is very doable with minimal input of the pedals, and without a centering spring. And make use of the tail wheel lock when you need to taxi in a straight line, then only unlock the tail when you need to actually make a turn.

I wouldn’t let that stop you from enjoying everything else the Apache has to offer. It is annoying, but still very flyable. You learn to adapt and compensate. I would also recommend removing the springs from your pedals. Flying helos without needing to trim the pedals is a game changer.

Yes, the tail rotor is a mess. They are working on a now rotor model that will address the situation. No clue on when we will see it.

Keep in mind there is different laser behavior needed for Limas vs. Kilos. The Kilo needs a constant laser for the missile to track the target and be guided in. The Lima needs a few seconds of lasing the target to get the positional data loaded into the missile, then you can stop lasing — and George does. Sometimes this can be a pain if you want to switch to a different target but the missile already has the data for the first target. You have to switch to Kilos and then back to Limas to get George to lase and capture new data. If you keep flying around without shooting the Lima, I think George will clear the missile and re-lase the target to get fresh data. This sounds like the behavior you are describing. EDIT: The complaints about George not lasing in other threads were primarily when engaging with the gun, but that issue seems to be much improved as of a few patches ago.

Sounds like a control bind issue. Maybe your trigger button is setup as a modifier in conjunction with some other axis? Or double-bound with Force Trim Release? Does this happen when you give George permission to fire, or only when you fire the weapon yourself? Like MAXsenna said, capture the event in a short track file and post it here.