Harker

The correct behavior is that Offset elevation is the absolute value of the Offset itself, not the difference between the Offset and the Waypoint (so it's now correct in-game). If the game manual says otherwise, it's a mistake.

According to documentation, STT should indeed be not available when in the A/G master mode.

You can switch to the A/A radar by selecting AIR, but the only modes available are RWS and VS (no TWS, since trackfiles are not build in A/G master mode). Automatic acquisition modes, as well as STT, are unavailable.
 

The relevant info I've found does not indicate that setting someone as a Member should do anything for them. This is you, selecting a PPLI to display as MEMB2, in this case. Even if there was syncing, the only way for their jet to know you're actually MEMB1 (instead of 3 or 4), is to be able to sync the entire group.

As I understand it, each pilot can set their MEMB list as they want. The Lead can also be distinguished by marking themselves as a Lead in the TGT DATA page, which will show an "L" next to their PPLI (that way, other flights can see all leads, and better keep track of different flights).

The trackfile's position on the display is extrapolated between detections, using the stored target velocity, to present a smooth and continuous picture to the pilot. It's reasonable to assume that even if the target is detected in a closer bin, the MC knows the target didn't physically jump there, given a stable velocity.

An alternative would be to present the trackfile always in the bin in which was detected, but that would disregard the extrapolation. That disagrees with the data I've found.

However, the third option, that I have observed in one video of the Viper's radar (can't find any videos of the Hornet's), is to have the trackfile be extrapolated in its current bin, and once the target is detected in the next bin, the trackfile jumps to the center of that bin and begins its extrapolated movement there. That way, you only have jumps when the target enters another bin, but a smooth presentation otherwise. This might be the best of both worlds, as it leans towards the side of caution. Ultimately though, I've found no public info other than "the MC extrapolates between detections to give a smooth target presentation".

NB. The same behavior happens in MPRF, but is harder to see, because the MPRF bins are smaller.

Just checked it, it works fine. Only the F/R needle is being used, since there's only one tank. Make sure you're not starting a mission with reduced internal fuel (I noticed that the jet started with 50% internal fuel in some of my missions without me changing it in the ME, so it might be that). The centerline tank's fuel will transfer to your internal tank pretty quickly.

This is correct behavior. VS is a legacy mode that's incompatible with MSI, so it's not available via the pushbutton rotation.

Yes, all steps look correct. As long as you remember to select TOO1 for each station, launch from each station, then change each station to TOO2, and launch, you should be able to hit all eight targets.
(Correct on the QTY use as well: QTY will just allow you to drop from multiple stations, the weapons will still go to their respective targets.)

The default starting point of the system is INTL. Most times, you want to switch to MPRF, so that comes after.

It's less common to be in HPRF only, and then switch to MPRF.

The bricks are still there, but may be hard to see over the terrain video. The terrain showing in GMT and SEA without INTL being selected, is a reported bug that only occurs in MT.

You can switch to TWS, same as before, by using OSB 4. You don't need to press the DDI button either, you can switch by hovering over the radar mode (RWS) with the TDC. It'll expand the list, and you can select TWS from there.

This is indeed part of the damage model. The Hornet has two Digital Data Computers or Mission Computers (MC), and they control different functions. MC1 controls the navigation functions, while MC2 controls the weapons delivery calculations, associated data processing etc. Each computer offers limited backup functionality for the other.

Since your MC1 failed, it's normal that navigation data became invalid, while other stuff worked. Also, the HUD system wasn't damaged, and thus was still working.

Sometimes it's possible to restore some of the lost functionality by using the MC1 OFF/MC2 OFF switches, located in the back of the left console. This will attempt to pass over the work to the remaining computer, if it's included in the latter's backup subroutines.

If this is about the Velocity Vector showing this behavior when outside of the HUD boundaries, it's fixed internally.

If the problem appears while it's inside the HUD boundary, then it's a new bug.

2) Yes, you need to drop a WP on Echo. If you acquire it visually (or via the FLIR or Radar), you can also designate it and instantly drop a MK (Markpoint) on it, which is much faster.

