Tholozor

New fuze options are WIP and can currently be ignored, but basically: - M904/M905 are old-school mechanical impact fuzes. - FMU-139 is an electro-mechanical fuze installed in the tail. - FMU-152 is the Joint Programmable Fuze (JPF) installed in the tail that permits cockpit programming.

Never named the door gunners, but my copilot is Bob.

Radar manual.

The radar elevation display on the cursor in VS mode is calculated if the range scale were at 80nmi (according to the -742).

WIP while new fuze options are being made.

Incorrect grid zone designator (GZD). 31N would be near N0°E0°. GZDs are very large, and the one that encompasses most of the PG map is 40R (next closest 'CP' grid square would be hundreds of miles away). You can check the GZDs on the F10 map and switching the coordinate format to MGRS.

This has been requested before:

Not doing anything wrong, this is by design. With a TGT designated, weapon release indication will always switch to AUTO, regardless of STORES setting.

The version of the F-16 that ED is modeling does not have EGI.

The manual is present in your DCS installation directory. Look under Mods\aircraft\FA-18C\Doc. Latest revision is from this March, so a few things may have changed since then.

That VORTAC should not exist. Sphinx Intl. and Cairo West share the same TACAN.

Better to ask for help in the SRS thread:

AFAIK, MWS-compatible pylons were introduced with MLU M3 (maybe M2) on EPAF F-16s, so somewhere around the early-to-mid-2000s(?), possibly late-90s, but definitely not used in USAF service for this block/timeframe. Pylon-Integrated Dispenser System pylons (PIDS) were originally only store racks with chaff dispensers built-in. Once they were upgraded to carry IAMs, they also added provisions to mount MWS sensors, but didn't come standard (PIDSU), and could eventually have MWS installed on them (PIDSU+, referred to as PIDS+ in the SMS). Electronic Countermeasure Integrated Pylon System (ECIPS, or referred to as MAUQ in the SMS) pylons were originally only store racks with integrated jammers. Same as the PIDS pylons, they were also upgraded for IAMs without the MWS (ECIPSU), and could also have them installed (ECIPSU+, referred to as MAUQ+ in the SMS). The article @VarZat linked also has a similar breakdown of the variants.

PP missions can loaded via MUMI, but can also be created/edited from the cockpit, nothing prevents you from doing that (there's just a small handful of things that can't be created/edited from the cockpit, such as the name of the mission). I should've specified in my previous post that we currently can't make PP missions outside of the cockpit. Due to inherent inaccuracies of TOO coordinate generation IRL (that aren't simulated in DCS, such as Dilution of Precision, and User Equivalent Range Error), pilots are recommended to create PP missions when passed coordinates from ground controllers for precision strikes.

Already reported:

Check your axis controls for the MAN RNG knob and see if it has something bound to it.

Already reported:

Currently we don't have a way to set up PP missions in the Hornet for JDAM/JSOW/SLAM/HARM, as these would be loaded from MUMI (data cartridge). Designating a waypoint to be used as a target would be TOO, because the aircraft has no way to know what the waypoint is for, it's just a waypoint to the computer. Once we have the ability to make actual pre-planned target points, co-locating waypoints won't be necessary. However, if the context is that you're using a waypoint to mark a target for non-smart weapons like GP bombs or PW2s, you can say that waypoint is your TGT point, and designate it as-such in your waypoint sequence, but it's not necessarily the same as a PP mission.

Here's what I found from my own tests using ground power to keep the internal fuel level full for all tests (displayed as 10,840 lbs internal on the IFEI @ 20°C, 29.92 inHg), full gun ammo on HEI-T rounds: - A slick Hornet with the wing/centerline pylons removed: CHKLST shows A/C WT as 36,396 lbs and rearming menu showing 36,229 lbs. My presumption is that this ~167 lbs discrepancy is accounted for as the weight of the pilot (LAU-116 ejectors on stations 4 and 6 would attribute to ~130 lbs together, and LAU-7 rail launchers on the wingtips would account for ~180 lbs together, so neither of these seem likely). - Adding the centerline pylon (SUU-62) does not change the weight on the rearming menu (stays at 36,229 lbs). A/C WT increases to 36,535 lbs (SUU-62 weighs ~139 lbs, so A/C WT is correct). - Adding all 4 wing pylons (SUU-63) does not change the weight on the rearming menu (stays at 36,229 lbs). A/C WT increases to 37,775 lbs (each SUU-63 weighs ~310 lbs * 4 is ~1,240 lbs. 37,775 - 36,535 = 1,240. A/C WT is again correct). Right off the bat, any payload that does not remove any pylons will automatically have a difference of 1,379 lbs between the rearming menu and the A/C WT, plus the 167 lbs discrepancy. Adding ATFLIR has the A/C WT properly accounting for the removal of the LAU-116 on station 4. The A/C WT will decrease by 65 lbs when the pod is initially added and the LAU-116 removed, then increased by 430 lbs once the rearm is complete. However, the rearming menu does not account for the removal of the LAU-116, and only shows the difference of the weight of the ATFLIR itself. External fuel tanks are accounted for properly by both rearming menu and A/C WT calculation. A full FPU-8 tank accounts for ~2,535 lbs (~2,244 lbs for JP-8, if calculating at 6.8 lbs per gallon, plus 290 lbs for the tank itself). The LAU-115+LAU-127 launcher combo racks for AIM-120/AIM-9 are also accounted for correctly (~357 lbs for each AIM-120, ~120 lbs for the LAU-115C/A, and ~191 lbs for both LAU-127A/A attached to the side). The only issue I see in the screenshots lies in your internal fuel weight. The rearming menu sliders are set to 100%, but the internal fuel level is below that. Given the above regarding the weight discrepancies between the rearming menu and the A/C WT on the CHKLST page, we can determine if the jet is calculating correctly. Using the screenshot of the aircraft loaded with AIM-120s and three external tanks, internal fuel at ~7,530 lbs: - Starting at 46,983 lbs on the rearming menu, we add the weight of the discrepancy between the menu weight and A/C WT if the aircraft had nothing loaded and pylons removed (+167). - We add the weight of the SUU-62 centerline pylon (+139). - We add the weight of the four SUU-63 wing pylons (+1,240) - We subtract the weight of the missing internal fuel (-3,310) This gives us a total of 45,219 lbs, only ~12 lbs off from the A/C WT. Same thing applies to the second screenshot with AGM-65s: - Starting at 43,096 lbs on the rearming menu, adding the discrepancy (+167). - Centerline pylon (+139) - Wing pylons (+1240) - Removed LAU-116 for the ATFLIR on station 4 (-65) - Subtract the missing fuel (-1130) Total of 43,447 lbs, only ~3 lbs off the A/C WT. I'd say CHKLST is doing a better job than the rearming menu.

Already reported:

The first waypoint is usually listed as 'SP' in the editor, presumably as Start/Spawn Point. You can also consider it as waypoint 0.

Start time can be done with the SP waypoint, or by setting the unit to Uncontrolled, adding a triggered action to Start, then triggering the action at a specified time. I believe the Orbit command has a duration setting, but I can't check at work.

VS is not entered via the pushbutton selection rotary (Wags' video had it incorrectly implemented, which was correct for older OFPs prior to MSI). Hover the TDC cursor over the radar mode and select VS with TDC Depress.

A track would help us diagnose.

What are your hardware specs?