Harker

No argument there, I was merely pointing out an undocumented change in the behavior of an existing feature.

2.7.1.7139 Open Beta. Track attached. In the past, the FLIR offset cursor would only update the designation upon TDC Depress. Now, if the ATFLIR is in AUTO mode and the TDC is depressed once to bring up the offset cursor, slewing the cursor around will continuously update the A/G designation, without needing to depress the TDC again. FA-18C_ATFLIR_AUTO_always takes des priority_plus AUTO offset cursor continous des.trk

2.7.1.7139 Open Beta. Track attached. There appears to be some error(s) on which sensor should control the A/G designation and how. Lock a ship with the SCS, with A/G radar in SEA mode. The radar will actively track the ship and a designation will be created (RDR is displayed on the HUD). The ATFLIR is automatically slaved to the designation in INR mode. CORRECT Switch TDC priority to the FLIR page. The radar stops tracking and the designation is now controlled by the FLIR, although the TDC was not depressed on the FLIR page and the mode is not changed from INR. WRONG, the radar should continue to track the target and the designation should be controlled by it, since the FLIR was not commanded to designate (RDR should still be displayed on the HUD). Assign TDC priority back to the RDR ATTK page. It is no longer possible to command the radar to track, with the SCS. Depressing and releasing the SCS towards the RDR ATTK page will flash the display, but it'll not be commanded to track. WRONG, if the radar is commanded to track, it should track and the designation should be controlled by it (RDR should appear on the HUD). The FLIR should, in all cases, be slaved to the new designation. With the FLIR in AUTO track mode, it is possible to move the designation via the RDR ATTK page, with TDC Depress+TDC Slew, but upon assigning TDC priority to the FLIR page, it snaps back to the tracked target. WRONG, the designation should be created on the new point, with the FLIR exiting AUTO and slewing to the new designation. FA-18C_ATFLIR_AUTO_always takes des priority_plus AUTO offset cursor continous des.trk

+1. Both of these are important in the correct operation of the radar and the jammer. Especially the letter is pretty critical, so we won't have to manually use the ECM knob every time.

Yeah, that's a reported bug. Until it's resolved, assign the TDC to another page (any display other than the one with the FLIR), designate with WPDSG and assign the TDC back to the FLIR page.

It had a cockpit overhaul last year and some minor additions. But all major features and functionality were finished early on. The Hornet still has major features and functionality missing and a lot of things are placeholders and WIP. The point of EA, at least in the usual sense, is to last until the above are finished. After that, the product can be maintained and most development resources can be shifted to something else. But for this to work, all missing and WIP items have to be completed while still in EA and the things that are left for later should be things that cannot be done within the current framework of DCS (such as the DTC). Minor additions are fine after EA and bug fixing is something that will continue forever, as DCS is updated and that's normal.

Nope, I had it happen at around 12 NM in MP yesterday. Bandit as L&S on TWS, going for STT with SCS Right and the radar "locks" something beyond the scope, with a range reading of 99.9 NM and a dashed TD box on the HUD. Going to STT with TDC Depress on the L&S worked OK, as well as automatically going to STT from TWS, on an AIM-7 shot.

You should never directly modify files in the installation directory. Use a mod manager, such as OVGME. I've been doing this for years, with zero issues, but I go and check for file changes between updates and adapt my mods accordingly. Just uninstall the mods prior to an update/repair and then modify them as required and re-enable them. As for cockpit and livery textures, install them through the Saved Games folder and they won't be affected by updates, assuming the description.lua files don't change for the original liveries. As always, the use of mods is optional and you use them at your own risk. I also want ED to fix specific issues so I don't have to rely on mods, but until they do, I accept that I either need to wait or carefully use mods.

You mean TOT and FLT? They're working for JDAMs when you're inside the IZLAR, but not implemented yet for JSOWs.

If you're firing from too far away, keep in mind that the AMRAAM has a battery life of 80 seconds. It's possible it's running out during the loft maneuver and then the missile naturally goes ballistic.

Seeing a missile on the scope is one thing, but currently, an STT lock can change from a bandit that's going 0.9 Mach, hot, 15 NM away, to your launched missile that's 2.5 Mach, cold, 2 NM away. Zero range and velocity gating is currently implemented, it's kind of a mess.

When you say "a perfect track", is it range resolved? Because if not, then it's an AOT and that's correct behavior. And why would you be able to break the track by turning the ECM on and off? What should happen in his case is that the track would switch between a fully resolved track and an AOT (resolved in azimuth, elevation and range vs resolved only in azimuth and elevation). You are helping the F-18 if you turn off your ECM, because you're giving away your range. Why would turn off your ECM in the first place? If the AMRAAM behaves like it knows the range, then it's a bug with the missile or the radar-missile interface. The pilot in the F-18 does not have information about the range, with their own radar. Finally, of course having an AWACS will help the F-18, why wouldn't it? The entire point of a datalink system and the MSI system in the Hornet is to help with SA and situations like this.

The F-18 cannot achieve a lock either past 22 NM, on jamming targets. They are kept in the system as AOTs (Angle Only Tracks), without range info. For the F-16 and F-14 I agree, their radars are unaffected by jamming and for the JF-17, I don't know.

The steering dot is there to guarantee optimal kinetimatics at launch, it has nothing to do the with guidance of a missile equipped with an INU. Guidance might be not optimal, but the missile will not go stupid. This is probably related to the AMRAAM's interaction with ECM.

IIRC, HACQ should indeed always remain slaved on the JHMCS, regardless if you're looking through the HUD or not (because with the current DCS implementation, you get a dead zone around the HUD). I don't recall where I saw the info though.

TIR user here, same. Although I also couldn't really make it work, but I'm pretty sure that's on me. A friend of mine who's slewing with a joystick hat found it more useful and he's better at employing as well.

Again in pg 254, it's described that for OFP 10A, it's always a circle, but 10A refers to the A Hornets. nnA=F/A-18A, nnC=F/A-18C, nnE=F/A-18E, nnX= both FA/18C and F/A-18E.

AGR stands for Air to Ground Ranging, where the radar is used to get the slant range to the target. This mode is automatically enabled when you go SCS Fwd when in AG mode.

If you look at pg 254, there are two versions, depending on the OFP. With 15C, it's a circle when undesignated and a diamond when designated. Maybe pg 193 has a generic example.

Yes. It allows the AIM-9X seeker to look up, without the pilot needing to do so. It looks up and left/right, approximately above the left/right edges of the center mirror, depending on whether you're looking left/right. I haven't managed to get much use out of it myself, but others might like it.

Yeah, it was what I was thinking. Unless I'm mistaken, we can see that in DCS right now. Circle when the WP is not designated, diamond when it is. The circle/diamond logic might be a little wonky in DCS, but it's there. I'm not at my pc right now, but I'll check when able.

SCS Aft with JHMCS knob to on will enter UPLOOK mode. If you want to enter VACQ, you go SCS Left and then Aft. Without JHMCS, you should be able to enter VACQ from any other ACM mode, with SCS Aft.

It's trying to fly the course, not the WP, if you have a course set up. Disable the course (deselect and reselect WYPT) and it'll fly towards the WP.

Page 254 of the pdf, for example? I think we have this already with the A/A WP option, unless I'm misinterpreting the document.

The Trigger launches A2A missiles and fires the gun, while the Weapon Release Button (red button at the top of the stick, to be pressed with your thumb) launches/drops A2G munitions. I have a question, were you locked by a SAM when this occurred? Was your HUD saying HARM?