Tholozor

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:

Oh, my mistake, I thought you were referring to the Common Configuration Implementation Program.

@shaji Something is definitely wrong in that video, as the JDAM shouldn't have access to the M904 nose fuze anymore. AFAIK, JDAMs in reality have never been assembled with mechanical fuzes in the nose, only plugs or the DSU-33 airburst sensor. The rearming menu should prevent incompatible fuzes from being selected.

The CCIP upgrade happened in two phases, Phase I upgrades for Block 50/52 started being redelivered roughly circa 2002, with Phase II upgrades being redelivered roughly circa 2004. IIRC, Block 40/42 started redelivering roughly circa 2006 directly from Phase II.

Page 257 of the Early Access Guide

New pilot model was introduced a few patches ago.

Please post a track so we can take a look for ourselves, the video doesn't really have any tells what the problem could be. Regarding the TGP, press STBY in the top-left corner to select another mode (A-A or A-G).

JPF page will be under the MSN page for the selected weapon in the bottom-left corner.

Only one I could find in the User Files: https://www.digitalcombatsimulator.com/en/files/3318043/

Keep in mind that the data card functionality is something that is being developed as a core function not just for the Hornet.

In the Mission Editor, in the aircraft's Additional Properties tab, you can change if the pilot is equipped with the JHMCS, HGU-68 ('Not installed' option) or NVGs (attached to the HGU-68). The JHMCS and NVGs can be equipped via the ground crew menu, but currently can't be removed back to the normal helmet.

I apologize, my original description regarding the Mk-122 safety switch slightly off. When used in conjunction with the the FMU-139, the Mk-122 switch typically has two connections; an arming wire and a coaxial power cable. The arming wire is typically a few inches shorter than the coaxial cable, so it's pulled first, which closes a DC circuit inside the safety switch and permitting the capacitors inside to be charged to power the fuze (basically the weapon will not be charged until release is commanded). If EFUZ is set to OFF, no power will be applied and the weapon will dud. When used in conjunction with the FMU-152, the arming wire for the Mk-122 is not required (but, can still be used as a redundant safety), as the fuze is completely digital (with faceplate backup settings). When weapon release is commanded, the stores system sends a coded arming pulse that charges the capacitors, arms the fuze, and sets the arm/function delay. The stores system in the Hornet has specific codes used for each station set by the ordnance crews that tell the aircraft what weapon it has loaded and how the weapon was assembled so it knows what to do with it (this is done via the Weapons Insertion Panel on the armament computer inside door 14R). For a Mk-82, it depends on how the bomb was assembled. Assuming it's been assembled with an M904E4 fuze in the nose, and an M905 fuze in the tail, then: Setting MFUZ to NOSE, and EFUZ to OFF should result in detonation based on the M904E4 setting. Setting MFUZ to OFF, and EFUZ to INST should result in detonation based on the M905 setting.