Tholozor

If they aren't yet, you can probably bet they're going to start looking into it.

Already reported:

Not possible without injecting waypoints into a sequence.

There's actually 60 waypoints (0 through 59). Waypoint 59 only auto-populates with the bullseye data, but can be edited. As stated above, a sequence can only have 15 total.

Can't watch the track at work, but did you ensure the launch bar was retracted?

The coordinates provided to you were in precise DMS (DD°MM'SS.ss"), the Hornet's default coordinate format is DDM (DD°MM.mmmm' if set to PRECISE, otherwise only MM.mm'). Precise DMS is entered with 6 digits (DD°MM'SS") for the first set, then the decimal seconds for the second set (.ss"). Precise DDM is entered with 4 digits (DD°MM') for the first set, then the decimal minutes for the second set (.mmmm').

Totally possible. Textures can reference different folders in Saved Games or in the core installation. My VFA-136 livery (link in my signature) does this with a shared folder where all textures are stored, and the actual liveries are just description.lua files that assemble them. The syntax in the description.lua is the key. You can't just put in the name of the other texture, because it's only going to either look in the core installation textures (note: not livery folders) or the individual folder of the custom livery to look for it; it needs a file path if the texture is in another folder or archive. Here's an example for the Hornet's fuel tank. Normally, it would look something like this: {"FPU_8A", 0, "FPU_8A_Custom", false}; If we want to look for a texture in another custom folder, it looks like this: {"FPU_8A", 0, "../Custom Folder/FPU_8A_Custom_Elsewhere", false}; The same can be done for core installation livery folders/archives, so you can re-use textures present in core liveries without having to double-up your files. Here's an example for the normal/bump map for the F-16 that's calling the one present in the 36th FS folder in the core installation: {"F16_bl50_Main_2", 1, "$LIVERIES/36th_Fighter_Squadron/f16_bl50_main_2_normal"}; In the OP's example, the description (for Livery 2, 3, or 4) would need to look something like this to reference a texture in the Livery 1 folder: {"f18c1", 0 ,"../White Hornet Livery 1/F18C_1_ExampleWhite_ONE_Diff", false};

IIRC the shoot cue will come up when the steering dot is inside the ASE circle and the target is inside Rmax, need to double-check.

Correct. Both MSL OVRD and DGFT are each considered their own master modes, independent of the others, and the MFDs can be configured as-desired.

If this is on the Syria map, it's a known issue.

Used to be possible, but was changed a few months back.

As far as the WYPT/TGT thing goes, WYPT indication always switches to TGT when a designation exists on the HSI/SA pages, and removes the WPDSG option until undesignated.

Also, early warning radars operate at frequency bands too low for the HARM's seeker to detect, so keep that in mind regarding what target you plan to engage.

Short press and long press just define the amount of time the command is held. You absolutely can keep using your keyboard or current coolie hat binds on your stick (or rebind them to whatever you want), you just have to hold that command for a longer amount if time to register a Long command.

The antennas are a slightly different regarding the bands in the F-16, but operate on the same principle. The upper antenna has a filter in order to prevent TACAN/AIFF band interference, which includes TACAN channels 1-13 and 59-73. DME should be unavailable in this range unless the aircraft is roughly within 5 miles of the station (provided the upper antenna is in use). Both antennas have L16/AIFF band notch filters to prevent interference, and the system should be defaulting the lower antenna for TACAN use. L16 transceiving will operate off both antennas, except during AIFF interrogation, which filters the upper antenna. If for any reason a failure occurs in the filter for the lower antenna, L16/TACAN operation will automatically move to the upper antenna, and provide an associated PFL error.

Only on the F-15E for the year this F-16 is representing.

Can't check the track or miz at work, but did you ensure the 'Unrestricted SATNAV' option was disabled?

Estimated fuel on arrival is displayed on the FPAS page and HSI under the WYPT or TCN data block when Mach is below 0.9. Don't think there's really a way to know the fuel burn in the editor.

Sounds more like precise DMS where you put in the initial 6-digit DMS, hit enter, then input the decimal seconds.

The original implementation was incorrect. The only cursor-following mode is SPOT.

Make sure you're inputting 10-digit coordinates for precise grid.

If the MAP option is enabled, and the HSI/SA page set to a range which the color map should display, automatic brightness control is always enabled.

What are your computer specs?

Check your elevation control if it has an axis bound to it.

The CHK SEAT caution will only trigger with the seat not armed when the right throttle is at MIL or above, and weight-on-wheels.