Jump to content

Viper Mini-Updates


Wags

Recommended Posts

  • 1 month later...
  • ED Team

 

COMING SOON

Map Used in Video: DCS: NEVADA Test and Training Range

Purchase DCS: F-16C Viper from:

In this DCS: F-16C Viper video, we’ll explore some of the new features and changes coming to the DCS Viper later this month. Our primary goal is to resolve as many of the roadmap items as possible.

I’m going to be coving a lot of different items, and you can find timestamps in the video description to find what you are most interested in.

0:00 - Intro

0:28 - Automatic Laser Designation

3:07 - CCIP Laser Ranging

5:13 - Targeting Pod Attitude Advisory Function (AFF)

7:04 - HOTAS Bombing Mode Cycle

7:40 - Manual (MAN) Bombing Mode

9:03 - ALT Release Button

9:48 - Spotlight Scan Radar Mode

10:26 - Change in CRM HOTAS Selection

11:13 - FLCS BIT Test

11:58 - AN/ALQ-131 ECM Pod

11:27 - Wing Tank Jettison

12:49 - Gun Gas Purge Door and Barrel Rotation

 

Automatic Laser Designation

First, we’ll be adding new functionality to the LASR DED page that will allow you to automatic laser designation. As you might imagine, this will be very useful for weapons like GBU-10 and -12 and will not require manual lasing using the trigger.

From LIST in the ICP, press MISC at the 0 button, and then LASR at the 5 button.

Along the bottom of the DED page, we now have the laser start time. Press down on the “dobber” switch until the option is highlighted and you can then enter the automatic laser start time in seconds before estimated time to impact between 8 and 176 seconds. After estimated weapon impact time, the laser will continue to fire for 30 seconds and then automatically shut off.

 

CCIP Laser Ranging

If in CCIP bombing mode with a targeting pod loaded, pressing the control stick trigger to the second detent will fire the laser for 30 seconds to provide precise ranging.

Note that when in CCIP mode that the TGP line of sight is slaved to the CCIP impact point.

 

Targeting Pod Attitude Advisory Function (AFF)

When the TGP is displayed on an MPD, the AFF alert will display and flash under the following conditions to alert you of an unsafe nose attitude while potentially being heads down and not paying attention.

The TGP must be displayed, you must be in air-to-ground master mode, and you must be below the set Altitude Low MSL Floor value. If those conditions are met and if roll exceeds 75-degrees or pitch exceeds -20-degrees based on the gun boresight line on the HUD, the alert will trigger.

 

HOTAS Bombing Mode Cycle

Probably the easiest way to cycle the bombing mode is to press the Nosewheel Steering/Missile Step Switch on the control stick. When pressed, it should cycle between CCIP, CCRP, and DTOS. In the current version, other modes are incorrectly included in this rotary, and will be corrected in the update.

 

Manual (MAN) Bombing Mode

Although this already available in the current Open Beta, I’d like to talk a little about it today. After selected the Air—to-Ground master mode, select MAN bombing mode by pressing OSB 2 and then MAN at OSB 16. If you were to lose your normal CCIP or CCRP bombing symbology, this can be a backup.

On the HUD Control Panel, you can set the HUD Depressible Reticle to OFF, Primary, and Standby. When set to Primary, the HUD symbology will be present, but the Depressible Reticle be the bombing sight. When set to Standby, only the Depressible Reticle will be present with MILs setting.

When Primary is used, rotate the Depressible Reticle wheel on the right side of the ICP to adjust the MILs setting. The MILs value can be seen below the airspeed table.

I’ve included some basic manual bombing profiles at the link listed in the video description.

 

ALT Release Button

In addition to the Weapon Release button on the control stick, you will be able to use the red Alternate Release button on the left auxiliary panel in the update to release weapons.

 

Spotlight Scan Radar Mode

When Range While Search or Track While Scan radar modes, a Spotlight Scan will be required to designate the target. To do so, place the radar cursor over the desired target on the FCR and press and hold the Target Management Switch up for greater than one second. This will place the radar into 10-degree azimuth and elevation scan of a small volume to rapidly build track history. For best results lead the target a tiny bit and let the radar build three to four target histories before releasing the Target Management Switch and commanding the radar track the target.

 

Change in CRM HOTAS Selection

So that it does not catch you unaware, the HOTAS command of Target Management Switch right to toggle between Range While Search and Track While Scan modes will change from holding greater than 0.5 seconds to greater than 1.0 seconds.

 

FLCS BIT Test

When performing a cold start, a real-world element is to conduct a FLCS built in test of the control systems. Once the aircraft is started, moving the BIT switch on the Flight Control Panel from OFF to BIT initiates the BIT test. You will see the light above indicate RUN and the various control surfaces of the aircraft will run through a preset series of movements. Once complete, the RUN light will extinguish, and the BIT switch will return to the OFF position.

As we watch the FLCS BIT test run, you probably noticed the AN/ALQ-131 ECM pod. Although it will behave the same as the existing AN/ALQ-184 ECM modes, the option to load the AN/ALQ-131 pod will be available.

 

Wing Tank Jettison

Another external item that we’ll talk about today is a correction to how the external wing tanks are jettisoned. Currently, when you jettison the wing wings, only the wing tanks are jettisoned and not the pylons. This was in correct, and with the update, the pylons will also be jettisoned.

 

Gun Gas Purge Door and Barrel Rotation

When the gun is fired, the gun gas purge door will now open to remove gun gasses from the gun compartment. Additionally, we’ve added an animation to the barrels of the M61 cannon.

There are many more changes coming in the next update, and we ask that you review the change log once available.

 

Manual (MAN) Bombing Table for MK-82, MK-84, and CBU-87 attached.

MAN Table.pdf

  • Like 21
  • Thanks 9
Link to comment
Share on other sites

  • 1 month later...
  • ED Team

DCS: F-16C Viper Mini-Update

Following some time off, I’d like to update you on current Viper tasks and priority tasks following those.

