Santi871

Nice catch, thanks. Also noticed it with the ATFLIR waypoint symbols. Reported both.

Reported, ty

Yes

It is slewable and also azimuth stabilized.

Yes, this is how it is. AMRAAM or AIM-9 has to be mounted on a LAU-127, which itself has to be mounted on the sides of a LAU-115 (not underneath) which is then mounted on the pylon. The only operator which can mount the LAU-127 directly onto the pylon is Switzerland AFAIK. This was later "fixed" in the Rhino. More info in this thread: https://forums.eagle.ru/topic/186219-fixed-internally-wrong-launcher-rails-for-aim-9s-and-aim-120s

Have you assigned TDC to the HUD? It should say "AGR" below the altitude window. As for OP, lemme know if you manage to reproduce.

It's fixed internally, just didn't make this update

Reported.

This should already be fixed internally but I'll double check

That's a feature, not a bug. It's done that way so you can step the L&S to a popup threat without having to step through the entire bank of tracks.

It seems (if I'm interpreting it correctly) the color map might be heading up oriented instead of track up which would obviously be a bug, let me run a few more tests to confirm and report it.

The HSI is oriented track-up in your track/video. It's just that when sitting on the deck on the moving carrier there can be a big discrepancy between the track and heading, probably due to the slight wind and invalid air data. It goes away as soon as you takeoff or taxi around a bit. IIRC I've seen it happen in the real jet in youtube videos but I'll double check to make sure. Note that there is a CV alignment issue which which is already fixed internally but with GPS available and the INS set to IFA (as in your case) you won't be affected by it anyway.

Reported, thanks

Real HUDs depending on their technology have limitations. Not only in the display's refresh rate but also in the rate at which the data is transmitted to the unit. As far as the Hornet is concerned we are talking at least 2-3 decades old tech, the data rate limit of the avmux is modeled and that's probably what you're noticing. And in a Rhino Can't speak for other modules, you'll have to ask their developers if they're modeling things like that.

It's a bug and we'll look into it (for A/A). For A/G the diamond reticle is normal and indicates the pod is slaved to the A/G designation.

Lubber line = heading line, that should be there and it's not ingame, but the other guys seem to be referring to the heading select command marker which I don't think should appear in SA.

You guys are mixing things up a little. The release point for auto is wind corrected once you've reached the release point in terms of compensating the wind effect on munitions. What's not wind corrected (and should be and it's reported) is the ASL and steering cue not lining you up with the release point with wind correction. So if you center the ASL and fly straight and level you will drift and have to constantly correct it until you reach the release point like in the first post. For example, set up a left to right crosswind and line up with the ASL 20 miles from the target. Fly straight and level. The ASL will end up left of your velocity vector. That shouldn't be happening.

Yes it's correct. I'm not sure being able to override AUTO by reselecting CCIP is correct.

Yes. It's something I have to report.

The bars coverage in the Hornet is correct. The Viper has a non circular antenna that is wider than taller which results in an oval shaped taller beam, hence the larger coverage.

I have already reported this.

In USAF/ANG F-16s, the wiring that provides HARM and Maverick video is not installed in stations 4 and 6. This means the weapons can be installed and ferried but they are not functional (which is why flight manuals indicate it can be loaded). Not a matter of opinion, a matter of facts.

Np. Reported.

Radar track files should be deleted when ACM is entered. I'll report. Seems like the issue only affects the helmet modes though.