Tholozor

The GAIN ORIDE switch is used to maintain predictable controllability in the event of AoA sensor or pitot-static failure (not necessarily FCS failure). Depending on the position of the flaps switch, it sets control surfaces to predetermined, fixed values to improve handling under specific conditions.

What's your aircraft's gross weight? George has to respect the torque limits.

Already reported:

In agreement with the above post; user error. The CODE option on the STORES page doesn't change the actual laser code anymore. IRL, these are set physically on the bomb's guidance unit with a screwdriver. In the case of DCS, this would be set either in the mission editor or in the re-arming menu. The code choice is also in error, as 1438 is not a valid code for Paveway II series LGBs (GBU-10, -12, and -16). The second digit can only be 5, 6 or 7.

We'll probably need a track replay so we can see your steps to help diagnose.

A bug report for this already exists here:

The LITENING pod has had IR laser capability via the MARK option for quite some time, but I agree, the beam shouldn't be visible outside the aperture of the NVGs.

Early Access Guide page 457

Already reported:

CZ should also be available on the FCR and HSD pages.

Already planned:

Some part of this is also that specific F-16 livery (152d FS) has no mipmaps, leading to textures appearing 'crunchy.' A number of F-16 liveries don't have mipmaps.

The main problem in the first post is that you're comparing the new M1A2 SEPv3 model to the replaced/updated M1A2 model. The SEPv3 has the CROWS turret for the commander's .50 and the shield for the loader's M240. The regular M1A2 model doesn't have those and looks more like the one in the first comparison screenshot.

The folded fins problem is already reported: Regarding the missile, the 5V55 is correct for the S-300PS (SA-10B). AFAIK the 48N6 would be used by the S-300PM-1 or PMU-1 (SA-20).

It was discussed in detail in this mini-update:

This isn't a Hornet-specific issue:

@beacon Check the Autopage option in the ASE settings.

Per the title, if the radar is in STT on a trackfile, the act of assigning the TDC to the ATTK display commands the radar into AACQ. This only occurs if the ATTK format is on the right DDI. TDC will swap displays normally if the ATTK format is on the left DDI. TDC_ATTK_AACQ.trk

Looking at this a little closer, there's definitely an error regarding the fuel slider and the actual fuel level when external fuel tanks are involved. In these screenshots, you can see in the initial setup the aircraft's fuel level is set at 50% (cold start, de-fueled from 100% and on ground power). After the installation of the centerline fuel tank, the internal fuel level is still the same, yet the fuel slider has increased to 71%, leading the rearming menu (after the rearm is complete) to read an increase in weight by an amount approximately double the amount of the external fuel tank.

That's because his aircraft's actual internal fuel (in the screenshots in the linked post, specifically) was less than 100% (I broke this down as well in the second half of my linked post). Regarding the pylons, some OFPs have stores management codes for them. I'm not sure whether or not it applies to this version if the weapons insertion panel behind door 14R needs the codes or not.

That chart is out-of-date, JDAMs shouldn't be able to be configured with M904/M905 mechanical fuzes anymore.

The rearming menu doesn't take the wing and centerline pylon weights into account (although it does in the editor). I did a breakdown over here:

If you're using R/BL mode, the SEEK setting defines the range from the TGT point the Harpoon seeker will go active and start looking for contacts (page 377 of the DCS manual): - SML: 10km - MED: 20km - LRG: 30km

All bombs of the same type must have the same fuze(s), you can't mix them. The armament computer on the Hornet has specific codes that the stores system reads when ordnance is loaded that tells it what kind of weapon it is and what fuze(s) it's equipped with (if applicable). This controls what options will be available on the STORES page. If the stores system detects that more than one of the same kind of weapon is loaded with mis-matched fuzes (or any invalid weapon code was entered), it will throw a LOAD (crossed out) advisory, indicating the fuze mis-match.

There's definitely something in the default textures giving it a blue tint, even with atmospheric conditions taken out of the equation. This screenshot was taken with the default livery in the modelViewer: