Tholozor

Move the cursor to the edge of the display then bump it. It's a little finnicky on if there's any vertical movement, so you may need a deadzone to ensure it's purely horizontal motion.

Only very specific variants ever had AIM-7 (notably the Block 15 ADF in U.S. service and the Iraqi Block 52s).

That vacuum sound isn't the engine, IIRC it's the ECS blower.

Not a bug, the Advisory line cuts off information on that part of the screen. The left DDI is not intended to be used for data-sensitive pages like SA or ATTK RDR.

Make sure you're using the binding for second stage trigger to launch A/A weapons, and hold the trigger down.

Also ensure you set flaps to HALF for takeoff. If you lift off with flaps in AUTO is messes with the FCS logic and you'll have to switch flaps out of AUTO and back to reset it.

The model of the pilot in the seat is part of the aircraft's model itself. The textures for it are in the same directory as the aircraft textures in CoreMods.

@escaner it's the same thing. With a Maverick or HARM selected, the FOV/RAID button does not operate for the targeting pod (short press or long press). The weapon takes priority control over the entire switch.

Not a bug:

IIRC, FOV can't be changed once a target is locked.

Can't watch the track right now, but bid you get "cleared hot" from the JTAC?

10 minutes is just the maximum alignment time for GPS weapons, they should be ready to go after about 2:30.

Do you have any mods installed like the F-16I Sufa?

Exactly, the HTS isn't a spot-on targeting system, it uses angular signal reception to calculate approximate emitter positions. Flying directly towards an emitter reduces the pod's ability to make better calculations. From the early access manual, page 285:

Go to WPN -> UTIL and verify the LASER is armed (solid circle).

What parameters are you dropping the bomb from? Remember that the auto lase timer is the time-to-impact at which the laser will begin firing, so if the TTI is greater than the auto lase setting, it won't fire on release.

Are you talking about A/A gun, or A/G gun?

Don't worry about WPNS DEGD (Weapons Degraded) on the BIT page, those aren't fully implemented yet; you can ignore it. The NO WPYTS cue can only present itself during a carrier alignment, either by radio (RF) or using a cable (CBL) to align the aircraft based on the alignment from the ship and the aircraft's position relative to it. During the INS platform leveling, the aircraft can receive waypoints (up to 10) from the ship. If no waypoints have been received, you get the NO WYPTS cue on the HSI. Receiving waypoints isn't required for alignment.

The XMT option on the HSD is only relevant for transmitting data across the selected network (e.g. sending a steerpoint with Comm Switch IFF IN Long). It doesn't control anything regarding receiving datalink info. As far as I've seen, the main issues that crop up regarding non-functional DL info is the MIDS LVT knob not being on, or an incorrect/interrupted alignment.

The INS is already aligned in a hot start, there's no need to move the knob to anything.

Looks like an Offset Aimpoint. Did you perhaps cycle STP or TGT to OA1 or OA2?

The implementation of LITENING is pre-MSI; ATFLIR would have that type of functionality, but only in A/A master mode, as that's the only mode in which AZ/EL is available.

Post a track then, because it all seems fine on my end. George will make a call based on the current speed vs. the target speed, not the target speed vs. the previous target speed.

The USAF -1 for the Block 50 has the label on the panel, however that's the typical configuration (Fig. 1-3 on page 1-16, and Fig. 1-68 on page 1-154 for reference).

I think George is reading the aircraft's current parameters and choosing a voice line to represent the direction he plans to go. So say you're in a hover and set for 70kts, then bump it down to 40kts, he'll still say "speeding up" if he hasn't reached a point where the opposite voice line would apply. Same seems to apply to altitude commands.