Tholozor

Pre-Programmed missions would be part of the data cartridge functionality (MUMI).

The A-10 and F-16 both use a similar SPI logic, the Hornet does not. In the 18, the FLIR pod must be the driving source of the TGT designation (denoted by a 'FLIR' mnemonic in the HUD), primarily through SCENE or AUTO tracking modes.

The Maverick can slave to the SPI in the system, but it can't move the SPI unless you're using VIS mode where you have a "pseudo-SPI" to slave the seeker based on where the aircraft is pointed. In PRE mode, the Maverick slaves to the SPI (which is basically the same location as the steerpoint, provided the slew deltas are Cursor Zeroed). If you're starting the aircraft cold and dark, the Maverick seekers needs to be boresighted as well so that they're aligned properly (not required for a hot start).

According to ↓this↓ thread, the 9E has all the coding in place, and they're just waiting for the 3D model for it to be implemented.

When you move the TGP around in the F-16, it introduces a slew delta (change) into the entire steerpoint system. To reset this, you must perform a Cursor Zero (CZ) command.

Should work for JDAM and JSOW.

TOO1 and TOO2 must be switched manually. Because you set all the stations on TOO2, none of them went for TOO1. After you drop the first 4, switch all the stations to the other TOO mission and then pickle.

Probably related to the ARI bug?

TOO1 and TOO2 are individual to each weapon station (i.e. TOO1 on STA2 is different from TOO1 on STA8). This permits you to have up to 8 total individual TOO targets across all 4 stations, as the Hornet's maximum JDAM load is 8 total (2 for each station if loaded on BRU-55). Stepping to another station will invoke that station's last selected TOO mission. As an example, let's say you have 4 JDAMs loaded on BRU-55 racks on Stations 3 and 7, and you have 4 targets you want to engage. You might designate them like this: - TOO1 on Station 7 on target 1 - TOO2 on Station 7 on target 2 - TOO1 on Station 3 on target 3 - TOO2 on Station 3 on target 4 Or you could do it like this: - TOO1 on Station 3 on target 1 - TOO1 on Station 7 on target 2 - TOO2 on Station 3 on target 3 - TOO2 on Station 7 on target 4 Since the system doesn't "assign" TOO missions to individual weapons mounted on the rack, you would have to manually switch between TOO1 and TOO2 for each station between drops, otherwise *both* weapons on the rack would release on the same TOO mission. Personally, I prefer to use the second method of assigning targets between TOO1 and TOO2 on each station, as the active station will automatically step to the next one when a weapon is released. This way I can release all the weapons on their TOO1 missions first, then switch them to TOO2 as it steps back through the release order.

You can select the FMU-140 on the CBU-99 version of the Rockeye.

Turn down the gain, set the MPCD to night mode and adjust the contrast.

Did you also turn on Link16 from the second DL menu on the UFC?

This version of the Hornet has TACAN and Link16 embedded in the same MIDS terminal, as opposed to older models that had a separate AN/ARN-118 TACAN module.

Correct, but since Bob is "in control" he takes care of any turn coordination or thrust lever adjustments to keep the helicopter stable.

If you're not providing any more lateral input to the stick, Bob will interpret that as "don't turn." Think of it like dual-linked controls in the real helicopter where they move together. You're "guiding" Bob as to what you want him to do by moving the stick and thrust lever.

What do you mean by "it won't let me"? What weapon are you using? Do you have a track we can look at?

The tail rotor/crabbing is already a known WIP issue:

Already reported:

The Weapon Insertion Panel uses alpha-numeric codes to tell the SMS what weapon is loaded with what fuze configuration. The code for the nose well is different if the weapon is equipped with a DSU-33 or not.

The M240H, which is the specific version equipped on this CH-47, does not include a guard on the barrel.

The good chunk of Block 50 F-16s in U.S. service were built in the early 90s. There were only a small handful of 00- and 01- serials that were built for U.S. service (about 4~5 for 2000 and about 10 for 2001). Compared to this, the amount of U.S. Block 50s built in the fiscal year for 1991 attribute to about a little over 90 airframes. That's not to say that the 00- and 01- serials are "invalid" (especially considering the original default livery for the DCS F-16 was serial 01-7052). It's just that the 91- serials for U.S. Block 50s are much more common.

You would probably have to either find a custom livery that already changes the fiscal year of the serial number or make your own; that part of the decal isn't dynamic.

Is the pod still in standby mode (STBY)? Top-left OSB to change the pod's mode (STBY, A-A, A-G).

@darkman222

If you're referring to 'YF1497,' that's the MGRS grid.