Wags

Around this time next month. We have several other DLCs in the cue before it.

Top left for TDC and bottom right for ownship (but there is a bug with that one). The other two you may see on the HSI are bullseye (BE), not BRA.

The FPAS is number is the expected fuel remaining when the TCN point is reached, not current total fuel.

SA rings appear as a function of the HIDE function, it has nothing to do with late activation. We are looking into additional HIDE options in the ME though.

It's based on how the ROE is set up. As mentioned in an earlier mini-update, right now we base hostile on a negative M4 response. That is perfectly valid if that is how the ROE is set up. Later, we may add other ROE factors like SURV and NCTR that determine hostile/friendly determination.

We found out later that you doiong an M4 interroation from the SA page is indeed possible. Please provide track of 360-degree M4 successful interrogation.

Hey everyone, As some have correctly deduced, we also implemented realistic frequencies for A/A TACAN that do not interfere with the datalink. If you are having issues of C2 aircraft, C2 contacts, and some PPLI not appearing on the SA page, note that that TACAN functionality is embedded in the MIDS terminal. Because the upper antenna filter is fixed, it filters A/A TACAN frequencies on channels 1-36 and 64-99 (X and Y). A/A TACAN channels should be chosen outside of these ranges. The upper filter makes the top antenna unusable for T/R (Air to Ground) TACAN channels 1-29 X and Y, 47X to 63X and 64Y to 92Y. For TACAN channels in these ranges, the bottom antenna is the only antenna for TACAN. [This] causes reduced ranges for DME at channels within the range of the filter when flying directly away from the TACAN station. In addition to setting TACANs within the correct range, also be sure to set the initial waypoint of an AWACS to include an EPLRS advanced waypoint action set to ON. - Wags

It is odd, but it is what it is.

Yes, this is correct as is.

Although termed BRA, this display does not include the altitude element.

Way too late. Order RTB in the port hold.

It certainly works. If you can post a track, I'm sure many of the helpful folks here can assist you.

It is correct as is.

Thanks guys. The issue has been reported and we'll try to fix ASAP.

Dooley is no correct. There is no bug.

It's a fixed threat circle that does not account for altitude, aspect or airspeed. Same as threat circle in ME. It is NOT detailed accounting of engagement range, but rather a very rough estimate. Same as the real system.

Because the D/L had to add new elements to the .miz file, you may need to re-save your Hornet missions that include C2 aircraft. If that still does not work, please delete and replace C2 units. Thanks for the excellent OB reporting so far. This highlights the great value of the OBs. - Wags

Already reported thanks.

Folks, as noted, this is already reported thanks.

No, they should not.

Thanks, reported.

All can say is that the HARM does not, nor should not, provide range data in TOO.

Yes, please provided a track in the bugs and problems sub-forum. No, they should NOT be in sync.

As stated, re-saved.

Not seeing this after D/L has time to update. Enter a bug report with a short track file the demonstrates it here: https://forums.eagle.ru/forumdisplay.php?f=594