Harker

New changelog just released, it's not mentioned there, sadly.

That's a problem with how servers are set up and/or how people play, it's not a problem with the module. IRL, you don't often have the same type of aircraft on opposing coalitions, but even if you do, you deal with it through proper situational awareness and sensor practices, planning and usage of other tools at your disposal, such as comms. Unfortunately, these are all things that people often do not make use of, in DCS.

I'm not going to discuss the viability of employing AMRAAMs against non-radar trackfiles, but the Hornet has MSI, the Viper does not. An MSI trackfile can be created by means other than the radar, the radar is just a contributor to MSI. The DL, FLIR, CIT and HARMs are other contributors. Hornets can rank and designate offboard trackfiles, same as radar trackfiles. You can read the relevant info on the 742-100.

Well, the main point is that you get to have situational awareness of your surroundings, regardless of what you see with your radar. What you do with that info, is up to you. I personally use the SA to make tactical decisions, on when to commit, when to re-attack etc. Just keep in mind that DL-only info has a 12 second update rate, in DCS. You can indeed use it to silently hunt for targets and either go for AIM-9s or enable your radar for just one sweep with ACTIVE, find them and launch an AMRAAM (I'd still recommend that over MADDOG launches). You can set up your radar's azimuth and elevation before going Active, based on the datalink info. You can also use it to help you quickly lock targets with LHAQ. You can see the target's DL info with the JHMCS and use LHAQ to get a lock from further out. You can do this straight out of SIL, as entering an ACM mode will automatically exit SIL. Also, in the future, once/if MSI is properly implemented, you'll be able to designate DL-only trackfiles with your radar, in the same way as you can do now, with radar trackfiles, allowing you to, for example, receive targeting and intercept cues on them from further out or from within SIL. And they can also be included in the ranking order and designated for TWS AUTO. But this is all functionality that's not implemented right now, so we'll have to wait until it is.

You can place the TDC over the desired contact and press STEP. This will remove the TDC and place a box around the contact. You can also use STEP without the TDC and it should step the box through contacts, in order of rank (in DCS it's kinda random sometimes). Or if you have an L&S, it should always be stepped on first. Be aware that STEP can exit by itself on occasion. But in principle, it should allow you to have info on a contact, hands-free.

I haven't checked in a while, but do you know if CSS is still bugged when adjusted with the trim hat?

Also tested it. The range gate is set to 40 NM, according to the RDR ATTK page and the actual limit is the acquisition range (because detection and acquisition ranges are apparently different now) in Medium PRF. I could lock a MiG-29 at 20 NM, for example.

Also had it happen once, on our server. Same mission as before and every client experienced it.

It's far from being mostly complete. I'm just trying to inform here, a lot of the following items are not frequently discussed outside of specific threads and posts on the Hornet. The radar has several major issues (including wrong memory logic, wrong TWS AUTO, too slow TDC speed and two missing modes - VS and TA), MSI is still not implemented at all, AZ/EL doesn't show off-board tracks, SA doesn't have the same ranks as the Radar page and you can't designate from it. The RDR/JMR priority option is also missing from the radar page. The RWR has wrong threat ring logic and missing cues, since launch. The HSI is missing functions and is the wrong HSI configuration for our Hornet - we should have TAMMAC, with, among other things, the ability to load between chart, elevation and (sort of) satellite maps, like in the Apache. The INS works terribly without GPS, way worse than an INS should. A/G weapons delivery is using the wrong input from sensors, even with AGR enabled. The ATFLIR is missing the AUTO acquisition window (A/A and A/G) and it's missing TWS mode for A/A, as well as the ability to be cued by the HMD in A/A. We're missing terminal delivery options and associated HSI cues for the JDAM, JSOW. There are other items as well, like you mention, but these are some big issues that need to be resolved. Especially the radar and RWR related stuff, they're really holding the Hornet back in the A/A role, for example.

See this thread: /topic/297325-new-exhaust-effects-on-missiles-are-gone/ I tested with AMRAAMs and Hellfires, myself. Both were using the old exhaust effects.

Good observation. I just tested and saw the same thing myself. Edit: I posted a bug report about it.

/topic/297272-harpoon-agm-84-explodes-immediately-after-launch/

Not seeing a mention of a FLIR fix for the ED's jets in the patch notes. I hope it made it in and it's just not mentioned. EDIT: Nope, just polarity fix...

Hadn't thought about that. If that's indeed the case, then we're done here.

As seen in the following and other videos from our Hornet's time frame, single stems can display different emitter codes, from the same azimuth. In DCS, all emitters have their own stem, often causing emitters to be on top of each other, making them unreadable. Maybe this is something the team can look into. This shows the behavior I'm talking about, from 2:36 and after: An example from DCS is also attached.

That's the actual bug here. AUTO will only update the designation if the TDC is assigned to the FLIR page. This is wrong, because as long as the FLIR remains the designating sensor (and it does, indicated by the FLIR cue on the HUD), it should continuously update the designation, regardless of TDC assignment. The laser is firing at the tracked target, since it is tied to the FLIR LOS, not the designation. I cannot submit a track right now (the OP's track should suffice), but it is very easy to reproduce: Load the ATFLIR. Track a moving target, using AUTO. (Zoom in) Observe that the designation diamond is following the moving target. Assign the TDC to another page (SA page, Radar, Maverick etc). Observe that the ATFLIR is still AUTO-tracking the moving target, but the designation itself remains stationary. Notice the FLIR cue on the HUD, that informs that the FLIR is the designating sensor. On a side note, the A/G radar in FTT does not suffer from the same bug.

I'm thinking the same thing. To get where we are already, it's clear that certain documentation was used, because info on the DDI pages and other avionics functionalities is not available anywhere else in the public domain, otherwise others would be able to find it as well. So, when we talk about certain features, they are often on the same chapter or even page as something that's already in DCS. I assume ED has the same or better access to manuals than most of us, so all we do is point to pages in docs they already used, to an extent. Are certain parts in these docs out of limits? Why is one thing OK and not another, when both things are on the same page? ITAR doesn't work like that.

Yeah, if you can detect a target reliably, you can also command STT on it. STT can fail if commanded on a trackfile that the radar fails to reliably acquire, but if you're already detecting the target without issues and a good update rate, STT should work as well. As for the memory logic, it's still not working correctly, same as before. MSI memory doesn't exist and the Radar memory is still controlled by the brick timeout, whereas it should be dependent on radar frames. Are you seeing something different? Because I can't notice a difference from before.

I agree. Several games implemented both DLSS and FSR. Also, for now, DLSS is arguably superior to FSR, so it would be a mistake to not include it, IMO.

In addition to other radar and MSI stuff that were already mentioned, Radar-only track memory and MSI track memory (different things). RDR/JMR priority. TAMMAC, with CHRT, DTED and CIB (can be used in essentially the same way as in the Apache, and since ED did it already there, they can do it here). ATFLIR TWS mode. RWR filters. RWR-INS coupling, emitters should smoothly move in azimuth during turns, regardless of the actual RWR signal update rate (which corrects the detected azimuth). Harmonization of display element refresh rates on the HUD and JHMCS, specifically the RWR stems (see above) and DT2 target box.

2.7.11.21408.1 Open Beta In A/A mode, with a missile selected, when commanding ACM, the PRF will change to MED, regardless of the previous PRF setting. Bug: When exiting ACM (either with the NWS/Undesignate button on the stick, RTS or unboxing ACM), the radar should resume the previous PRF setting. This does not happen in DCS, currently. The radar resumes all other previous settings, except from the PRF setting. If another missile is selected with the Weapon Select Switch and you then re-select the previous missile, the original, correct PRF is selected again. Track attached. FA-18C_exiting ACM does not resume previous PRF.trk

It's still an old missile and terminal guidance is required, otherwise a hit is not guaranteed. Even with GPS assistance, it still has a CEP of at least a few meters (as any INS+GPS guided weapon), probably more, given its hardware. It should most likely miss, without terminal corrections. CEP is already implemented for JDAMs (unsure if it's in for JSOWs), it should be implemented here as well. Even the SLAM-ER should have a small CEP.

Hi Flappie, I tested again, after a repair and the issue seems fixed. I had a few crashes related to Weapons.dll, so I deleted it, run a Repair and all works OK now. I do run mods, but always test in vanilla, after updates. Thanks for taking the time to check regardless! Cheers!

I appreciate you testing this yourself. I think it's better to look at vehicles/aircraft with a camo paint scheme and writing, as well as jets (especially in afterburner). In the new FLIR, camo patterns and writing are not visible through the FLIR and jet engine exhaust is visible, with afterburner being much more visible. In the "old" FLIR (F-18, F-16, A-10), you can see the camo and the writing, and exhaust trails are not visible (smoke can be, but not the same), with afterburner also not being particularly bright, merely showing up a little bit. That's because the "old" FLIR still uses the simple color filter, as before.

You have the filter active now, try disabling it. As for pre-set loadouts, you can create your own, by clicking on NEW and then opening the ordnance menu with by right clicking inside of the empty station boxes.