Hulkbust44

That's not what they are talking about. It's a different AP nav function that at least was working. OVFLY and REF WP do work last I checked

Cold? absolutely, here your target is at mach 1.1 Granted the LARs in DCS are too conservative last I checked.

As per Changes since 15 May 2003, the SA format navigation data should be in white when displayed on the AMPCD. Lines, waypoints, nav target's etc should be in white. When COLOR on the Attk>DATA format is unboxed, all AMPCD format data should be displayed in white. @BIGNEWYPM coming later. white_text.trk

As seen in the track, the radar contribution circle indicating that the radar is contributing to the displayed trackfile, is missing. In all search modes, and track modes, the circle never appears. For reference the circle in seen in the ED early access guide multiple times, but I haven't seen anything from ED about it. This is a crucial component of the A/A system for the Hornet. It's the radar contribution circle that will distinguish FLIR, HARM, L16, ASPJ, and CIT only onboard tracks from the tracks that have the radar as a contributing sensor. Knowing what sensor is building or helping the trackfile is critical to understanding how valid/accurate the data is. norcctrk.trk

in SCENE and AUTO it will always try to keep that track. AUTO will even coast for a bit if looking at a moving target. Cycle to INR and undesignate if you just want to point it.

Until we get the -210 we won't know for sure, but those numbers sound just fine, the -402 should be more efficient.

It's what is stated in the radar manual, 742-100 I believe, and 600-100. Also rember the elevation scale is not always fixed, there's a option at OSB 11.

Issue sounds similar to what you see if you move before the ground crew is done rearming.

@BIGNEWYWhat do you mean "pm evidence" ? Why don't you think this is a bug? It was working before a certain patch and the change was not announced, it is then a bug. This is an unintended change to the code that you are just inherently defending? Ask the team if they intended to change the SA EXP logic with the map enabled. This specific issue I reported a few years ago, it got fixed, and it now it's back.

That's basically it, the problem with this post has to do with the EXP of the map being wrong.

We already have an A+, just with more powerful engines...

There's no FLIR FOV on the HMD as ED hasn't added it yet...

IIRC it should be a smooth 3lbs all around until alpha becomes a factor at 22 deg and modifies it.

The last official comment I saw here about the Close Air Support Format was that it's "not correct for our version" What prompted that? It should be, so what does ED need for evidence? We have the 2002 paper which details every element of it's functionality more so than any system we currently have... Official technical document from 2001 describing "Free Text Messages" use via the Variable Message Format for transmitting and receiving CAS mission data. This is done via the Comm 2 ARC-210 (DCS) "F/A-18C/D AFTER AFC 269 one ARC 210 DCS (Digital Communication System). The ARC 210 DCS is only installed as a comm 2 radio" "With AFC 270 the Multifunctional Information Distribution System (MIDS) is installed." AFC 269 and AFC 270 are BUNO 163427 and up (Lot 10 Hornet) Our aircraft is the second to last Legacy Hornet produced at BUNO 165407 The ARC-210(DCS) and VMF/CAS format absolutely belong on our 2005 aircraft.

And which is that?

That's not true with the ATFLIR, never has been. SCENE and AUTO will always provide a designation. INR would be the only one that needs a command. Just like the others. "It is a bit nerving that I can not "hook" on markpoint on SA or anywhere, I need to use the up and down buttons and designate it as TGT." Yep, that's not a Hornet design issue, it's an ED lack of implementation issue. Everything on the SA should be selectable with TDC deppress...

Just read the latest Hornet mini-update, and I must say it sound like a great plan with good priorities. As always, the MSI line caught my eye. "A review of MSI functions based on available data for the version we are modeling." @Wags @BIGNEWY This begs the question, what version are we modeling? In this case we're talking about the digital data computers config and not an OFP.

Would this be the same for the monochrome map if enabled on the DDIs?

We're also talking about a helicopter here, however correct me if i'm wrong, DCS doesn't model the rotors when it come to RCS. If it did, at these ranges you really couldn't lose the target due to velocity gates. Paging @Beamscanner (when it's not Dec 24th...)

Once upon a time this was still possible as well...

When you have a surface TGT and attempt to EXPand on the SA with the MAP enabled, the display just expands over and tracks with your aircraft rather than the designation. The use to be an issue for aerial tracks as well but ATM it works. noEXP.trk

I set the HARM format as TDC priority in TOO, yet there was no TDC cursor so I am unable to select a HARM target via TDC. Source: Hornet EA guide null noTDC.trk

Use the AZ/EL and not AUTO. Let's you change azimuth and elevation simultaneously.

Can you restate the question?

Yep, HARM, ALR-67, and ASPJ all work together. To the point there is an caution on the RWR display for when it can't talk to the HARMs. We're still missing things like TOO range known vs unknow and TGT designations. Also A/A sensor contribution, MN FILE, actual PB capability...