Floyd1212

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.

Two things to consider here. 1) Selecting MSL on the WPN page is not the same as Was'ing missiles with the Weapon Action Switch. You may have done so during your engagement, but didn't explicitly mention it in your description above. 2) More importantly, it doesn't appear that you have any RF missiles left to shoot. It looks like you have fired 4 missiles, and the 4 remaining on the rail are SAL laser-guided missiles.

This has always been the case. I just checked it again now, and when I swapped to the front seat the "Boresight IHADSS" message is not there. That's not to say that there isn't a problem with alignment when using the IHADSS in the left eye. I could see George boresighting for the right eye, then when you swap seats and use your left eye, things are off. I use TrackIR in 2D myself. If you use the right eye, does everything work properly?

Yes, if you start the aircraft from the back seat, and let George get through his startup routine up front, you don’t need to boresight again when switching between seats.

In my experience, trees in DCS are mostly just cosmetic. FCR can see through them George can see through them You can IAT a target, and then continue to track a moving vehicle through them You can lase through them SAMs can track you through them And in some cases, missiles can pass through them and kill you

I don't think anyone has been complaining about that type of issue. Maybe some sort of hardware issue? Where are you taking off from in those screenshots?

Select HMD as your Sight.

Next time you go to fly one of those missions, grab a screenshot of the PERF page before you lift, and then post it here.

I'm not familiar with the campaign, but what is your altitude and temperature at the airfield?

Not yet. You can see it is still on the ToDo list here: https://forum.dcs.world/topic/318054-dcs-ah-64d-roadmap/

I know there was something mentioned in the recent patch notes about "optimized build of ground unit routes" but I am still seeing a lot of issues with pathing for on-road routes. For example, along this one section of highway I am seeing three segments that it won't route vehicles through: At 32 U NB 48231 33379 At 32 U NB 50013 33743 At 32 U NB 61160 29189

Yes, that is a temporary workaround while working in the ME, but the issues needs to be resolved by Ugra. If a better solution is going to take a while, I would suggest removing them altogether until they are ready to be implemented properly.

I just checked for myself and also see the issue. Rocker down works fine. Rocker up slowly and it seems to be reliable, but click it too fast, and it jumps to Preset 1.