Tholozor

From this mini-update: This might include the hydraulic/flaps light logic.

Are they set to Hidden maybe? I see the 'Show Hidden Units' option is unticked.

So this particular instance of ED not making an updated video/post detailing a particular change that multiple community members and ED have basically said (via the tag on the thread) the current implementation is correct completely negates all arguments? https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.7.14.24228/ Sorry, but the burden of proof is on you now.

That was covered in my reply, depressing the TDC will exit Spotlight mode. The documentation I've read makes no distinction if the TDC is depressed over a trackfile or not.

I think the 'correct as is' tag on this thread kind of answers the question.

AFAIK, Spotlight is entered from A/A master mode, but I'll need to check the description in the manual (not sure if the lexicon specifies A/A master mode or A/A radar mode). Spotlight will be exited (and should return to the previous search mode) by pressing NWS/Undesignate, depressing the TDC, or moving the TDC to another display.

That was the old QTY logic and was incorrect, it's been changed since then.

Truly pre-planned missions can have much more functional data programmed into the mission than the pilot is capable of doing in the cockpit as well. The programming software used to write the missions for the memory unit provides mission planners with a ton of options for making optimal attacks. Missions can be named, have pre-determined TOTs, terminal settings, JPF settings, and can generate a pre-planned IZLAR for use in determining a launch point based on specified quantity release parameters and terminal settings.

The logic behind QTY release is working as intended based on documentation I've read, it's purpose is to provide the pilot the ability to release multiple JDAMs on multiple targets all at once. It's up to the pilot to select what each JDAM is targeting for the QTY release. Once the dynamic intersection IZLAR is implemented, QTY release will be more efficient on multiple targets.

Here's my observation from watching the track (time will be referenced off the IFEI clock): @09:03:25 - STA8 PP2 in the briefing is input as STA8 PP1 @09:04:27 - STA2 PP2 in the briefing is input as STA2 PP1 @09:06:15 - STA8 PP1 is corrected to STA8 PP1 from the briefing @09:07:20 - STA2 PP1 is corrected to STA2 PP1 from the briefing @09:09:15 - STA7 PP1 is input with incorrect LON from STA3 PP1 from the briefing @09:11:51 - STA3 PP1 is input with STA3 PP1 from the briefing @09:13:52 - STA7 PP1 LON is corrected to STA7 PP1 LON from the briefing @09:14:40 - STA8 is switched to PP2 @09:15:41 - STA8 PP2 is input with STA8 PP2 form the briefing @09:15:55 - STA2 is switched to PP2 @09:17:03 - STA2 PP2 is input with STA2 PP2 from the briefing @09:17:56 - STA7 is switched to PP2 @09:18:53 - STA7 PP2 is input with STA7 PP2 from the briefing @09:19:12 - STA3 is switched to PP2 @09:20:03 - STA3 PP2 is input with STA3 PP2 from the briefing @09:20:23 - STA8 is switched to PP1 @09:21:02 - STA2 is switched to PP1 @09:21:29 - STA7 is switched to PP1 @09:21:48 - STA3 is switched to PP1 @09:22:17 - STA8 is switched to PP2 @09:22:35 - STA2 is switched to PP2 @09:23:06 - STA7 is switched to PP2 @09:23:26 - STA3 is switched to PP2 @09:23:45 - STA8 is switched to PP1 - After this, STA2, 7 and 3 are cycled through a few times, but left on PP2 - Initial release is done with STA8 on PP1, and all other stations on PP2 - Second release is done with STA8 switched to PP2, and all other stations are still on PP2. QTY release will release the selected stations regarding their selected PP mission.

Each station has its own individual set of PP coordinates. i.e. PP1 on STA8 is not the same as PP1 on STA2. Any PP mission programmed is only applicable to the station it was programmed on.

Try assigning the TDC to the MAV display, then pickle.

There's isn't a 'waypoint up' or 'waypoint down' option on the controls; all waypoints, control measures, target points, etc. are selected either automatically through a route, or manually as a direct-to. If you have the HOCAS cursor mapped, it can be used to select the options around the bezel of the MPCDs instead of pressing the pushbuttons manually.

What kind of weapon/release mode are you using?

If you have SSAA turned on, try turning it off.

Not true, the radar can track a target based on azimuth and elevation. Range can become ambiguous: https://meteorologytraining.tpub.com/14271/css/14271_59.htm

Those F-16s are using a newer tape, you're talking about a 10-year time difference.

Home waypoint selection is only available when the FPAS is able to calculate the HOME FUEL caution, otherwise the home waypoint is crossed out and selection arrows removed (this is correct as-per the NATOPS). The HOME FUEL caution logic should not be active with weight-on-wheels, the refuel probe deployed, or for 5 seconds after a new home waypoint is selected while the logic kicks back in. "Unused" waypoints are still technically viable coordinates, as all zeroes would be the position where the equator meets the prime meridian. Since the waypoint is so far away, the FPAS loses its ability to calculate HOME FUEL, as the remaining fuel would be far below what the aircraft can carry (at least in regards to the location of the theaters available to us in DCS), and home waypoint selection becomes unavailable. One main reason why HOME FUEL is so common on landing (that I've noticed) is due to the power corrections needed to maintain a smooth glideslope. The fuel flow rate fluctuates rapidly, causing the FPAS to reassess the HOME FUEL caution constantly (depending on the home waypoint location and current fuel on board), resulting in the calculation to bounce above and below the 2,000-pound threshold, triggering the caution over and over.

Was the laser armed?

Usually, pressing WPDSG should load the TOO coordinates when the TGT designation is written for the first time (regardless if a targeting pod is loaded). With a targeting pod, TDC Depress should write the new coordinates to memory.

The TGP should perform a laser-range update of the SPI on weapon release to ensure the target point is accurate.

Do you have easy comms on or off? Are you using the correct radio keybind?

Depending on the design of the weapon, the GPS receiver may not have a clear LOS for the satellites while under the wing. So while the weapon's internal alignment may be finished, it may not have a good GPS signal. Try and make some maneuvers, that might give it a signal.

Give these a read, hostile contacts should not provide AIFF return symbology: