DaemonPhobos

The "pointy thing" is a MUM-T upper receiver, fancy drone/video reception stuff. we shouldn't be getting that specific one because it didn't exist back then. The non-DU variation would be cool to have for aesthetic reasons but low priority I think.

I'm guessing you refer to "TUNING:MANUAL /TUNE PRI/STBY selection" when you mean modern variants and I think I get what's the source. Indeed we have that button apparently for presets only as it has been told here. Most of COM page is WIP so it should be easier when we get additional functionality.

The Standby freq is often alternatively called "last tuned" frequency. Your primary (current freq) becomes your standby (last tuned) when you plug a new freq. This new frequency becomes the new primary and your previous primary becomes your standby, This behaviour is correct as IRL.

Not really relevant to the anti-ship discussion, but any word on why the N,M and K2A hellfire variants are not planned? Or is it something that could change in the future?

The HF radio can only transmit and receive free text, some preplanned messages and Present position, and it doesn't use the IDM at all when doing so, think of it as a separate system with very limited data message functionality.

Just to clarify, our current apache module, as the airframe model reveals, lacks the hardware required for "direct" connection to the TI. (Blue force tracker), the SA Data button we are all talking here would enable the display of icons received from the TI. In regards to other forms of datalinks, is up to ED decision and info availability.

yes, it does have the ATM FCR mode, which is a 360 azimuth in wide scan, technically, ground targeting mode would also display helos or fixed wings as well, assuming they are within radar coverage in elevation and azimuth. in the FCR page you can only get the 16 priority target icons, TSD can show all targets classified. the maritime mode is a very late thing added as an upgrade on the Echos Radar electronics unit vor the V6 aircraft, so we won't be getting that one, we will get ground targeting mode, radar map, air targeting mode, and terrain profile mode.

to my knowledge, the only hellfire with proximity fuze is the Longbow Hellfire L7A and L8A, those are radar guided ones. we can clearly see in the video they were actively lasing during the whole missile flight, so it's quite likely we are talking about normal hellfires with impact fuze.

Nope, you will have to trust your hellfires will do the job. https://m.youtube.com/watch?v=E0Jt_Vy4Mj0

No problem haha, no need for apologies, it's normal to ask about details since aircraft have differences from country to country, and there is a lot of wild speculation going around in the forums so one can never be sure when it's accurate or extracted from wikipedia lol.

Iirc, US deltas, or atleast that's what appears to be. Are you an Echo pilot? You have the IZLID/GCP controls only on the weapon page iirc. 321d5cf473d43139f8349d7b6eb7c68c.jpeg_2200x2200q80.jpg_.webp

Unfortunately nope, the laser pointer integration on late deltas had an additional panel with the AWS laser on/off switch in the center pedestal below of the MPDs, so it's quite unlikely at this stage.

from what i understand the PIM codes use channel hopping techniques unlike the PRF which are single channel, i also wonder if DCS will model the pulses per second of atleast the PRF codes affecting guidance, the lower the code number, the higher the pulses per second, therefore, the better the missile guidance should be.

Lol, autocorrect failure, I will leave it that way because lazy Now seriously, weapons processor 1 is mounted on the left EFAB center door 5L160. Weapons processor 2 is mounted on right forward EFAB door 5R86 (you can see this door opened often on FARPs since the Sideloader is there as well.) This is completely abstract for DCS purposes and only informative. WP1 top, WP 2 bottom picture.

The missile should be able to engage the correct target as long as it has an acceptable RCS and matches the target parameters loaded in the programmable signal processor/REU, in case it's not capable of finding the target once fired, it may go for a secondary target assigned by the WP. The missile receives the following info from the Weapons professor: Target status: "ID, target type (air/ground), and LOBL inhibit on or off" ,Target detection time ,Target update time ,Target NED (north east down) position, Updated NED position,Target NED velocity, Crossrange,Height, Range,Range rate, Cross-range: and Aircraft time at request. It uses all of this information to inertially guide itself to the target until it can lock it with its own mmW radar.

The missile leaves the rail at approximately mach 1.4, but it takes around 36 seconds to get to it's max range, depending on temperature. Additionally, once the missile is fired, there is no connection between the aircraft and the missile. The missile will either use it's own mmW radar when LOBL( always LOBL when it's a moving target), or use inertial data provided by the WP/MP for LOAL, then attempt to acquire the target in flight using its own radar.

Afaik, we are not getting the BFT, as it's not displayed in current ED pictures. From what I can understand, AH-64s use the BFT to connect to the Tactical internet, the capabilities are the same since both use the same protocol. It's unclear what system did they use before the BFT with the MT2011 transceiver. According to the 2005 TM, Army aviation uses the BFT or EPRLS to connect to the TI, so I suppose there has to be some sort of gateway back in those days. (Added BFT antenna picture)

An easy way to recognize US deltas from echos is that Es have the VU2 VHF/FM antenna behind the rotor mast, the VOR/ILS receiver at the tailboom, different IHADSS helmets based in the HGU-56P that have two Improved magnetic receiver units at the back of the heads instead of the IR detectors. Post V4 Echo aircraft also have have the link16 antennas above the wingtips. The Echos use the Composite main rotor blades which are larger than the legacy ones, something difficult to see in-flight pictures, additionally, they have a flat underbelly. Also, only the deltas have the HF antenna (towel bar) over the length of the tailboom.

I wonder if they will add all the necessary systems in order to get a full startup as per -10 or CL. The init checks, boresight and BUCS preflight tests are unlikely for EA but atleast for the final release.

I think there is no official confirmation of this yet, but it is a valid armament for our apache, the aircraft can carry it, and it was in service during that timeframe, so I see no reason not to add it. (M255 flechettes)

The size of the complete MPD, no idea, but the viewable display area is 6.25 x 6.25-inch

You are not supposed to aim directly at the target, but slightly offset and short of the target. The M789 HEDP has a butterfly shaped frag pattern with a 4 meter lethality radius in a diagonal shape (forward-left/ forward-right are the areas with most fragmentation.) The gun is called Area weapon system for a reason, it's not meant to be pinpoint accurate.

Maximum effective range is 1500-1700 meters per gunnery handbook Maximum ballistic compensation up to 4200 meters, beyond that you get BAL LIMIT performance inhibits. Typical gun engagements according to most TADS videos are at between 700 to 1000 meters. The round to round dispersion of the M230 is around 3 milliradians by the book, however, that does not appear to be correct per real life videos, probably that's the nominal dispersion of the gun itself not taking into account the flexible turret and other factors.

I'm having a feeling of deja vu right now. Again, the Romeo hellfire has additional FLAT and LOFT trajectories and programmable airburst altitude which our version isn't capable of displaying. I don't see a single flashcard or material showing JAGM integration on current service units, and it is of course not compatible with 2010 aircraft. The AIM-9 and AIM-122 were just tests (I think they were installed for demo purposes only), I believe there was no AIM-122 left by the era the D model Apache entered service. The ATAS is only integrated into export apaches, they require a software that is able to display the associated symbology and function,also, not compatible. The APKWS was not available to the apache even on mid 2012 for sure, some sources quote APKWS was authorized for use around 2015, they are compatible with our apache but they are anachronistic. Regarding the INS navigation for HF, I already told that the SAL 2 hellfires cannot inertially guide themselves to the targets, they require active LRFD lasing. There is no target data handover for SAL missiles unlike RF ones. They just have an internal autopilot that follows trajectories until they get a lock on a laser with proper PRF/PIM codes. All of these are not doctrine, but technical limitations of the aircraft being modeled.