Ahmed

Thanks for the lesson. And yes I happen to know quite a lot about software development

Hi, CPHR option is currently completely non-functional in the UFC COMM display. While this doesn't add any value to single player, being able to cycle through the different UFC CPHR options would allow to use secure comms on both radios in MP via tools such as SRS, and it is likely a <5 minute fix.

Highly doubt it will make it into the module, although it would be great to have a more accurate drag modeli, accounting for interference drag, indeed.

sorry for bumping but, did this get finally reported? I pm'd BIGNEWY a quote of this from a real document.

It is a simulation within a simulation. However, it would be useful to have it properly simulated nevertheless (the number of 'live' missiles is limited in-game too after all)

Hi, The SA FRIEND sensor filter acts as some sort of "magic IFF" tool when both coalitions have the same aircraft. With the default "FRIEND OFF" selection, in a setup like in the attached track, despite both emitters being virtually the same emitter and triggering the same RWR indications, the SA and RDR ATTK still filter them and only display the EW symbol for the hostile Hornet. magic.trk

Hi, This is probably heavy WIP still, but the RWR tones don't sound at all similar to the ALR-56M. Here you go a couple of videos to illustrate: 2:35 - New airborne (or ambiguous) threat tone (missing in DCS) 3:07 - Missile launch tone 3:23 - Missile launch "recycle" tone (to be played every 15 seconds after the missile launch tone -- currently in DCS the missile launch tone plays continuously instead of playing once and then playing the (slightly different) recycle tone every 15 seconds) And in-between all that some (clamped? idk) prf tones. 36FS Fiends - Red Flag Alaska Ep 2 - YouTube with some audio in the first minute (including new ground threat tone at 0:31) I hope it helps the team understand the "abstract" wording in the documents describing the ALR-56M tones.

And the track 75.trk

Track attached elevation.trk

Forgot the (very short) track AACQ.trk

Hi, CVN_75 doesn't have an entry in the AN_ALR_SymbolsBase file, thus sowing as U in the RWR. Additionally, it doesn't seem to have a hardcoded ALIC (in case anyone is planning on shooting HARMs at carriers). Additionally, providing an external file to define ALICs instead of having them hardcoded would make these issues easier to fix, without requiring several module updates to include new unit ALICs each time a new unit is added, and also would easily support 3rd party modding of new units. Not having them hardcoded to the unit's GT name would also prevent the different Nimitz carriers from having different ALICs while having the same radar emitters types.

Hi, currently you can't adjust antenna elevation while in SIL (the elevation caret will move to the commanded position when the radar is taken out of SIL though). This "looks odd" and I can't find any mention of this on any document, so I sort of report it just in case... Is it is possible for you to consult this with your SMEs?

Currently selecting AACQ when SIL is boxed will make the SIL option disappear (as it is not available during AACQ), making it impossible to unbox SIL and keeping the radar silent forever (workaround is to go into ACM). Correct behavior is: entering AACQ should automatically take the radar out of silent mode.

Hi, There have been some threads about the track up format and the SA/HSI on the carrier, but I couldn't find this specifically. In the attached track you can see how the SA-2 threat ring and the friendly E-3 donor symbol show up on completely incorrect bearings while the Hornet is sitting on deck. SA.trk

There is likely a small underperformance indeed, compared to usually quoted ranges of detection of the real one and hearsay. We will see when ED adjust the APG-68 how both compare (i.e. if they get the same detection performance then ED are definitely doing something wrong). A related and probably more important problem are the RCS inconsistencies in the database across aircraft, and the external stores not affecting RCS.

^^^ this. Plus DCS would also benefit a lot from modelling external stores affecting RCS.

While waiting for ATC to issue QNH, you can always do it the old fashioned way and convert QFE to QNH.

Several systems can be configured by the pilot to bump up the lethality shown for "low level" threats. I haven't read anything about the F/A-18's ALR-67 being one of those. However, it does discern between lethal and non-lethal threats, just not in DCS because ED interpreted the documents in a different way, that can easily be demonstrated wrong by watching any HUD tape on youtube that includes EW symbology. Hopefully something that will be fixed at some point.

Deleted: misread units

Currently, while some units such as ships seem to have multiple radar sensors modeled in the database, this seems to be ignored by the RWR and HARM that seem to reference the emitter unit rather than its sensors. This affect specially naval warfare. This would be an area where DCS has some room for improvement in the future, and maybe something that can be worked on now that IADS and some EW/ESM seem to be on the roadmap. Additionally, many newer systems (such as the SA-12/S-300V 9A82/9A83 TELARs, or many naval units such as Aegis cruisers) use an illuminator for terminal guidance that is different than the radar used for mid-course tracking, that should be modelled too as it has a big impact in various aspect of the EW arena, ranging from system survaivability and multiple-target engage ability, to late RWR launch detection.

Apologies I didn't realize I recorded that track with a naval unit that is not in the threat library, and that this fact could lead to confusion. I have re-recorded the same using Pyotr Velikiy to show that it happens with all naval SAMs. naval_piotr.trk

Oh no. This again. I just wonder how many of those defending the "airplanes can land anywhere" principle have actually landed any real plane (bonus points if bigger than a 172) in an unprepared strip.

Grimes has already replied, but, as for this, all the changes and new functions I've seen in 2.7 were already documented in their wiki when I checked, so most likely yes.

Currently in-game, the SAM light only illuminates when a SAM radar is locking prior to missile launch. At missile launch the SAM light extinguishes and is replaced by the CW light, regardless of the guidance type (command/SARH/TVM/SAGG/mid-course-GAI). The CW light should only come on for guidance types that rely on a CW emission for missile guidance. The SAM light, according to the very own DCS F-18C manual, should behave as follows. Track attached with SA-2 (command guidance) example. cw.trk

Hi, Currently in-game, when engaged by (at least some) naval units, the symbology in the EW page and RWR don't flash (and they should also flash in the HUD as reported here), unlike when engaged by ground/air threats. Additionally, and as part of the same issue, the "SAM" light in the right advisory/threat warning indicator panel does not illuminate when locked by a naval threat. Track attached. naval.trk