Current tasks include:

  • Complete external model Level of Detail (LOD) to improve performance.
  • We are now close to completing the High Drag and Low Drag ballistics and calculations for both CCIP and delayed-CCIP releases for the MK-84HD. This should also improve other general-purpose bombs.
  • The Low Altitude Drogue Delivery (LADD) is being finalized and tested.
  • Correcting some HOTAS short and long press logic. This is also true for jettisons.
  • GPS target coordinate shifting.
  • Radar SAM and DTT modes tracking retention improvement.
  • Adjustments to SPOTLIGHT mode for short press.
  • Adjustments to Track While Scan (TWS) designations.
  • Animated ECS inlets.

Following the above, priority items include:

  • Non-Cooperative Target Recognition (NCTR)
  • Tuning air-to-air performance including look-down and search to bug target delay.
  • Digital Maneuver Cue (DMC) and Loft indications.
  • Further work on Link 16 and adding air-to-air target assignments.
  • Alternate gear handle and animated tail hook.

Please note that this is not a 100% inclusive list, but rather the more important highlights.

Kind regards,

Wags

  • Like 27
  • Thanks 15
Link to comment
Share on other sites

  • 3 weeks later...
  • ED Team

DCS: F-16C Viper | Non-Cooperative Target Recognition (COMING SOON)

In this DCS: F-16C Viper video, we’ll talk about the Non-Cooperative Target Recognition, NCTR, that can be used to identify the aircraft type. As many of you are probably aware, this system compares turbine blade signatures of different engines to a database of associated aircraft types.
 
This can be a useful system to identify the aircraft at beyond visual range of up to around 25 nm. Because NCTR requires the radar to see the engine blades, there some important requirements:

First, the target nose or tail must be within 30-degrees in azimuth and elevation of your nose.
Second, the target must be within about 25 nm.
Third, you must be in Single Target Track mode.

To interrogate with IFF and NCTR at the same time, press and hold Target Management Switch Left for greater than one second. (Left Control + Left Arrow)

Let’s look at this in action.

We are STT on a high-aspect target at around 30 nm. To perform an NCTR print, hold the Target Management Switch to the left for greater than one second. When you do so, it will both perform an NCTR print on the target and perform an Identify Friend or Foe interrogation along the line of sight of the STT target.

If the target is outside the range and angle constraints, an INVL, or Invalid, message will appear on the Fire Control Radar, FCR, page. 

Now that we are 24 nm, we will perform another TMS Left Long press and we can see that the target has been identified as SU27, meaning an Su-27 fighter.

It’s important to note that because we both performed and IFF interrogation and an NCTR print, we now have two identification sources that allow the Rules of Engagement tree to identify the target as hostile, indicated as red. Meaning you will be able to identify hostile targets with only ownship systems.

  • Like 16
  • Thanks 1

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

  • ED Team

DCS: F-16C Viper | LADD Bombing Mode (COMING SOON)

 

In this DCS: F-16C Viper video, we’ll discuss the final bombing mode coming to the Viper: The Low Altitude Drogue Delivery, or LADD, bombing mode. Much like CCRP toss bombing, LADD allows low altitude toss bombing ingress attacks, but provides some unique parameter settings that are not available in CCRP toss bombing.

While certainly an interesting option, and included for the sake of completeness, I think you will find the standard CCRP toss bombing preferable. I may be incorrect, but I is my understanding that LADD is more designed for tossing airburst nuclear weapons under very defined conditions. And no, we have no plans to add nukes to DCS.

Let’s get started.

First, we’ll select AG master mode and then select LADD from the bombing mode options, note that you cannot select it from the nosewheel steering / missile step switch rotary. On the LADD SMS page, select the Control sublevel to setup the delivery.

At OSB 10 we can set the desired release angle, which defaults to 45-degrees. Let’s select it and set it to 30-degrees in this example. Next, press the LADD options at OSB 6. In the center of the page, we have three options. At the top is the Pullup Range, or PR. This defines the range at which we will initiate the pull up to the entered release angle. It defaults to 25000 feet, but for a 30-degree release angle, 40000 feet is a better choice. Unlike CCRP Toss that automatically adjusts the PR based on the release angle, you must manually set this is LADD mode. As a general rule, for release angles: use 45000 feet for 45-degrees, 40000 feet for 30-degrees, and 35000 for 20-degrees. Press Enter to save the value and move to the next selection.

Next is the desired weapon time of flight in seconds. We’ll keep the default 28 seconds and press enter.

Last is the Minimum Release Altitude, or MRA. Upon pull up, you must reach the entered altitude in feet within 5-seconds. If you take longer, the weapons will not release. This will probably be the most common reason for weapons not separated and “correct as-is” tags being added to forum posts. Given that we are at only around 500 feet, I’m going to lower the MRA from 1100 feet to 800 feet. Press enter to save the value and then Control to return to the main LADD SMS page.

Note that In the center of the page we have our release angle, pullup range, time of flight, and minimum release altitude listed. I’ll unpause now.

The target point from which the release is calculated is indicated on the HUD as the box. Fly to align the Azimuth Steering Line on the box.

As with CCRP Toss bombing, the Vertical Steering Bar and the Release cue will move to the Flight Path Marker as you near the pullup range. Unlike CCRP Toss, there is no anticipation cue indication or release scale on the HUD. As the Vertical Steering Bar and Release Cue near the Flight Path Marker, press and hold the weapon release button. Once the three symbols intersect on the HUD, the Vertical Steering Bar and Release Cue will reset up the ASL and you’ll initiate a smooth 4G pull up while maintaining the FPM on the ASL. Once the FPM is at the entered Release Angle, 30-degreees in this case, hold the FPM at the angle and wait for the Release Cue to march down the ASL to intersect the FPM and the weapon will be released automatically.

It’s important to note that LADD is probably the least accurate of all the bombing modes and bombs may fall on target, short, or long.

  • Like 10
  • Thanks 2

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 3 weeks later...
  • ED Team

Dear all,