You can then either create an Offset with bearing and Range or just set up a courseline and anchor using that. Keep in mind that the Offset symbol drifts on the SA page (reported bug), so use the HSI for position keeping.

3) Keyhole CAS is complicated, no other way around it. It also takes us a while until bombs are delivered, in my group. A couple of points, the situation is unlikely to change between successive runs, so it's fast to adjust to the next target. And you can already start taking the 9-line on the way there, if time is of the essence. I don't know how it would go in a real world situation, but I'm guessing the JTAC/AFAC would handle available assets according to the situation.

ACM modes are range gated. Targets can be detected, but they are rejected beyond a certain range, since the point of ACM is to focus on nearby targets.

IAMs will only accept coordinates given in DDMMSS.ss format, currently.

If you want to display all of the other coordinates in the aircraft in that format, you need to go to HSI->DATA->A/C and toggle the LATLN format option, located next to OSB 15.

IIRC I remember someone from ED saying that it was normal. It's there to draw your attention to the fact that TACAN and MIDS (same knob) are off.

Check your radar elevation, your radar is looking way too high.
On your radar cursor, you can see the numbers 56 and 67; these represent the lower and upper altitude coverage (in thousands of feet) of your radar pattern, at that range.
Also check the small, blue, horizontal marks and the sideways T symbol on the left side; the marks represent vertical offset, with the larger, central mark representing the horizon (so, your altitude).
You'll see that you're at 43k ft, while both targets are a bit below you. You can also see that you're scanning above you (56-67) and the T caret is above the horizon.
What you need to do is lower the radar elevation, so that you're actually scanning the altitude your targets are located in (in that case, slightly below you). Remember that your radar scan pattern widens as range increases, so you might need to re-adjust radar elevation as you get closer.
After you bug or lock a target with TMS Up, the radar will attempt to automatically adjust its scan pattern to maintain the track of the target.
Cheers

You can place down an A/G designation with selected JDAMs just fine. What's the issue? If you want to do it via the HMD/HUD, you need to be in A/G mode.

The current JDAM target will still be displayed separately as a diamond, if it's different than your current A/G designation.

You can also select other A/G weapons, while leaving the JDAMs boxed. They only lose power if you explicitly de-select them, but you can select another weapon and de-select it to return to the JDAMs.

Your cockpit seems set up correctly, but you're outside of the detection range of these air defense units. The ZSU-23-4, for example, will only show up on the RWR when it's tracking you, which it'll only do if you're close enough.

I start from cold and dark all the time and I don't have your issue.

If you determine that the above is not the solution, post a track of a small mission, so we can see what exactly is happening.

The POWER button on the THREAT WARNING AUX panel. Left of the CMDS panel, left side.

IIRC the RWR should have a knob near it.

As for EHSI, you need to press the CRS knob in (click it), and then rotate it.

Try unboxing ALG (Automatic Level & Gain) and adjusting the Level and Gain values yourself. As soon as you unbox ALG, you'll get the LG option next to OSB1, click it and you'll be able to adjust level and gain values using OSBs 2/3 and 4/5 (they'll replace ZOOM and FOCS).
 
You can also play with the DDI contrast knob and see if it helps, in addition to adjusting Level and Gain.

Cage/uncage works now.

The radar will attempt to reacquire the L&S, by extrapolating its range and velocity and looking for a contact that matches the extrapolation (I'm sure the procedure is more complicated than that, but this is the idea) for a period of time. And to answer your question regarding acquiring the wrong target, it's possible, if the two aircraft are flying with a very similar velocities and are very close to each other. Remember that the radar has a limit to its resolution.

1LOOK RAID doesn't need to be enabled for Memory mode to do its thing, although I suspect that it might increase the chance of reacquiring the wrong target, but that's more of an empirical understanding for me, right now (I don't know enough about what the actual wave changes between STT and RAID are, so I'd rather not speculate). It might increase the chance of reacquiring *a* target.

You're correct in saying that the pilot will need additional information to judge whether the target is friendly or not. You can interrogate the L&S and get IFF and NCTR info, which should help differentiate the aircraft.

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.