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?

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.