We have made some Viper HMCS changes to correct ACM BORE HMCS behavior:

  1. Set ACM BORE mode and enable HMCS.
  2. Use view LOS to slew the HMCS boresight cross over a target.
  3. Press and hold TMS forward and the ellipse will be visible on the HMCS and the radar will slave the ACM BORE pattern to that LOS if within gimbal.
    Target should be within 10 nm.
  4. Release TMS forward and the radar will automatically attempt to snag the target as an STT, and the ellipse will be removed.

Kind regards,

Eagle Dynamics 

  • Like 7
  • Thanks 5

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 2 weeks later...
  • ED Team

Welcome to this look at some of the most important Viper changes coming this month. This will by no means be all the changes, and we suggest you review the change log for the complete list once available.

00:00 - Introduction
00:25 - Updated HMCS in ACM BORE Mode
01:44 - Removed Range to Jamming Target on HSD
02:14 - Corrected Unstable Radar Elevation on Bugged Target
02:28 - No More AIFF Range and Azimuth Indication on Non-Detected Targets
03:02 - TGP and FCR slaving with TMS Right
03:42 - MK-84 Falling Short in CCIP
04:31 - Corrected AGM-65D Handoff on Moving Targets
05:55 - Added Engine SEC Function

Used Key Commands
TMS Up: RCtrl + Up Arrow
TMS Right: RCtrl + Right Arrow
TMS Left: RCtrl + Left Arrow
TMS Down: RCtrl + Down Arrow

 

  • Like 10
  • Thanks 3

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

  • 1 month later...
  • 4 weeks later...
  • ED Team

DCS: F-16C Viper | January 2023 Update (COMING SOON)

COMING SOON

What map is this? A preview of the upcoming DCS: Sinai Map.

NOTE: Multi-Threading is enabled in this video, but DLSS is not (forgot to enable it).

Purchase DCS: F-16C Viper from: 
https://www.digitalcombatsimulator.co...

In this DCS: F-16C Viper update, we’ll talk about the primary new features coming to our Viper: new ALR-65M radar warning receiver features, an animated tail hook, and the alternate landing gear handle. 

First, we’ll look at some of the new features coming to the Viper’s radar warning receiver, or RWR. Some of these items may have been introduced a bit earlier, so I’ll cover them all in this video.

In the center of the RWR display can be indications for the Search and Low Altitude functions that can be enabled next to your left knee. When the S is flashing on the Search button, acquisition radars are not displayed on the RWR display. This can help declutter the scope. But, if you press the button and the S becomes steady, acquisition radars will be displayed, and an S is displayed in the center of the RWR scope. When the Altitude button is pressed and LOW is displayed on it, low altitude/short-range ground air defense systems are prioritized, and L is displayed in the center of the scope. If LOW is not displayed, then air emitters will be in priority.

If both SEARCH and LOW are both enabled, then the S and L on the scope will mipple.

Also please note that symbol sizes have been slightly reduced and Early Warning Radars, or EWR, are now displayed as a dish symbol on the scope. To see them, the SEARCH button will need to be enabled.

New air and ground emitter visual and audio indications have also been updated. Newly detected emitters will pulsate for a few seconds between half size and full size to grab your attention. When a new airborne emitter is detected, you will hear a high frequency alert tone and when a ground emitter is first detected you will hear a lower alert tone.

When you are locked by an airborne or ground-based radar in tracking mode, the scope symbol will now have a square around the emitter code. As before, if the radar is guiding a missile, there will be a flashing circle around it too. Speaking of radar-guided missiles launches…

The missile launch tone is also now quite different. Rather than continue to sound if the radar is guiding a missile, it will now have a high-frequency launch alert tone of about seven beeps and then it will go silent for 15 seconds. If after 15 seconds a missile is still being radar-guided on you, the tone will repeat but at a lower tone. This pattern will continue until the radar is no longer in missile guidance mode.

The target separate button now correctly separates a group of over overlapping emitters along the azimuth rather than incorrectly spreading them along heading. Only the priority emitter will be at its “true” scope location.

Upon pressing the SYSTEM TEST BIT button, the RWR TEST BIT will run and display on the scope.

Later, once we have a library of the pulse repetition frequency, or PRF, tones for each radar and operating mode, we will add the handoff mode that allows you to cycle the priority emitter and hear the PRF audio of it.

In this next update we’ve hooked up a couple new items in the cockpit. The first is the tail hook. By setting the hook switch to the down position, the hook will be lowered. If then set to the up position, the hook will be slightly raised, but you’ll need to land and request a repair from the ground crew to fully raise it. Before you ask, we’d like to include the ground arrest system for airfields later, but there are currently no plans. I’m sure many of you will try it with the carrier though, good luck.

The other cockpit item is the alternate landing gear handle, left mouse button clicking will allow the landing gear to drop using the same air pressure bottle as the tail hook. Note that the pressure is limited, and you probably cannot do both.

  • Like 14
  • Thanks 9

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

  • 4 months later...
  • ED Team

DCS: F-16C and F/A-18C Velocity Radar Modes Update (COMING SOON)

In this video, we’ll cover two new velocity-based radar modes coming to the Viper and F/A-18C. For the Viper, we have added Velocity Search with Ranging, or VSR mode, and the F/A-18C, Velocity Search, or VS mode has been added. Let’s talk about both.

VSR mode is a new Combined Radar Mode, or CRM, or the Viper radar that can provide additional detection range of nose-on aspect targets. VSR interleaves High Pulse Repetition Frequency, or HPRF, with Medium Pulse Repetition Frequency, or MPRF, but it does not support Situation Awareness Mode, or SAM. The HPRF acts as an alert scan in which the target is detected along with its angle and velocity. The following MPRF scan determines range information. Note that this will only be effective when the nose of the target is in high aspect to you. Once a target is detected in VSR, it can be designated and tracked as a Single Target Track, or STT.

This can be a useful mode to detect and lock onto high aspect targets at greater ranges than possible in Range While Search and Track While Scan CRM modes.

