Raptor9

Look at it more closely. He has CM selected as the point type when entering AE as the Ident, not TG. He started by entering TG, but it switched to CM. This is an error in the video. Enemy Armor is a Control Measure (CM), not a Target (TG) point. You can use it for targeting purposes, but Enemy Armor is a CM. A CM is a Control Measure. A CP/Checkpoint is one type of CM. Checkpoint is just the default CM point used if you cursor drop a CM point before entering an Ident code. Control Measures may consist of Friendly CMs, Enemy CMs, or General CMs. This is all laid out in the DCS AH-64D manual, starting at page 188, and specifically at the bottom of page 190 and the top of 191. As I said, the kneeboards in these training missions are wrong.

Your point type was set to TG when you entered the second point, not CM. This is why it did not work, as I mentioned previously. As Floyd1212 pointed out, the kneeboard in the mission is in error, it needs to be a CM if you intend to use the Enemy Armor icon using the AE Ident code. If you are unsure what codes are what category, you can access the ABR page (T4) from the TSD>POINT page prior to adding a point, and review what Ident codes you wish to use and what point type they are under.

The chaff and flare quantities can only be 30 for chaff and 60 for flares. No other combination can be used, despite what the rearm/refuel menu sliders do. There is only one 30-cartridge dispenser for chaff. The other two are only for flares.

You tried to enter an enemy Control Measure IDENT code as a Target/Threat type of point, which doesn't work. If you want an enemy armor icon (AE), you need to select CM as the type first. Enemy Control Measures are not the same as Target/Threat points. Up until recently, you didn't need to bother ensuring the correct point type was chosen for the IDENT code you were using, because the TSD would automatically change the point type to match the IDENT code entered, which isn't accurate to the real-life avionics (further, there are a couple codes that are duplicated that require the delineation, like BP and SP are used more than once). Now that the DCS AH-64D has been corrected to how it should behave, you need to ensure you select the correct point type.

The LST isn't implemented yet in Early Access, so the closest you are going to get is change the missile channel to match the laser code being used by the JTAC, and allow your missile seeker to acquire the designation while using SKR as your ACQ aa others have mentioned above. You can do this all from the backseat. Now, you can put your HMD LOS directly over the ACQ crosshairs after the missile has found the laser designation, and then cue George to scan in that area, but obviously that won't guarantee he will find the same target your missile is tracking. There is no way to specifically do what you are asking @Fakum, even after the LST is implemented, because it can't be used from the backseat; the LST is a part of the TADS, and only the CPG can directly control the TADS.

The real AH-64D has no such trim hat. This wouldn't be a feature or cheat to compensate for how DCS simulates force trim, like the trim reset, or being able to display the controls indicator overlay in the pilot's vision, this would be adding a control mechanism that exists in some real-world helicopters like the Mi-24, but it does not in the real-world AH-64D. This would be like increasing the performance of the DCS AH-64D to help those players that struggle with power management with a heavy weapons load. Would it make it easier? Probably. But it would also be unrealistic and inaccurate. I'm not trying to sound like an elitist, because I'm not, but it just takes practice, not an expensive joystick setup. I use a Saitek X52 that I've had since 2008, and I can control DCS helos just fine. I don't have any fancy TM Warthog or Virpil controls.

Any time the TADS is not being used as a sight or as an NVS sensor by either crewmember, it should slave fixed forward. The only time it should turn around to the stowed position is if TADS STOW is selected on the WPN UTIL page, if the TADS system is powered off, or if a boresight sequence is in progress. I believe this has been reported already, but yeah, not accurate at the moment.

You should always get the aircraft properly trimmed before engaging a hold mode. You don't have to, but if you don't, you most likely won't get the results you are expecting.

What AvroLanc said. COORD SHOW enables the display of the points themselves. THRT SHOW enables the display of the rings of the Target/Threats shown.

It's more like "Some players don't want to spend money on the product now, so the company that makes the product gets to decide when they can play it for free" vs "Some players decide to pay money for the product now, so they get to play it now." It's like a person going into a grocery store and asking for a free sample of the new menu item at the deli, and when they are told no the person points to the people in the checkout line paying money for the same thing and asking "Then why do they get to have any?" Just to be clear, no one here is saying that wanting to try before you buy is wrong or a bad choice; I've used the free trial program myself a few times. We're just saying the justifications for some of the complaints in this thread are illogical within the context of how the world works. And to be blunt, insulting those that disagree with you never sways anybody to your side, neither in real life nor on the internet.

Ok, let's consider this logically...Those players that pre-ordered the AH-64D before the module was even released into Early Access, or those that have already bought it after release in Early Access, had already made up their mind that they were going to purchase the DCS AH-64D without any free trial. This could have been from any combination of factors that range from the preview videos and screenshots, review videos done by content creators, or previous positive experiences with other helos developed by ED. Those that haven't purchased the module yet are obviously not yet decided that they want to purchase it, or leaning towards purchasing it at some date in the near future, but may be waiting to see how the Early Access progresses. This crowd is the primary group ED is most likely targeting with their "free trial" program for their modules. So if such a demographic aren't interested in spending money on a product after seeing all the same preview videos, screenshots and reviews as those that have, a bad first impression during a free trial is quite likely not going to entice them to actually buy it. Therefore, ED is gauging when they think the module is in a certain state that they think a free trial will maximize additional sales from those potential customers that remain undecided whether to purchase it. It actually makes quite a lot of sense from a marketing standpoint.

The AH-64D rotor system is a low inertia rotor system, but the variables that affect rotor RPM in an autorotative descent are numerous, ranging from density altitude to cyclic movement, direction and magnitude. I haven't had time to look at the tracks posted by the OP, nor am I interested in making black and white statements on realism at this stage in Early Access. So you can can count me out of the "all the SMEs" generalization, since I don't know where the "all" is coming from.

