Raptor9

As other uses have stated, DL Net is required to share any data between aircraft, which is still in development. When this item is released, expect an announcement on the forums here: To be clear and to manage expectations, the DL Net and Tactical Internet are separate datalinks, the latter of which is not planned. DL Net is the only datalink type that is planned in DCS: AH-64D.

As I already stated, the K and L are the only ones planned. As these are already in game, no further AGM-114 variants are planned.

As the tag on this thread states, only the K and L models (which are currently in game) are planned. Also, any comments I've made on this forum prior to late 2022 were made prior to joining the ED team, and are not official statements about any ED products or development.

Snowplow should only be available in NAV master mode (with the FCR in A-G mode) and "pre-planned" A-G sub-modes like CCRP. It won't be available in "visual" A-G sub-modes like CCIP, STRF, VIP/VRP, etc. The manual is currently being revised to go into further detail regarding how different sighting modes like Snowplow should work, and also when they should not work.

The "PLT NVS switch" is a typo in the controls that has been reported. It is meant to be "CPG NVS switch" and controls the NVS switch in the CPG cockpit. Both crewstations can use different NVS sensors independent of each other, which is why they have separate switches.

He asked how to cycle between the missile types. To do so, you need to select TADS as the sight. Since only the CPG can do that, contextually only the CPG can toggle between the missile types. FCR forces the type to RF, HMD forces the type to SAL. He could not get the missiles to toggle in the front seat because he did not set TADS as the sight. When he returns to the back seat, he tells George to toggle the missile types. George selects TADS as his sight during this process to achieve the result, so when the OP returns to the front seat, he finds that the missiles can now be toggled. The missing step was to select TADS as the sight, which George was doing for him. He isn't selecting RF missiles in the backseat, he is commanding George to change to RF missiles in the front seat, which George does after George sets TADS as the sight.

No, it is not possible, since you cannot select TADS as a sight in the Pilot seat. That is not a bug.

The Communications system is receiving a lot of major development "under the hood" and these functions will return when complete. This is a temporary but necessary measure. Thanks.

I was talking about how specific hardware devices may have mechanical play or inaccuracies, leading to instances where the user inputs may be violating the breakout values simply due to the fact the input from the device may be moving around due to loose springs or inaccurate input sensors. It isn't related to anything with the flight model, just hardware input limitations.

Sorry, what I should have said was "do not make any inputs from the force trim reference point using your stick." In real-life, the cyclic would remain where it is. In DCS, when using a spring-centering stick, the assumption is you are letting it spring back to center when trimming, which means don't apply any inputs after that.

Such options are being looked into for the very reasons you've mentioned. But as the case with all things, I cannot make any promises or provide any estimates, but just to assure you that we are already aware of how such situations can complicate the intended logic.

The point is that the slew rate comparisons between DTV Wide FOV and FLIR Medium FOV do not apply. The DTV Wide FOV should be compared to FLIR Wide FOV, not FLIR Medium FOV.

Dear all, it needs to be understood that everyone's experience with the flight model of the DCS AH-64D may vary somewhat based on the hardware used and the individual settings they have set in the options. Because of the various hardware combinations (or personal preferences) that we all have, as many options to tune the individual controls are provided, and some additional options are being looked at to provide even more tailorable configurations for flight control. As an example of the desire to provide as many options as possible, we've provided some additional controller options this patch that allows users without an analog axis to adjust how their 4-way or 8-way hat switches control the TADS. Having said that, due to the varied experiences that people are having, we can only state when changes are made to the flight model, and when they are not. As I have personally stated multiple times in this thread and others, the facts are the facts when it comes to what is included in any given update. If someone experiences something different following any given update (whether perceived or real), we are not saying these experiences are not occurring, we are simply stating whether the flight model, SCAS, or hold mode logics have changed in any given update. No more, no less. One final note based on some confusion I am seeing in this thread. The shaded area in the Controls Indicator corresponds with the range that the FMC can move the swashplate independently of the pilot's control positions. However, the Attitude Hold (whether it is in Position, Velocity, or Attitude Hold sub-modes) will only engage if the cyclic is within the "breakout" value of 0.25 inches from the force trim reference position (with some additional criteria as well, such as pitch/roll rates). This equates to roughly 2.5% of the axis travel in either direction (actually 2.5% in pitch, 2.25% in roll). If you enable the Attitude Hold but continue to move your stick around in excess of 2.5% axis travel from the last position that you released the force trim, the Attitude Hold will not engage because you are telling the FMC that your intentions are to fly the aircraft yourself. To get the Attitude Hold to work for you, fly the aircraft to the desired state while pressing the force trim, then let go of the force trim and do not move the cyclic. If you move the cyclic and exceed the "breakout" value, even if the force trim is not pressed, the Attitude Hold will disengage.

