Tholozor

FIX can also be used on the ground. You can create a waypoint on your actual position and update via overfly. Refueling/rearming shouldn't require you to realign your INS.

Also, another point to consider is that MSI processing stops in A/G mode, and you might want the radar available for AGR.

Have you tried using the FIX update methods?

Yea, the external tanks will only fill the same amount that's missing from the internal tanks (i.e. the externals will stop once the internals are full).

With LGBs loaded and selected, pressing PB4 on the STORES page (which is blank) opens an empty MFUZ selection menu. The only option is 'OFF,' but some PBs seem to think they're valid selections. Ultimately the blank option on PB4 just shouldn't do anything. LGB_MFUZ.trk

TMS Up with FCR as SOI to lock.

PP targets can only be set per pylon. If you have 2 JDAMs on one station, you'll have to set multiple PP targets (PP1, PP2, etc) and step to them manually before release.

Assign the TDC to the Maverick display.

Assigning the TDC to the HUD also assigns it to the HMD. With the TDC assigned to the HUD, the HMD should automatically have the dashed reticle (unless a TGT is already designated). You can't get the dashed reticle in the HMD while a TGT designation exists.

This is reported:

HSI wind is already reported:

From the early access guide on page 66:

Exactly. The missile doesn't have to cover the range at which you fire it: it has to cover the range needed to intercept.

If I had to guess, some HSI functions may come with the 'full INS simulation' item on the roadmap, such as the UPDT functions.

IIRC, it's 3 overlapping symbols: - HMCS boresight cross. - Steerpoint diamond (usually centered if none exist in the computer). - Cross through the steerpoint diamond when the steerpoint isn't visible within the HMCS field of view (would usually be pegged to the edge of the display in the direction of the steerpoint).

@Bucketnate Do you have Easy Comms turned on or off in your settings?

It's possible that may be to avoid copyright, same with many of the landmark buildings on the Nevada map?

The "issue" is that the AI pilot doesn't use force trim, and is constantly holding the controls in the desired position, so that when you return to the pilot seat, your controls are reset to center. You can overcome this by turning off 'Automatic AI Handover' in the Special options for the 64, which will prevent the AI from taking flight controls until you manually command handover.

Cant watch the track at this moment, but did you check the knobs on the volume panel?

And again, I ask what benefit is it to put the steering dot locked to the TD box? It would literally be providing you wrong information. If the target is outside the confines of the HUD to the point where you can't see it in your peripheral, the position of the steering dot won't even make a matter until you bring the nose around since you're already off-bore (and if you're close enough for 9X, then the steering dot is practically irrelevant for a HOBS shot).

Why not just ignore the dot? Having it pegged to the center of the TD box wasn't providing any any relevant information to begin with, so what's the difference?

Correct, the delay doubles as a safety feature plus missile-ownship data.

From my own testing this can happen to both pods. Not sure if this is an issue with gimbal maximum rate or maximum roll limits. Tracks attached. ATFLIR_GimbalRoll.trk LITENING_GimbalRoll.trk

It's not just a 'butterfinger' feature, the launch authorization delay also uploads target parameters to the missile.

The launch delay is intentional as a launch authorization to prevent accidental firing.