VS mode in the F/A-18C works quite a bit differently. When selected from the radar format page, VS mode provides the most powerful radar mode, capable of detecting targets at the greatest range. However, whereas VS mode will provide target azimuth and closing velocity, no range information is provided. VS transmits only in HPRF with a high average power out setting.

Note that the higher the closing velocity, the higher to the top of the display will the target brick be. Maximum closure speed is 2,400 knots at the top of the display.

Target returns are presented on the b-scope as velocity versus azimuth. Again, it does not indicate range. If there is insufficient target closure, it will not be detected and displayed. As such, VS will only detect targets that are nose-on aspect. If the target is in high aspect, VS is only marginally affected by look down.

  • Like 11
  • Thanks 3

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 3 months later...
  • ED Team

COMING SOON

In this DCS: F-16C Viper video, we’ll look at new features coming to the datalink capabilities of our Viper. As many of you already now, data linked flight members are limited to the same four-ship group as set in the Mission Editor. With this update, it will now be based on the Fighter Channel and the Source Track Number, or STN. This will allow you to set aircraft outside a group to your Team of aircraft 1 to 8 and even change this while in a mission. You can also set up to four donors, but those must be set prior to mission start. Let’s get started.

Let’s start in the Mission Editor to see how we now set up the Viper’s datalink. When selecting an F-16C Block 50 Airplane Group, you will now have an additional tab called datalinks. We’ve also added some new functionality to the Aircraft Additional Properties tab that we’ll look at first.

Along the bottom, we now have three new items under Datalink. The Voice Callsign Label, Voice Callsign Number, and STN are identifiers used when setting up the network. You will probably want to set the Voice Label and Voice Callsign Number to match each aircraft’s callsign. It’s important that each STN be unique within a Fighter Channel and the STN must be entered as an octal, i.e., only values of 0 to 7 are valid.

The Tactical Net Datalink, TNDL, tab as two sub-tabs, one for Settings and one for Network.

The Settings sub-tab allows you to set the Fighter Channel that the network will reside on, but for the time being, these are fixed to just channel 1 within the Mission Editor. In all but the massive missions possible, you can keep this on Fighter Channel 1. You can also keep the Mission Channel for C2 control and Special Channel for HTS functions to 1. The Voice Callsign is auto filled from the Aircraft Additional Properties tab, and if the aircraft is to be the Team leader, check the Flight Lead radio button. The Transmit Power determines the broadcast range.

The Network sub-tab is the meat of setting up the network. The top portion lists up to eight Team members that can exchange data and target assignments over the datalink. Although these can be assigned in the Mission Editor, they can also be edited while in flight. We’ll examine this a bit later. Along the left side of the team member number that is auto assigned and to the right is the Time Difference of Arrival (TDOA) assignment check box. This will determine Team members participating in the HARM Targeting System, HTS, TDOA group. This will be the subject of the next video. To the right of that is the Pilot Name and to the right of that is the Voice Callsign Label and Voice Callsign Number that we discussed earlier. Next is the member’s STN number. The rightmost column can be selected to remove a member from the Team.

If you have open Member slots in the Team list, you can add an entire Group or add an individual aircraft.

Below the Team Member list is the Donor list that can have up to four aircraft. Note that these must be assigned prior to flight; they cannot be viewed or edited once in the cockpit. Like the Members list, each row displays an aircraft with its Member number, Pilot Name, Callsign, STN, and delete option. As donors cannot take part in a TDOA team, there is no column for it. Also like the Members, you can add Groups and individual units to the list.

What is also very important to note is that any aircraft with a TNDL STN can be added to the Member or Donor network, not just other F-16s.

We’ll get in the air now and look at this in action.

To view our datalink settings, select LIST from the ICP, then Enter for DLNK, and dobber right once. Here we can see that our Fighter Channel is set to channel 1, our Mission Channel is set to Channel 1, and our Special Channel is set to 1. On the right side we can see our callsign, first and last letter of Viper and the number of 11. We can also see that we are the Flight Leader and the transmit power is set to Medium. Dobber once more to the right.

Much of this will look familiar from the Mission Editor. We can see our Member Number of 1 to 8, a “T” if the member is assigned to the TDOA team, and the STN. We’ll talk about TDOA in a later video. 

Looking at the HSD, we can see our flight of four aircraft around us with their Member Number in blue. To the left are Team members 5 to 8, also in blue with Member Number. To the right are the four Donors, marked as green with a center dot. Ahead of us are four aircraft not in our network. 

Let’s look at an example of changing a Team member assignment; in this case, moving a Donor to Team Member 8. To do so, we’ll first Dobber down until we select the STN of Member 8. Now, we’ll enter the STN of a donor aircraft, in this case, 00304. Upon pressing enter, Member 4 is my Team Member 8.

We hope you enjoyed this explanation of expanded datalink functionality for the Viper and recognize it as a major advancement for DCS in general.


NOTE 1. There is a known issue with the lack of a dot in the center of the donor icon on the HSD. This will be resolved prior to launch.
NOTE 2. Due to complications stemming from our other businesses, we had to adjust datalink terms. In this case, Tactical Net Datalink (TNDL).
NOTE 3. As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as I’d like to, I lack the time re-record these videos.

  • Like 17
  • Thanks 6

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • ED Team

Changes Coming to Sighting Point/Cursor Slews, Snowplow, and VIP/VRP Logics

COMING SOON

Dear all,

In the next update to Open Beta, you can expect a large number of fixes for the DCS: F-16 Viper. Over the past six months, the F-16 team has been revamping the aircraft's air-to-ground sighting and weapon delivery sub-modes to be more authentic and to address many reported bugs in how the F-16 integrates it's sensors, HOTAS, and targeting logic. Along with the upcoming changes to the datalink within the F-16, this has been a very large task that required our dev team to address many aspects of the F-16 all at once, due to the level of integration such changes would require within the aircraft systems.