It is not possible to fire the AGM-114L onto points (Waypoints, Control Measures, Targets, etc) stored within the aircraft database. The AGM-114L needs targeting data from a sight (TADS or FCR). Points can be set as acquisition sources which can cue or slave a sight to a location, but the sight (TADS or FCR) still needs to generate its own target data for the AGM-114L to use.

The mixed missile loadouts were already being discussed internally prior to the update. We don't have any news to share on that regard, and are making no promises, but we are aware that different Hellfire types can be mixed on the same 4-rail launcher in real life. We are also aware of some issues with George's use of radar Hellfires when not in a stationary/near-stationary hover.

I wasn't offended, nor was I responding to your previous posts with any emotion, I was stating things as facts as they exist in DCS, with some real-life context added. George is still WIP, but he is designed to emulate a crewmember working with the same limits as a human operator. If you are so close to a target, that is inside the minimum laser range of 500 meters and he may have determined it is too close.

We can take a look at the slew rate when in FLIR Medium FOV compared to the FLIR Wide and Narrow FOV; however, the DTV does not have a Medium FOV setting. It only has Wide, Narrow, and Zoom settings. When the Medium FOV command is pressed, it sets the FLIR to Medium FOV but the DTV is set to Wide FOV, which is why the DTV appears to have such a high rate of slew when Medium FOV is pressed, because it is actually in Wide.

There may be other reasons too, like if flying erratically and he is having trouble keeping his crosshairs on target. Or perhaps inside a minimum range. If a target is 200 yards away, the pilot should be engaging with the gun from the helmet sight while flying away. Enemy positions at those ranges are not targets, they are threats.

Any time a crewmember actions a weapon, it will take control away from the other crewstation. Crew coordination is important. George will not fight you for a weapon, but as soon as you interact with him again, he will take the weapon back that is currently assigned to him in the AI menu. But if the CPG is shooting the gun at a target and Pilot sees someone close by that is about to shoot down the helicopter, and needs to take the gun to engage the higher threat, the ability to take a weapon from the other crewmember is important when speed is critical.

Just because you can do something, doesn't mean it is optimal. I can shoot at a target with the gun while doing a barrel roll, but it doesn't mean those rounds are likely to hit. George is programmed to engage targets based on what is optimal. If the symbology presents a weapon inhibit message, he won't fire because he recognizes that as a condition that might cause the engagement to be unsuccessful, just like a real crewmember.

The weapon actioned in the crewstation is targeted by the sight selected within that same crewstation. Weapons actioned in one crewstation cannot be fired by the other crewstation. The only exception to this logic is COOP rocket mode, but in this case both crewmembers are actioned to the rockets and both crewmembers receive the same targeting information from the CPG's sight. It is not possible to employ a weapon independently of the opposite crewstation while simultaneously using the sight from the opposite crewstation. The laser-guided Hellfire doesn't need to receive guidance from the launching platform. When the pilot shoots the laser-guided Hellfire from the backseat, it is essentially a "remote" missile shot, meaning that the missile is being fired on someone else's laser designation. Whether that "someone else" is a JTAC, a drone, another aircraft, or that pilot's own CPG in the same aircraft, it doesn't matter. The pilot is using HMD as his sight while firing that missile, which cannot fire a laser. However, since the radar-guided Hellfire does need to receive targeting data from the launching platform (which the HMD cannot provide), the RF missile type cannot be selected and the SAL type is automatically selected and "barriered." This behavior is described on page 165 of the DCS AH-64D Quick Start Guide.

Correct. Engaging LMC shouldn't change any existing slew rates. The only time LMC should affect the slew rate of the TADS without user input is if the range is updated to a different value. When the range value changes, the existing angular slew rate being maintained by LMC is adjusted to maintain the same angular velocity at the new range value. LMC shouldn't perform any stabilization onto a point, it should simply maintain TADS angular rates independent of the aircraft angular rates.

The previous behavior of the LMC, in that it would ground stabilize when engaged, was not accurate. The current behavior is more accurate; the CPG is required to manually adjust the slew rates to compensate for linear motion.

The DCS F-16 early access guide includes a takeoff speed chart in the Procedures chapter as well as Appendix A. Look for the Takeoff section.