Not implemented yet. You'll have to manually read off the coordinates for now.

Based on the linked conversation from the other thread, I believe the OP is saying that the laser should be able to physically designate a target for other platforms or munitions out to the maximum DCS laser range of ~8NM/15km, even though the DCS AH-64D only processes the return to a maximum range of 9999 meters. For example, a GBU-12 should be able to guide to the laser designation from an AH-64D that is 12km away from the target, even though the player(s) in the AH-64D only see "9999" in their range readout.

Sounds like you are leaving a stale laser range value in system. If you move the TADS, you need to re-lase the different location, otherwise it will use the last laser range value.

Yes, the actual designation should be detectable beyond 10km by any DCS weapon or LST/LSS sensor capable of tracking it. If it isn't, then it might be worthy of a bug report with the appropriate track file.

That is the maximum range it will display and use for storing targets or other calculations. Light obviously goes on for infinity, but the avionics will only process returns below 10,000 meters, even if the DCS laser energy goes out to 15 km.

@macedk, I've highlighted portions of your post in the quote box above that I want to address. Before I comment on your issues, I want to stress that this is not intended to be a criticism of you as a player, but rather constructive criticism to you (and other players) of how to approach this problem from an aviator perspective. From what I gather, reading your own words, it seems to me the primary hinderance to learning to handle the DCS AH-64 is not from a lack of practice, but a lack of control. When I say "control", I don't mean good HOTAS settings or a proper understanding of how to fly a helicopter, but a lack of control over the aircraft instead of letting it control you. A saying pilots have is "staying ahead of the aircraft". This implies that you are anticipating what is going to happen before it happens, and you are mentally calculating what you will do based on what you expect or anticipate to happen, and then doing it when it is precisely the right time to do so. Take pre-emptive steps to maintain control of the aircraft, instead of reacting to what is happening at any given moment. If you are reacting to what the aircraft is doing after it is already doing it, you aren't actually piloting it. How this concept applies in your case of transitioning from forward flight to a hover? If you know that the aircraft is going to need significantly more collective as it approaches and goes below ETL (Effective Translational Lift) airspeeds, and you know that pulling in a lot of collective will require a significant increase in left pedal to compensate for the increase in torque, you should start to smoothly apply collective before the demand of additional lift is actually needed. This deliberate but smooth collective application should be done in conjunction with a smooth application of left pedal, which is likewise initiated before the demand of counter-torque is actually needed. And because these inputs are smooth and expected, you can set the pace for how quickly they are applied to ensure you can maintain the balance of all the various control inputs. There should be no surprises with basic maneuvers which are adequately practiced. Do not wait for the aircraft to tell you that you need to give it more collective to maintain your altitude. You control the helicopter and tell it what to do and where to go, it shouldn't be telling you what you need to do to save it. If you are reacting to what the helicopter is doing, and then trying to maintain balance of all the forces keeping it in the air and right-side up, you are already behind the proverbial power curve of "control". If you stay ahead of the aircraft and set the pace for the maneuvers at a rate that you can maintain the balance of all the control inputs, you will start to gain proficiency and you will find yourself able to perform the maneuvers at a faster pace more and more. This concept does translate to the simulator 1 to 1. Again, not a critique of your skills, but some advice of what mindset to use when trying to solve this problem (based on how you've described your circumstances in text form).

They did a while ago; it's not planned. Such an item would also be outside the timeframe of the variant being modelled in game.

There are only two bindings for trim. Force Trim Release (which is the Forward direction on the Force Trim/Hold Mode switch), and a cheat that doesn't exist in real aircraft for "Resetting trim". The other three commands on the Force Trim/Hold Mode switch have nothing to do with force trim. Left toggles Attitude Hold, Right toggles Altitude hold, and Aft disengages any active hold modes. This seems to be creating a lot of confusion with players which are convoluting force trim and the hold modes because they share a 4-way switch, but they are separate functions.

Aside from it being a prohibited procedure in the US Army, there is no evidence to support the claim of "many" Apache pilots. I know it is mentioned in a book, and I know one or two pilots that have done it, but that hardly equates to a common technique. One pilot that tried it said it wasn't very effective because you lose a lot of your NVG field-of-view because of where the goggles are required to be adjusted to fit in front of the HDU.

That is an excellent idea.

I think 4-6 seconds would be way to long, and there should not be SCAS alarm because that wouldn't be accurate to the real aircraft and that tone indicates specific things within the AH-64. It's one thing to implement specific control behaviors to account for various hardware options in the game, but changing the nature of the simulated aircraft's actual avionics seems going to far. Personally, I think a better solution would be to reduce the speed that Instant Trim moves to the new center, so that it matches the speed of the Default trim option in the other ED helicopters. This would make the aircraft more standardized within the ED helo line-up and easier to transition between them, especially if those wanted to use the UH-1 as a trainer aircraft for the AH-64. If they wanted to retain the INSTANT TRIM (FFB Friendly) option as is for the FFB friendly behavior, I would suggest that they simply copy the INSTANT TRIM logic to a new option and slow down the re-centering position to match the Default option in the other helos. Maybe even label it "Default" in the Special options so players understand what they are getting when coming from other helo modules like the Ka-50.

The system should automatically detect the presence of not just the missiles but the launchers themselves. Did you turn off the MSL power on the WPN>UTIL page? If not, it might be a bug.

You simply select it. Whoever is the last crewmember to action it takes control of it. George will take it back when you tell him to target the next thing, but until then, you just select it.