Understandably, this may seem like a lot of changes, but for the most part very little will actually change within the DCS F-16. These changes are mainly focused on ensuring all the minute details that are required for the F-16 avionics to function are properly implemented to prevent any sort of logic conflicts when using the air-to-ground targeting systems. While the Early Access Guide is still receiving revisions to sufficiently explain how all of these weapon delivery sub-modes are intended to work within DCS F-16, we are including a brief conceptual overview for our Viper players to frame the underlying logic in hopes that it will enhance everyone's understanding of why these updates were necessary; until the Early Access Guide can be updated to reflect these concepts.

F-16 Conceptual Overview

The F-16 sensors (FCR, TGP, and HTS) drive a singular System-Point-of-Interest (SPI). As such, only one sensor can be in a track mode at any given time.

  • When any sensor enters a track mode, it will cause the other sensors to exit their track mode. For example, if the FCR is in Fixed Target Track (FTT) against a surface target location and the TGP enters POINT track, the FCR will exit FTT. This is because the non-tracking sensors must remain aligned to the tracking sensor to maintain the singular SPI location. If two sensors were in track mode simultaneously, the single SPI logic of the F-16 would be violated.
  • When a sensor enters a track mode (FCR FTT/MTT, TGP AREA/POINT, or HAD designation), this automatically puts DTOS, VIS, or EO-VIS into a post-designate state at the corresponding location.

The F-16 A-G master mode includes many weapon delivery sub-modes that may be used, depending on the weapon selected on the SMS page. These sub-modes are categorized as either "Pre-planned" or "Visual" weapon delivery sub-modes.

"Pre-planned" sub-modes revolve around the use of steerpoints that have been programmed at pre-planned target locations.

  • These sub-modes include CCRP, LADD, PRE, EO-PRE, and EO-BORE. (PRE is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-PRE and EO-BORE are only used with AGM-65)
  • These sub-modes permit direct sighting options (STP/TGT) or offset aimpoint sighting options (OA1/OA2), as well as the Snowplow sighting method.
    • Sighting points are used to ensure the accuracy of the targeting solution to the target steerpoint prior to weapon release. Offset aimpoints are not targets themselves, but are used to ensure the target location (TGT) is accurately placed for weapon delivery (i.e., due to INU drift in a pre-GPS scenario)
    • The selected sighting point determines where the System-Point-of-Interest (SPI) is placed relative to the steerpoint, which directs all sensors to a singular location.
    • Snowplow permits employing a "Pre-planned" weapon delivery mode when existing steerpoints are not practical, and provides a means to rapidly direct the SPI in front of the aircraft at the Snowplow cursor. If a designation is performed while in Snowplow, the main Navigation cursor is slewed to that location and Snowplow is exited.

"Visual" sub-modes are geared toward visually acquiring a target location independently of a pre-planned steerpoint.

  • These sub-modes include CCIP, STRF, DTOS, VIS, and EO-VIS.  (VIS is used with AGM-154A, GBU-31/38, CBU-103/105, or GBU-24; EO-VIS is only used with AGM-65)
  • Sighting options are not available in these sub-modes, nor is the Snowplow sighting method. The sighting option rotary and the Snowplow OSB options are removed when these sub-modes are entered.
  • These modes will automatically place the FCR in AGR (Air-to-Ground Ranging) and the mode cannot be changed except for placing it in OVRD/STBY.
  • The TGP (if installed) is automatically slaved to the weapon solution in CCIP or STRF sub-modes.
  • The TGP (if installed) is slaved to the TD Box in DTOS, VIS, or EO-VIS sub-modes, even when these modes are in a pre-designate state. This augments the visual identification of targets and assists in optically locating targets at extended ranges.
  • When a target location is designated in DTOS, VIS, or EO-VIS sub-modes, this also updates the current steerpoint location by moving the Navigation cursor to the same location. This ensures a seamless transition between sub-modes (Example DTOS->CCIP->CCRP) against the same target location in which the SPI is maintained on the target.

Visual Initial Point (VIP) and Visual Reference Point (VRP) sub-modes are a means of conducting strikes against pre-planned target locations in CCRP sub-mode while using visual landmarks for final alignment of the targeting solution. These are especially useful when conducting low-level strikes in which the target may not be visible until just prior to weapons release.

  • These sub-modes permit cursor slews to be performed to align the targeting symbology with visual landmarks without affecting the cursor deltas of the main Navigation cursor.
  • VIP adds "IP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VIP mode is entered, the sighting point is automatically set to "IP", after which the sighting points may be advanced in a sequence of IP->TGT->OA1->OA2->IP.
  • VRP adds "RP" as an additional sighting point option that may be selected using TMS Right-Short while the HUD or FCR is SOI, or by pressing the corresponding sighting point rotary at OSB 10 on the FCR or TGP MFD formats. When VRP mode is entered, the sighting point is automatically set to "TGT", after which the sighting points may be advanced in a sequence of TGT->OA1->OA2->RP->TGT.
  • These modes allow a single overfly designation of the IP or RP in which the SOI is automatically set to the FCR and the sighting point is set to the TGT. This allows a seamless transition with one button press from the ingress phase into the final attack phase, without the requirement to manually slew the cursor to align the diamond symbol in the HUD with the physical landmark that represents the IP or RP.

Changelog:

Sighting Points & Cursor Slews

  • Cursor slews are now possible in several different modes that are independently accumulated. As an example, the VIP cursor may be slewed and zeroed independently of the Navigation cursor. If Cursor Zero is pressed and "CZ" remains displayed on the MFD, it is because another cursor still has cursor slews applied. This may be seen when the DTOS/VIS cursor is zeroed back to the FPM, but the main Navigation cursor may still be slewed away from the original steerpoint location. To zero the Navigation cursor, CCRP or CCIP should be entered and then CZ pressed.
  • When cursor slews are applied, Cursor Zero is needed to remove them. For a time, changing the selected steerpoint was erroneously zeroizing the cursor when it should not have been. This has been rectified so that cursor deltas are maintained during steerpoint switching (ie, if the TGP was looking 500 meters west of steerpoint 1, it will be looking 500 meters west of steerpoint 2 if the STPT is advanced from 1 to 2).
  • The TD Box occludes the steerpoint diamond. If they are co-located, which is the case in "Pre-planned" A-G sub-modes like CCRP or LADD, the steerpoint diamond will be hidden by the TD Box.
  • When the steerpoint is slewed using the cursor, the OA1 and OA2 offset aimpoints will always slew with it to maintain their programmed offset distance/direction as entered on the DED DEST page.
  • Pressing Cursor Zero no longer zeros the OA1/OA2 settings. These can only be zeroed by manually editing the RNG value to 0 on the DED DEST page.
  • If the RNG value of OA1 or OA2 is set to 0, the OA triangle symbols will be removed from the HUD/HMCS and will not be available in the sighting point rotary options.
  • OA1 and OA2 will not be available in the sighting point rotary options if FIX or A-CAL are displayed on the DED.
  • When not in VIP or VRP modes, the OA1 or OA2 triangle symbols will not be displayed in the HUD/HMCS if not selected using the sighting point rotary option. When in VIP or VRP modes, both OA triangle symbols (if RNG is not 0) are always displayed along with the IP/RP diamond, TGT TD Box, and PUP circle symbols.
  • Sighting point options are not available if in any "Visual" weapon delivery sub-mode: CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method.
  • Sighting points may be cycled using TMS Right-Short while the HUD or FCR is SOI (prior to this it was only possible with FCR as SOI).
  • The "Ghost A-G Cursor" (white crosshairs) is now displayed on the HSD at the current sighting point location for all sighting points (including OA1, OA2, IP, and RP). Prior to this it was only displayed when TGT was the selected sighting point.
  • The Azimuth Steering Line will only be referenced to the TGT sighting point location, even if the sighting point is changed to OA1, OA2, IP, or RP. Only the direct sighting point (TGT) can represent the target solution for weapon delivery; offset aimpoints only assist in alignment of the targeting solution.
  • Only one sensor can be in a "track" mode at any given time, since the SPI represents the location to which all aircraft sensors are directed. Entering a track mode in one sensor will cause other sensors to break lock.
    •     If FCR enters FTT or MTT, the TGP will exit POINT/AREA track and any HAD designation will be dropped.
    •     If the TGP enters POINT or AREA track, the FCR will break FTT/MTT lock and any HAD designation will be dropped. 
    •     If a threat radar symbol is designated on the HAD, the FCR will break FTT/MTT lock and the TGP will exit POINT/AREA track.
  • If the sighting point is changed, the aircraft sensors will exit their respective tracking modes to prevent cursor slews from being erroneously input into the system.
  • The TGP is automatically slaved to the DTOS/VIS TD box while in pre-designate state.
  • If in DTOS/VIS sub-mode and a sensor is commanded into a track mode, the sub-mode will automatically enter post-designate state at the corresponding sensor track location. (ie, if the TGP is SOI and being slewed in DTOS mode and commanded to POINT track, DTOS will enter post-designate at that location)
  • If in any "Visual" weapon delivery sub-mode (CCIP, STRF, DTOS, or VIS; or if MARK is displayed on the DED with "HUD" as the marking method), the FCR will enter AGR mode and cannot be changed.
    •     FCR mode selection page is corrected to prevent manually changing the FCR out of AGR mode without changing the weapon delivery sub-mode.
  • When a laser-guided bomb is selected in SMS, the TGP laser will be inhibited from firing if the sighting point is set to OA1, OA2, IP, or RP. This prevents an LGB from being diverted from the intended target location, which is represented by the direct sighting points of TGT or STP.

Snowplow

  • Snowplow is only available while in a "Pre-planned" weapon delivery sub-mode: CCRP, LADD, PRE, EO-PRE, EO-BORE; or if in NAV mode if the FCR is not in an A-A mode.
  • When Snowplow is entered (via OSB 8 on the FCR or TGP MFD formats), the SPI is placed at the location of the Snowplow cursor in a pre-designate state (represented by the TD Box in the HUD).
    • In NAV mode when there is no TD Box and the steerpoint diamond represents the steerpoint location, there will be no HUD symbology corresponding with Snowplow cursor while in a pre-designate state.
    • If TMS Up-Short is pressed while the HUD, FCR, or TGP are SOI, Snowplow is exited via post-designate and the main Navigation cursor is moved to the location of the SPI (represented by the TD Box in A-G master mode or the steerpoint diamond in NAV master mode).
    • If Snowplow is exited from pre-designate by pressing "SP" at OSB 8 on the FCR or TGP MFD formats, the SPI simply returns to the existing location of the main Navigation cursor since a designation was not performed.
  • The Snowplow cursor location is placed in three dimensions by the following.
    • Aircraft Heading: The cursor will remain along the aircraft longitudinal axis and cannot be changed.
    • Range: The cursor will be placed in front of the aircraft at 50% the A-G FCR range. Adjusting the FCR range (even if the FCR is in OVRD or STBY modes, or if the RF switch is in QUIET or SILENT) will move the Snowplow cursor in range.
      •  If the FCR is powered OFF on the SNSR PWR panel, the Snowplow cursor is fixed 5 NM in front of the aircraft and cannot be changed.
    • Elevation: The cursor is set to the same elevation as the current steerpoint while in pre-designate. When Snowplow is exited via post-designate, the elevation of the SPI is re-calculated to the terrain elevation.
      • When weight-on-wheels, the cursor is set at the same altitude as the aircraft.

VIP/VRP

  • It is no longer possible to enable VIP and VRP for the same steerpoint. Enabling one mode will disable the other if set to the same steerpoint.
  • When VIP or VRP mode is entered, a Cursor Zero is no longer performed to the main Navigation cursor.
  • When an overfly designation is performed in VRP mode, the designation will now designate the location of the RP, not the TGT.
    • Only one overfly designation may be performed of the IP in VIP mode or the RP in VRP mode, using TMS Forward-Short while the HUD is SOI. Cursor slews may still be performed before or after the designation, but VIP and VRP modes must be exited and then re-entered to perform subsequent overfly designations.
  • When entering VIP mode, the EHSI will be directed toward the IP and the Azimuth Steering Line will be to the TGT. When an overfly designation of the IP is performed, the EHSI will switch to the TGT.
  • When entering VRP mode, the EHSI and the Azimuth Steering Line will be to the TGT, even after an overfly designation of the RP is performed.
  • Like 22
  • Thanks 12
Link to comment
Share on other sites

  • ED Team

COMING SOON

NOTE 1. A TDOA member can only contribute if they are not already tracking an emitter with the HTS. 
NOTE 2. This works for both single player and multiplayer. When in multiplayer and a Slave, you will get an audio DATA alert. 
NOTE 3. Due to complications stemming from our other businesses, we had to adjust datalink terms. In this case, Tactical Net Datalink (TNDL). 
NOTE 4. As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as I’d like to, I lack the time re-record these videos.

Hey everyone, Wags here from Eagle Dynamics.

In this DCS: F-16C Viper video, we’ll build upon the previous video about new datalink features. Namely, the ability to use participating data linked Team members more accurately and quickly pinpoint a threat radar emitter, like a SAM site. This is termed Time Difference of Arrival, or TDOA, and it is only available when each Team member is loaded with a HARM Targeting System, or HTS, pod. There must also be a minimum of three Team members in a TDOA team.

We’re here over the Persian Gulf map in a four-ship, with each member assigned an HTS POD and two AGM-88 HARMS. This is a common Viper SEAD flight in which both elements support each other. Let’s first bring up the Data Link page by selecting LIST from the ICP, then Enter to select Data Link, and Dobber right twice to display the data link assignments of Team members. For a Team member to participate in the TDOA team but must have the “T” enabled next to it. This can be toggled by Dobber up and down to select the Team member and then selecting any keypad 1 to 9 keys to toggle the TDOA selection. All eight Team members can participate in a TDOA network.

From the HAD page, select TM for Team members or AL for all to have all selected TDOA members to participate. If you wish to disable then, select NO.

After designated an emitter by pressing Target Management Switch, or TMS, up while the cursor is over a target, you can then press TMS left for greater than one second to display TDOA on the HUD and command TDOA participant members to designate the same target with their HTS and provide multiple triangulation angles. Note that the target will need to be within the Team member’s HTS field of view.

To provide optimal triangulation, the other element will attempt to approach the target from a different angle than yours.

When TDOA designated, TD-M is indicating that the target has been designated and you are the Master. If in multiplayer and receiving a designation as the Slave, you get a TDOA HUD message and DATA voice message, and once you designate, you’ll see a TD-S on the HAD for Target Designated Slave.

When a TDOA Team member participant is also tracking the target and contributing, it will have a segmented, white line between it and the target. You notice that the Position Quality, PGM, value will attain a high precision, 1 value much faster.

To exit TDOA tracking, press TMS down.

Happy weaseling!

 

  • Like 22
  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 3 months later...
  • ED Team

In this DCS: F-16C Viper video, we’ll review the new features coming the Viper. These include Laser Spot Search, or LSS, and Laser Spot Track, or LST functionality for the targeting pod, or TGP; the Control page for the targeting pod, the Freeze function for the Horizontal Situation Display, or HSD, page; and the addition of new Viper weapons; and changes to AIM-9 functionality. Let’s get started.

NOTE 1. Apologies for the audible breathing. I have a cold and am congested, but I believe better to create a video to explain these new features. 

NOTE 2: As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as I’d like to, I lack the time re-record these videos.

First, let’s look at Laser Spot Search, or LSS, and Laser Spot Track, or LST. As you might imagine, we’ll be using this to allow the targeting pod to search for specific laser Pulse Repetition Frequency, or PRF, and then be able to track it. The laser designation source could be a JTAC or another aircraft. Why would you want to use this method? Primarily if you require very specific targeting that only an external source can provide, for example, like having eyes on.

From the Instrument Control Panel, or ICP, select the LIST button, then zero for miscellaneous on the keypad, and then 5 for Laser.

On the laser page, we see the laser PRF that our targeting pod will lase with, and the laser PRF code that it will search for. It defaults to 1688 and we’ll use that. Note that a laser code must be an octal, meaning, only digits 0 to 8. 

Because we’ll be using an external laser-designation source, we’ll contact the JTAC and ask for laser designation of the target.

At waypoint 2 is a target array, where the target is located. Let’s enable the TGP by bringing up on the left MPD and make it our SOI, this should be old hat by now. Note that at the top of the left side we see our LSS code of 1688. To start the LSS operation, press the Cage/Uncage button your throttle or press the LSS OSB.

Once the laser code is detected, the Laser Spot Track, or LST, is transitioned from an LSS. We can now Target Management Switch forward to designate that location as our Senor Point of Interest and now conduct a standard CCRP laser-guided bombing attack.

While we are here on the targeting pod page, we can now select the CNTL OSB to display the Control page. From the control page, we can elect to display the gray scale to calibrate the TGP display, and we can enable or disable coordinates, north arrow, and yard stick distance by pressing the N/M OSB.

For this update, we’ve also added the Freeze (FZ) function to the Horizontal Situation Display, or HSD. It behaves differently if the HSD is SOI or not.

If SOI, indicated by the box around the periphery of the display, pressing the freeze OSB sets the HSD to the centered format and ground stabilizes the HSD cursor at its location.

If the HSD is not the SOI and freeze is selected, it will again center the HSD but instead ground stabilize on the ownship’s current location on the HSD. 
When in freeze mode, expand is disabled and steerpoints 1 to 99 are frozen.

In this update, we’ve also added some new weapons. These include the LAU-68 and LAU-131 rocket pods for Hydra unguided rockets and both the AIM-9P3 and AIM-9P5 Sidewinder air-to-air missiles.

  • Like 10
  • Thanks 4

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

  • 2 months later...
  • ED Team

AGM-65 EO sub-mode Improvements

Dear all,

In the latest DCS update, the F-16's EO sub-modes (EO-VIS, EO-PRE, and EO-BORE) have received some updates to improve their logic and the AGM-65 missile seeker control interface for the F-16. For the most part the underlying functionality won't change all that much; but the AGM-65 seeker behavior will be more consistent and accurate within each sub-mode.

Four terms (or modes) are used to describe the AGM-65 seeker operation with regards to the F-16 interface:
BORE: Seeker is caged straight ahead in line with the missile body axis.
SLAVE: Seeker is slaved to the SPI.
SLEW: Seeker is steered by pilot input.
TRACK: Seeker is tracking a target.

When not in TRACK and the SOI is set to the MFD WPN format, the seeker will be in SLEW.

When not in TRACK and the SOI is set to anything other than the WPN format, the seeker will be in either BORE or SLAVE, based on the current EO sub-mode:

  • EO-VIS: Seeker is in SLAVE mode, slaved to the SPI, which is located at the TD box.
  • EO-PRE: Seeker is in SLAVE mode, slaved to the SPI, which is located at the current steerpoint.
  • EO-BORE: Seeker is in BORE mode, caged straight ahead.

EO-VIS
The main effort of the changes made to this sub-mode was to ensure that the logic received the same functional improvements that DTOS and VIS sub-modes received several months ago, specifically in regard to how the HUD/HMCS designations worked with the SPI and TGP aiming. The most significant changes that players need to be aware of is how the TMS Forward/TMS Aft commands function in pre- and post-designate, depending on whether the SOI is set to HUD/HMCS or WPN.

  • When in pre-designate with the HUD or HMCS as SOI, the TD Box will be stabilized to the FPM (HUD) or HMCS Aiming Cross as it is now, and the first TMS Forward will ground stabilize the TD Box into post-designate (no change from before the update).
  • When in post-designate with the HUD or HMCS as SOI, the SOI will remain set to HUD and HMCS, allowing the TD Box to be slewed to fine-tune the position on the ground as desired. This will be a noticable change from previous versions, in which entering post-designate simultaneously moved the SOI to WPN. Now, a second TMS Forward when already in post-designate will be required to move the SOI to WPN.
  • When in post-designate with WPN as SOI, TMS Forward will command the AGM-65 to TRACK mode, and TMS Aft will slew the AGM-65 seeker back to the SPI (no change from before the update).
  • To return EO-VIS to pre-designate, the SOI must be moved to the HUD or HMCS, and TMS Aft is pressed to cage the TD Box to the FPM. This is the other notable change from previous versions, in which pressing TMS Aft while WPN was SOI was also returning the EO-VIS to pre-designate with the SOI back to HUD or HMCS. As a result, it is now possible to return the AGM-65 seeker back to the SPI while keeping the SOI on WPN and remaining in post-designate.

Since the seeker will remain in SLAVE mode while the WPN is not SOI, it is now easier to perform an off-boresight HMCS designation of a ground target for a handoff to the AGM-65. As long as the WPN is not SOI, the AGM-65 will remain slaved to the designated SPI location, even if at a gimbal limit. As the aircraft turns inbound and rolls out on the attack heading, the seeker will have arrived to the SPI, at which time the second TMS Forward may be pressed to transition the SOI to WPN for the final target acquisition and engagement. Even if you press TMS Forward too soon before the seeker has arrived at the SPI location, a press of TMS Aft while WPN is SOI and the SPI is within the gimbal limits will command the seeker to the SPI.

Below is a summary of the EO-VIS procedure, with the changes highlighted in red:

  1. (HUD/HMCS SOI) TMS Forward to ground stabilize TD Box into EO-VIS post-designate.
  2. (HUD/HMCS SOI) TMS Forward again to set WPN as SOI and enter SLEW mode or DMS Aft to manually set WPN as SOI and enter SLEW mode. Seeker LOS circle appears.
  3. (WPN SOI) Slew seeker over target.
  4. (WPN SOI) TMS Forward to enter TRACK mode.
  5. (WPN SOI) TMS Aft to exit TRACK mode/slew seeker back to SPI but remain in SLEW mode or DMS Forward to set HUD/HMCS as SOI and enter SLAVE mode to reposition TD Box as desired. LOS Circle will disappear when seeker enters SLAVE mode.
  6. (HUD/HMCS SOI) TMS Forward to return SOI to WPN and re-enter SLEW mode at current SPI or TMS Aft to return to EO-VIS pre-designate to designate a new SPI if desired. 

EO-PRE
Very little has changed in this sub-mode, but it is now possible to do a handoff from the FCR in GM, GMT, or SEA mode.

  • When the FCR is SOI and set to GM, GMT, or SEA sub-modes, entering FTT or MTT will also transition the SOI to WPN and the AGM-65 seeker will enter SLEW mode. However, the seeker will still need to be manually commanded to TRACK mode using TMS Forward while WPN is SOI. (An automatic handoff to the AGM-65 directly into TRACK mode is not possible when using the FCR; this is only possible when using the TGP.)
  • When the SOI is manually set to WPN, the LOS circle will appear since the AGM-65 is now in SLEW mode, regardless of whether the FCR is in FTT or MTT.
  • TMS Aft while the WPN is SOI will command the seeker back to the SPI, but the SOI will remain set to WPN. The LOS circle will remain and the seeker can still be slewed unless the SOI is returned to FCR or TGP.

EO-BORE
Similarly to EO-PRE, little has changed with this sub-mode.

  • If the SOI is not set to WPN, the seeker will be in BORE mode, returning the seeker to the missile body axis boresight position.

---------------------------------------------------------

In addition, it must be noted that the SOI will automatically be set to WPN any time the TGP or the FCR enters a track mode, regardless of the selected EO sub-mode. Based on research, this reflects accurate behavior for the version of F-16 that is being simulated in DCS.

Kind regards,

Wags

  • Like 11
  • Thanks 5

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...