Viper Mini-Updates

[Wags]

Dear all,

In addition to the ECM pod functions coming to the Viper, we will also be introducing jamming effects on the FCR. When the FCR can generate azimuth, range, Vc, etc. data for a target and the target is jamming, a yellow double-chevron symbol is placed over the contact. If, however, range cannot be resolved due to jamming, a yellow, double-chevron symbols is placed along the top of the FCR page along the detected azimuth angle of jamming.

The attached image shows examples of both of these conditions and a non-jamming contact.

This is planned for January 2022.

Kind regards,

Wags

[Wags]

Dear all,

Since I created the Viper ECM video, we have been able to enable separate SPJ responses for the XMIT switch in Position 1 and 2. We hope to include this in the next update, but it will depend on testing results.

• When XMIT is in Position 1 we have Radar Priority. When in Radar Priority and the jammer is transmitting and ownship radar and HARM/HTS performance is reduced by 40%.
• When XMIT is in Position 2 we have ECM Priority. When in ECM Priority, the FCR and HARM/HTS are silenced unless an AIM-120 is the active weapon. In this case, it behaves the same as Position 1. 

The overall jamming effect on hostile radars has also been substantially increased.

We plan to also implement this for the Hornet's jammer, but I do not have a time estimate yet.

Electonic attack will be playing a bigger role in DCS in 2022.

Kind regards,

Wags

[NineLine]

In this DCS: F-16C Viper video, we’ll look at the dive toss, or DTOS, bombing mode. DTOS allows you to designate a ground location as the Sensor Point of Interest, or SPI, through the HUD or HMCS. This designation can then be used for a CCRP attack using unguided and laser-guided weapons.

DTOS mode can be selected as a bombing mode from the SMS page at OSB 2 or cycled to using the nosewheel steering / missile step button on the control stick.

With DTOS selected and the HUD as the Sensor of Interest, or SOI, a 10 milliradian box is slaved to the flight path marker. You can then either TMS forward to ground stabilize its location or use the radar cursor switch to slew the box and then TMS forward to ground stabilize.

 Alternatively, you can set the HMCS as SOI and either ground stabilize the DTOS cue based on the aiming cross or slew and then TMS forward to ground stabilize.

In both HUD and HMCS cases, TMS Aft will slave the DTOS cue back to the flight path marker or aiming cross.

Once ground stabilized and designated, the location is designated as the SPI and standard CCRP steering is provided. When wishing to conduct a visual CCRP attack through the HUD or HMCS, this is the preferred method. 

As this will also create a SPI, the targeting pod and Maverick would be handed off to it.

Key Commands:

Nosewheel Steering / Missile Step Switch: s
Target Management Switch (TMS) Forward: Right Ctrl + Up Arrow
Target Management Switch (TMS) Aft: Right Control + Down Arrow
Display Management Switch (DMS) Forward: Right Alt + ;
Display Management Switch (DMS) Aft: Right Alt + .
Weapon Release: Right Alt + Space Bar

 

[Wags]

Much of our Viper work is now centered on the Link 16/IDM interflight datalink. This is a very important and useful element of the Viper, and currently, our highest Viper priority. With this feature in place, you will be able to:

- Share Mark Points between flight members

- Share SPI between flight members

- Network the flight together for HARM HTS TDOA mode to more effectively triangulate emitter locations

- Sending SEAD contacts between flight members

- Assign air-to-air target sorting between flight members

- Support Primary Datalink Track (PDLT)

- CAS mission assignments and reception

- Battle Damage reporting support

We also wish to roll in EXP HAD and HSD support.

As you might gather, this is a very complex task, and we don't have a delivery date at this time. We look forward to updating you on this task as it progresses.

In parallel, other Viper items continue development such as the instantaneous turn rate / available G tuning, pilot model, bug fixes, and more.

Kind regards,

Matt

 

[Wags]

Link 16 SPI sharing was implemented today. I think this will prove a very handy feature.

With the HSD not SOI, pressing the COMM switch right (inboard) for greater than 0.5 seconds will transmit the player’s SPI to other Mission members. When a SPI message is sent, the XMT L16 label at OSB 6 will highlight for two seconds on the HSD.

The sent SPI is based on the current SPI sensor track. If there is no SPI sensor track, then the current Steerpoint is sent as the SPI.

When the SPI is sent, recipients see it as a large, white “X”, the same as a Mark Point. On the HUD, MKPT## will appear that assigns the SPI location to Steerpoints 71 to 70. “DATA” will be heard as a voice alert. As you can see, it is the same as receiving a Mark Point, but it based on a SPI location rather than a Steerpoint location.

One difference is that if the SPI is created by the TGP or A-G FCR, there will be a lock line between the sender of the SPI (Mission members 1 to 4) and the SPI “X” symbol/location on the HSD. The line will disappear after 30 seconds or by pressing WARN RESET on the UFC.

We look forward to adding this to an upcoming Open Beta.

Also, to answer the posed question, yes, we plan L16 and IDM. 

Kind regards,

Matt

[Wags]

With the earlier release of the DTOS mode, I got quite a few "Christ-on-a-bike, Wags, where the max toss anticipation cue?" Well, it's now in the game and should be released in the next big Viper update based on final testing results. 

The maximum toss (45 degree) anticipation cue consists of a circle, 100 mR in diameter, displayed on the HUD (below the boresight cross at 0 degrees azimuth and -3 degrees elevation). The cue is displayed 2 seconds prior to a maximum toss pull-up (based on 4.0g in 2 seconds). When the solution cue is displayed, the anticipation cue flashes for 2 seconds before being removed from display. Weapon release occurs as the aircraft approaches a 45-degree pitch. Because there are multiple release points that can result in weapon release, release can occur any time after the solution cue is displayed. For less than a 45-degree toss, the pitch at release varies depending on the maneuver performed.

Kind regards,

Matt

 

[Wags]

To finish out a busy Viper development week, we've added Markpoint exchange between flight members (IDM and L16 Steerpoint storage ranges) and hearing the "Lock" VMU message when an STT lock has been obtained while in an ACM mode.

Have a good weekend,

Matt

[Wags]

Today we completed internal integration of L16 and IDM sharing of HTS/HAD emitter contacts. This will allow you to designate and share emitter location between Flight, Team, and Donors. Additionally, sharing of emitter triangulation data between flight members is also internally complete as part of the TDOA option from the HAD page.

We've made further adjustments to SPI sharing regarding accurate HSD symbology that includes Flight/Team member ID.

Finally, we've made good progress on adjustments to the ITR and G-onset, and internal verification tests will probably start next week.

If testing goes well, we plan to have it included in the next Viper update.

Progress on datalink is going well, but we still have some significant items to still complete. Once datalink is complete, work will commence on the CRUS DED page.

In parallel to datalink and FM, DEST DED page, MAN bombing mode, and LADD bombing mode are in work.

Kind regards,

Matt

[Wags]

Today we integrated Offset Aim Points (OAP) into our internal version. This will allow you to create two offsets from a Steerpoint (OA1 and OA2) from which you set a point to conduct an attack when set as the SPI. This is normally done on the AG radar page (TGP is possible too), and often when a good radar track cannot be had on the programmed Steerpoint or target.

On the HUD, they appear as a triangle when selected from the Sighting Options at OSB 10.

Kind regards,

Matt

[BIGNEWY]

WORK-IN-PROGRESS

 

Growling Sidewinder Viper Flight Model Changes Preview:

https://youtu.be/mz1ZhS78wws

In our next open beta update, we’ll be adding many new features to the Viper. In this video, we’ll go over the more visible items, but please consult the change log for the full list once released.

One of the biggest items in the update has been tuning of the G onset and instantaneous turn rate, or ITR. These have been adjusted to better match public data, and we feel more accurately depicts the performance of the Viper. Please note though that you can’t simply pull 9 G in any situation, it is highly dependent on your gross weight, drag index, altitude, airspeed, and more. To provide an impartial view on these changes, we invite you to check out Growling Sidewinder’s video on these changes.

Okay, let’s start talking about the more visible changes coming to this update.

We have adjusted nose pitch at takeoff. It will no longer continue to rise on you un-commanded when the gear and flaps come up. To best see this, keep an eye on the boresight cross, and not the flight path vector. against the pitch ladder.

When in an Air Combat Maneuver, or ACM, radar mode and you lock a target, you will now hear a “Lock” audio message.

Also, when in ACM mode and you command the Slew sub-mode, the Helmet Mounted Cueing System, or HMCS, will now display just the aiming cross.

If in Dive Toss Bombing mode, you can now designate the target by also depressing the weapon release button on the control stick.

We’ve added three more types of inert training bombs. These include the BDU-50LD low drag training bomb, BDU-50HD high drag training bomb, and the BDU-50LGB laser-guided training bomb.

We have added the final Markpoint option, an overfly Markpoint. To create an overfly Markpoint, select AA master mode, select MARK from the ICP, select the OFLY option, and press TMS forward twice to set the location to the next available Steerpoint in the Markpoint range of Steerpoints. The location is marked with a small yellow cross on the HSD.

Related, to Markpoints, we have also corrected a Markpoint location sometimes drifting on the HSD.
 

Although not complete, we have added several new datalink functions in this update.

With the HSD as your Sensor of Interest, or SOI, indicated by the box around the periphery, and the COMM switch on the throttle is held to the right for greater than .5 seconds, your current steerpoint will be sent to all your flight members. Your flight members will hear a “data” message and see Markpoint and the Steerpoint number that the location was saved to, 71 to 80. They will also see a large, white cross on their HSD at the sent location. To remove, press the Warning Reset Button on the ICP. You can then slew your HSD cursor over the point and TMS forward over it to set it as your steerpoint.

When the HSD is not SOI and you press long right on the COMM switch, your Sensor Point of Interest will be sent to your flight members. They will see it as a red tringle with a line and the reference number of the flight member. You will also see a dashed, blue line between the flight member and the target.  

With a HARM Targeting System, or HTS, pod loaded, you can also send detected locations of radar emitters to flight members. With the HAD as your SOI, designate a contact and press the COMM switch long to the right. Your flight members will see the datalinked location as a yellow symbols with a strike through it.

Also, on the HAD, we added the cursor bullseye location.

 

[NineLine]

In this video, we will explore use of the Destination DED page to create and edit existing steerpoints and learn how to use Offset Aim Point through the targeting pod.

[Wags]

Dear all,

In an upcoming Viper update, we will be adding category (CAT) fuzing options from the SMS/CNTL page. Based on the fuze CAT, you will be able to set fuze options. We are starting with CAT 1 fuzes with the ability to set the Arming Delay (AD) value that determines how fast the bomb arms after being released, and the Armed Delay 2 (AD2) that determines the time from impact that the fuze will activate and detonate the bomb. This now allows delayed fuzing.

If the AD value is set such that the bomb would not fuze before weapon impact, a LOW indication will appear right of the flight path vector. If you release in such a condition, the bomb will not fuze/detonate.

For now, the focus is on CAT 1 fuzes:

CAT 1: Impact fuzes requiring only an arming delay

CAT 2: Altitude fuzes requiring an arming delay and burst altitude

CAT 3: Time fuze requiring an arming delay and burst altitude

CAT 4: Rockeye fuzes requiring two arming delays and burst altitude

Kind regards,

Wags

[NineLine]

This is a useful tool to maintain situational awareness on your wingman, element lead, or a target.

You may notice that this is not as fancy as the Hornet HUD and helmet datalink. Although both our Viper and Hornet are based in mid-2000s jets, the Viper is rather ghetto compared to the Hornet in this regard.

To assign the PDLT to a datalinked contact, the HSD needs to be SOI, and the HSD cursor is slewed over the datalink-only or a non-designated correlated contact, and TMS Forward is pressed to assign it. An already designated (bugged) contact cannot be assigned as the PDLT, assigning it would make it a designated contact. If a PDLT contact becomes the designated contract, the PDLT octagon is removed.

If there is a PDLT assigned contact, and a different contact is assigned to be the PDLT, the PDLT assignment is moved to the newly assigned contact.

If there is an assigned PDLT contract, pressing TMS Right will cycle the PDLT through the undesignated datalink and correlated A-A contacts. The step order is from the bottom of the HSD to the top. If of equal distance on the HSD, then left to right.

TMS Aft, with HSD cursor over the PDLT, removes the PDLT assignment. If the PDLT is also over a threat ring, the first TMS Aft removes the threat ring, and the second TMS Aft removes the PDLT assignment. If the datalink track is lost on the PDLT contact assignment, the PDLT symbol is removed.

[BIGNEWY]

DCS: F-16C Viper | Visual Initial and Reference Points

COMING SOON

In this DCS: F-16C Viper video, we’ll discuss Visual Initial Points, or VIP, and Visual Reference Points, or VRP. As we discussed in a previous video about Offset Aimpoints, each Steerpoint can be assigned two offsets, or OA, points, a VIP, and a VRP. These are all valuable tools for setting up your attack on a known location or an offset location from it based on a bearing, range, and elevation.

This is one of the more complex features of the Viper, so strap on your thinking caps.

Let’s first talk about VIPs. In this mode, a selected bearing and range from a Steerpoint (IP) is used to define a target (TGT) location and optional Pull Up Point (PUP). This allows the creation of a target and pull up point from an Initial Point (IP) Steerpoint.

For example, let’s crate a VIP at Steerpoint 3.

• Until sequencing to Steerpoint 3 with VIP data, we would only see the Steerpoint diamond on the HUD/HMCS to direct us to the next Steerpoint; we would not see the Steerpoint 3 VIP TGT and PUP symbols. Additionally, the sighting option will stay as TGT.
• Upon selecting Steerpoint 3 (AUTO or Manual), the Steerpoint diamond on the HUD/HMCS will be at the Steerpoint 3 location. The Steering Option will automatically change from TGT to IP.  TGT (square and dot) and PUP (circle) symbols would now be visible on the HUD/HMCS.
• Once over the IP at Steerpoint 3 (overfly point) and HUD is SOI, TMS Forward is pressed to update the steering to the VIP TGT. The Steering Option changes from IP to TGT and the steering symbology (azimuth steering line) is regarding the created VIP TGT location.
• With the HUD still as SOI the cursor switch can be used to slew the VIP TGT point.
• If a PUP (circle) is also created, it would also be visible but no steering information regarding it is visible.
• If we were to then cycle to Steerpoint 4, or any other Steerpoint other than Steerpoint 3, the TGT and PUP symbols assigned to Steerpoint 3 would no longer be visible.

Steps:

Let’s use the example:

1. Select AG mode
2. Select CCRP or CCRP-related bombing sub mode like LADD or an E-O Pre mode
3. LIST from ICP
4. 3 from ICP
5. On the VIP DED page, the top line, VIP-TP-TGT is selected. Press M-SEL on ICIP to enable. It will then be highlighted. Without it being enabled, data entry will not be saved.
6. DCS switch down to select Steerpoint to create the VIP from. Once selected, use the ICP rocker switch to select the desired Steerpoint from which to set the VIP TGT and PUP.
7. DCS switch down to the enter the bearing in degrees on the ICP from the selected Steerpoint to the desired Target (TGT) location. Press ENTR on the ICP to save it.
8. DCS switch down to enter the range in nautical miles from the selected steerpoint to the target location. Press ENTR on the ICP to save it.
9. DCS switch down to enter the elevation in feet at the target location. Press ENTR on the ICP to save it.

At this point, the bearing and range from the selected Steerpoint to the Target point is set and includes a target elevation. The user can now optionally include a Pull Up Point (PUP). To do that:

1. DCS switch to the left to select PUP data entry
2. DCS switch up or down to select VIP-TO-PUP top line and then press M-SEL on the ICP to highlight it
3. DCS switch down to select Steerpoint to create the PUP from. Once selected, use the ICP rocker switch to select the desired Steerpoint.
4. DCS switch down to the enter the bearing in degrees on the ICP from the selected Steerpoint to the desired PUP location. Press ENTR on the ICP to save it.
5. DCS switch down to enter the range in nautical miles from the selected steerpoint to the PUP location. Press ENTR on the ICP to save it.
6. DCS switch down to enter the elevation in feet at the PUP location. Press ENTR on the ICP to save it.

VRP. In this mode, we can set a Reference Point (RP) from a known Steerpoint that is also the Target (TGT) Point. As with VIP, we can also create a PUP. This allows the creation of a run-in point based on a bearing and range from a selected Steerpoint that is also the TGT.

For example, let’s crate a VRP at Steerpoint 3.

• Until sequencing to Steerpoint 3 with VRP data, we would only see the Steerpoint diamond on the HUD/HMCS to direct us to the next Steerpoint; we would not see the Steerpoint 3 associated VRP RP, TGT, and PUP symbols. Additionally, the sighting option will stay as TGT.
• Upon selecting Steerpoint 3 (AUTO or Manual), the Steerpoint diamond on the HUD/HMCS will be at the Steerpoint 3 VRP RP location. The TGT symbol will be at the Steerpoint 3, and the PUP symbol would be visible if created. Steering option is set to RP and HUD steering (azimuth steering line) is in reference to the RP location.
• Once over the RP (overfly point) and HUD is SOI, TMS Forward is pressed to update the steering to the VRP TGT. The Steering Option changes from RP to TGT and the steering symbology (azimuth steering line) is regarding the created VRP TGT location (Steerpoint 3).
• With the HUD still as SOI the cursor switch can be used to slew the VRP TGT point.
• If a PUP (circle) is also created, it would also be visible but no steering information (ASL) regarding it is visible.
• If we were to then cycle to Steerpoint 4, or any other Steerpoint other than Steerpoint 3, the RP, TGT, and PUP symbols assigned to Steerpoint 3 would no longer be visible.

Process

Let’s use the example:

1. Select AG mode
2. Select CCRP or CCRP-related bombing sub mode like LADD or an E-O Pre mode
3. LIST from ICP
4. 9 from ICP
5. On the VRP DED page, the top line, TGT-TO-VRP is selected. Press M-SEL on ICIP to enable. It will then be highlighted. Without it being enabled, data entry will not be saved.
6. DCS switch down to select Steerpoint to create the VRP from. Once selected, use the ICP rocker switch to select the desired Steerpoint from which to set the VRP RP and PUP.
7. DCS switch down to the enter the bearing in degrees on the ICP from the selected Steerpoint to the desired Target (RP) location. Press ENTR on the ICP to save it.
8. DCS switch down to enter the range in nautical miles from the selected steerpoint to the RP location. Press ENTR on the ICP to save it.
9. DCS switch down to enter the elevation in feet at the target location. Press ENTR on the ICP to save it.

At this point, the bearing and range from the selected Steerpoint to the RP point is set and includes the RP elevation. The user can now optionally include a Pull Up Point (PUP). To do that:

1. DCS switch to the left to select PUP data entry
2. DCS switch up or down to select TGT-TO-PUP top line and then press M-SEL on the ICP to highlight it
3. DCS switch down to select Steerpoint to create the PUP from. Once selected, use the ICP rocker switch to select the desired Steerpoint.
4. DCS switch down to the enter the bearing in degrees on the ICP from the selected Steerpoint to the desired PUP location. Press ENTR on the ICP to save it.
5. DCS switch down to enter the range in nautical miles from the selected steerpoint to the PUP location. Press ENTR on the ICP to save it.
6. DCS switch down to enter the elevation in feet at the PUP location. Press ENTR on the ICP to save it.

[NineLine]

In earlier videos we looked at the upcoming Destination Page, Primary Datalink Track, and completion of Offset Aimpoints and Visual Initial and Reference Points. In this Viper update video, we’ll touch on some of the other changes coming to the Viper. Some of these will be in the next update, but some may come a bit after based on testing results.

The first is an update to the symbols on the Fire Control Radar, or FCR, and the Horizontal Situation Display, or HSD. The symbols are now governed by the simple rules of:
If your sensors detect the contact, the symbol will be solid. If your sensors do not detect the target and the source is only over the datalink, it will be hollow.
Unknown contacts will be white, ambiguous contacts will be yellow, green contacts are friendly, and red contacts are deemed hostile. It’s important to note that for this year of the Viper AIFF is not correlated to radar track files. As such, if you interrogate a contact, it will have no impact on its Rules of Engagement, or ROE, symbol.

From the HUD control panel by your right knee, we have added selections for True Airspeed and Ground Speed. Ground Speed will be important for the upcoming Cruise Page for May. It’s quite possible that this will be released in the May update.

With a bomb called up on the Stores Management Page, or SMS, and you select the Control page, we now have additional fuze options. This is the part of a much larger task, but you’ll now be able to set both an arming time after separation and an arming time after weapon impact. Set the arming at release time at AD and set the weapon fuze detonation time at AD2.
If the AD value is equal to or greater than the weapon time to impact, “LOW” will appear to the right of the Flight Path Marker (FPM).
For non-JPF fuzes, we plan to later set fuze values on kneeboard prior to flight, and DTE when implemented.

Additional Cursor Zero, CZ, options have been added to both the FCR and Targeting Pod pages when powered off. 

When using a Maverick, you can now press the Cursor Enable button on the throttle to cycle between Visual, Pre-Planned, and Boresight modes. Press the enter button to cycle the options.

There are of course many other smaller changes and those will be listed in the change log.

[BIGNEWY]

In this DCS: F-16C Viper video, we’ll explore the Cruise page. The Cruise page is a handy page to hit your targets on time and most efficiently fly the aircraft regarding range, endurance, and getting home.

[BIGNEWY]

In this DCS: F-16C Viper video I don’t have a new feature to talk about, but rather an important improvement to the Horizontal Situation Display, or HSD, and the HARM Attack Display, or HAD. The expand mode, or EXP, will allow you to zoom in on the HSD and HAD.

Let’s first look at Expand on the HSD. With the HSD selected as our Sensor of Interest, or SOI, we can position the HSD Cursor where we wish to expand the HSD. We can expand by either pressing OSB 3 or pressing the Expand, Field of View button on the control stick for less than half a second. Expand defaults to the Normal level, with the first press selecting EXP1 for a 2 to 1 expansion and a second press selects EXP2 for a 4 to 1 expansion. A third press cycles back to normal with no expansion.

The HSD EXP modes are very useful when you have several HSD symbols close together.

If you press and hold OSB 3 or the Expand button on the stick for greater than half a second, the HSD goes into Zoom mode, as indicted by the flashing Zoom label at the top of the HSD. If you have flight members, the HSD will select the smallest range to display all flight members. This can be as low as a 5 nm range, and it is useful to quickly understand where all flight members are in relation to you.

If there are no flight members, the HSD will be set to 5 nm around your aircraft.

Expand mode on the HARM Attack Display is very similar. When the HAD is your Sensor of Interest, indicated by the white box around the periphery, you can slew the HAD cursor anywhere on the HAD and either press OSB 3 or the Expand Field of View button on the control stick to cycle between Normal, EXP1, and EXP2. Note that there is no Zoom function when using the HAD.

Like Expand on the HSD, the Expand function on the HAD is very useful to designate a target when you have a group of clustered indications on the HAD.

[Wags]

Dear all,

 Although we released a large and well-received flight model and flight control system update earlier, we have not been sitting on our hands. We will soon be further improving these aspects of the Viper.

•  You will be able to attain up to -3.4G. Bring on the creative jinks!
•  Removed FLCS flight transition mode between gear down and gear up. Nose will be rock steady. Same holds true if you get slow and the flaps come down. This results in a much more stable nose pointing in a fight.
•  DFLCS roll rates have been improved/increased.
•  The yaw oscillation when on the deck at high speed is a memory.
•  With sufficient energy, the Viper will now hold 9.3G.
•  Gear down / AAR door open roll gains have been adjusted to be more accurate.
•  Takeoff and landing mode FLCS gains have been improved.
•  DFLCS gun compensation has been improved in roll and yaw when slow.
•  Manual Pitch Override (MPO) switch will override the negative G limiter.

 Kind regards,

Wags

 

[BIGNEWY]

In this DCS: F-16C Viper video, we’ll talk about the use of the GBU-24/B Paveway III laser-guided bomb with the Viper. Like the GBU-10, the GBU-24 also uses a 2,000 lbs. class warhead, but it has a much more advanced autopilot and larger control surfaces that allow a greater standoff range of greater than 11 miles when dropped high and fast. Lower and slower will result in a reduction in range of course.

The bomb can be carried on stations 3, 4, 6, and 7.

Once dropped, the GBU-24 can pitch up, termed a bump up, to climb and increase range.

Like all laser-guided bombs, it will require laser designation of the target from your own targeting pod or a remote laser-designation source.

We will first select Air-to-Ground mode from the ICP. On the Stores Management System, or SMS page, we can see that we have two GBU-24s selected at OSB 6. Also, on the right side of the page, we can cycle between four different release profiles at OSB 7. At OSB 8 we can release the GBU-24 as a single or in pairs. At OSB 10 is the Ripple Release Internal. We’d only use this when releasing more than one GBU-24 at a time, and it would be used to set the release time between drops from 50 to 500 milliseconds.

On the left side, RBS at OSB 20 and Mode at OSB 21 are not functional due to lack of public information. From OSB 18, you can cycle the fuze between Nose, Tail, and Nose Tail. Below that at OSB 17 you can select the Arming Delay with successive pressing of the OSB to cycle through the pre-set options in the center of the page.

Along the top at OSB 2, you select between Pre-Planned (PRE), in which the delivery is based on the current Sensor Point of Interest that could be a Steerpoint, Offset Point, A-G FCR designation, TGP designation, etc., or Visual (VIS) mode in which you can slew the designation box on the HUD and press TMS Forward to set the designation point.

As a laser-guided bomb, we’ll need to make sure that the bomb seeker is looking for the same frequency as the designating laser. Press the K on the keyboard to view the bomb seeker code. In this case, 1688. To check in reference to the targeting pod, press LIST on the ICP, then M-SEL, and then 5 for Laser. We can see that the TGP will be designating at 1688. If you wish to self-designate, these must match.

More options are available on the Control page at OSB 5. Alongside OSB 6, is the estimated weapon Time of Flight, this cannot be edited. At OSB 9, we can input the range at which the Range Cue is displayed on the HUD as a small circle. Let’s set it to 8 miles. Note the indication changes on the HUD. The desired release angle can be set at OSB 10. We’ll do a level release with an angle of zero.

The SMS page is set up, let’s explore the HUD now. Because we are in PRE mode, we can see the box and dot that indicates our target SPI location and the Azimuth Steering Line, or ASL, that provides us azimuth steering information to the target. We want to fly the aircraft such that the ASL intercepts the SPI indication. Along the ASL is Release Cue that appears as a thicker horizonal bar. As we approach our maximum release point, the Release Cue will march down the ASL until it intercepts the Flight Path Marker. Prior to the two reaching each other, hold down the weapon release button and the bomb will automatically release when the two symbols coincide.

Along the right side of the HUD is the GBU-24 dynamic launch zone. It is indicated as a 20-mile scale with a bar and “20” at the top. To the left side of the DLZ is a caret that indicates current range to the target. As we close on the target, the caret will move down the DLZ. 

Further down the DLZ, we have an open bracket to the right, and this the current range of the GBU-24 based on current aircraft flight conditions. The closed bracket below that is the planned range based on the inputted SMS data.

With everything set up, don’t forget to arm the laser.

At the bottom of the data block in the bottom right of the HUD, we can see the estimated Time to Release. Once the bomb is released, it counts down to estimated impact at zero.

[Wags]

Manual Bombing Mode

Coming in the next Open Beta update will be the addition of the Manual (MAN) bombing mode. I lacked the time needed to create a video on this, so please accept this text instruction.

Manual weapon delivery provides the capability to release conventional weapons and rockets when trajectory calculations are not performed or when conditions exist which prohibit computed nonmanual) releases. For conditions when aiming symbology and delivery cues are not available on the HUD, delivery can be achieved by using the HUD primary or standby depression reticle. Manual mode bypasses all calculations of the MMC and releases the weapon(s) immediately at WPN REL button depression, provided MASTER ARM is selected.

The primary reticle consists of two solid concentric circles 50 mR and 100 mR in diameter with a 2 mR dot in the center. The standby reticle consists of two concentric dashed circles 50 mR and 100 mR in diameter with a 2 mR cross in the center. Both are selected via the HUD Control Panel. Reticle depression can be varied from 0 to 260 milliradians and is controlled by a thumbwheel knob on the ICP. The depression angle is displayed on the HUD (lower left side) in milliradians. The reticle depression knob has two detent positions:  one at the gun boresight (0 mR depression) and one at the missile boresight (52 mR depression). All other HUD symbology is blanked when the standby reticle is displayed.

The BRT knob on the ICP must be off for the standby reticle to be visible.

Manual weapon delivery consists of selecting the MAN delivery option on the SMS format, manually depressing the reticle to the depression angle associated with the planned release parameters, achieving the planned release parameters while at the same time ensuring that the reticle coincides with the target, and depressing the weapon release button.

When the entered release pulses are greater than one on the MFDS SMS page, the release interval will appear directly above the release pulse (RP) setting. A range of 0.000 to 4.000 seconds can then be entered for the release interval.

If the manual weapon delivery option is selected, the MMC displays navigation mode symbology on the HUD. Depressing the MSL STEP button will select the CCIP submode. If rockets is the selected weapon and the delivery mode is manual, depressing the missile step push-button selects the CCIP-Rockets delivery option. Once in CCIP-Rockets, the missile step push-button will have no effect on the delivery mode.

Manual Weapon Procedures:

1. ICP - Verify A-G display.

2. MFD - Select/verify correct weapon and MAN delivery option.

3. HUD - Select/verify reticle depression and symbology.

(a) Select primary or standby reticle via HUD Control Panel.

(b) Select reticle depression in milliradians via RET DEPR knob on ICP.

4. Maneuver to planned release conditions.

5. MASTER ARM switch - MASTER ARM or SIMULATE (as desired).

6. WPN REL button - Depress.

Release occurs upon depression of WPN REL button regardless of release conditions required for accuracy.

[BIGNEWY]

DCS: F-16C Viper | Navigation Updating with FIX Taking

Our next step for the Viper is to include methods to check and update the location of steerpoints within the navigation system. This will include fix taking from the FIX DED page and altitude calibration from the A-CAL DED page. For this fist video, we’ll discuss fix taking.

If you have a long flight in which you may encounter navigation drift, it’s a good idea to have some geographic landmarks along the way to act as fix points to update the location of your steerpoint accuracy.

From the ICP, select FIX at button 8 and the FIX DED page is displayed. Using this page, we can select a location designation source that we can compare to the location of the selected steerpoint in the navigation systems. Using the DCS switch, or Dobber switch, right, we can cycle through the available location designation methods of overfly, fire control radar, HUD, and targeting pod. Below the designation source is the selected steerpoint that we will compare against, and below that is the location distance between the two. The bottom two lines indicate the navigation and GPS level of accuracy.

In the below examples, you will want to consider a fix point, possibly your initial point, to confirm that that there is no steerpoint drift in the navigation system.

Let’s look at each fix method and start with overfly.

Steps:

1. DCS switch right until OFLY is selected
2. Increment and decrement rocker can be used to select the steerpoint to update
3. Verify Steerpoint to update on the FIX DED page
4. When over the location to update, press TMS Forward
5. Check delta value on the FIX DED page
6. Press and release the ICP ENTER button to update. This will also deselect the FIX DED page
    

Next, let’s take a fix position using the FCR. To do so:

1. HUD to NAV Master mode
2. Select FIX DED page
3. DCS switch right until FCR is selected
4. Verify Steerpoint to update on the FIX DED page
5. Select Sighting Option (STP, OA1, OA2, etc.)
6. Slew FCR cursor over correct STP location and TMS Forward to FTT. This will freeze the FCR
7. Check delta value on the FIX DED page
8. Press and release the ICP ENTER button to update. This will also deselect the FIX DED page
    

The next method is using the HUD for a visual update.

1. HUD to NAV Master mode
2. Select FIX DED page
3. DCS switch right until HUD is selected
4. Verify Steerpoint to update on the FIX DED page
5. Select Steering Option (STP, OA1, OA2, etc.)
6. Slew HUD diamond over correct STP location
7. Check delta value on the FIX DED page
8. Press and release the ICP ENTER button to update. This will also deselect the FIX DED page
    

The final method is using a targeting pod if equipped.

1. HUD to NAV Master mode
2. Select FIX DED page
3. DCS switch right until TGP is selected
4. Verify Steerpoint to update on the FIX DED page
5. Select Steering Option (STP, OA1, OA2, etc.)
6. Slew TGP cursor over correct STP location
7. Press TMS Forward to designate a Point Track
8. Fire laser range finder.
9. Check delta value on the FIX DED page
10. Press and release the ICP ENTER button to update. This will also deselect the FIX DED page

[Wags]

Dear all,

Following our projects meeting today and review of the DCS: F-16C Road Map, we have decided to return several items to the planned features of Early Access release.

https://forum.dcs.world/topic/278635-dcs-f-16c-viper-roadmap/

These include:

• Sniper XR Targeting Pod.
• RWR Handoff PRF Tones.
• Radar Velocity Search Mode.

Whilst Date Transfer Cartridge (DTC) and Mission Planner is on the Road Map, this is a much larger item that is not just an F-16C item. As such, it will need to come after the module exits Early Access.

As mentioned before, once the Viper exits Early Access, we’ll release a roadmap of planned additional features.

On a different matter, we’ve been having “lively” internal discussions regarding the F-16C radar regarding detection versus bug range and the effect of radar look down angle. This has included a review of numerous documents and discussions with SMEs. We are making good progress to resolve these issues for a July update.

Kind regards,

Wags

[Wags]

Dear all,

A few, important updates:

• Based on clear language in a rather public F-16 manual, APG-68 search returns (small white square with vector line) represent only the initial radar detections that the radar has not Doppler correlated well enough to declare them to be valid radar tracks. Earlier, the time to resolve a search target to a tank target was excessive.
• The effect of radar look-down is being tuned to be less aggressive. It is now possible to have a valid track on a look-down target (MiG-29) more than 30 nm. Naturally, this greatly depends on RCS, Vc, and other factors.
• We have implemented multiplayer datalink sharing of radar contacts over the datalink of valid track targets. Earlier, this was limited to only STT targets. This essentially allows players to run radar silent and maintain SA based on flight member datalink sharing. The next step is to implement this for the AI.

It is our hope that these items will be available in the July update, but it will greatly depend on testing results and completing remaining sub-tasks.

We understand how important these items are to many of you, and I wanted to provide a little sit rep.

Kind Regards,

Wags

[BIGNEWY]

In the previous Viper video, we talked about using the FIX option on the ICP to update the Inertial Navigation System, or INS. While the onboard GPS can certainly assist with updating the INS, INS drift can still happen. This is not only true for a fix position as stored in the mission computer mission planning table, but also for altitudes. To calibrate for altitude drift, we have the altitude calibration, or A-CAL, function from the ICP.

To enable A-CAL, we’ll select button 9 on the ICP. Upon doing so, the A-CAL DED page is displayed. By default, the GPS automatic A-CAL options is enabled. This allows the onboard GPS to update elevations, or both. However, we’ll Dobber right to enable manual calibrations. If we lost our GPS or was denied in some way, this will be useful.

As with FIX, we have options to manually calibrate a steerpoint altitude by pressing ICP 0 to 9These include radar altimeter, fire control radar, the heads-up display, and the targeting pod. 

Unlike FIX, A-CAL allows us to calibrate the altitude, position, or both at the same time by pressing right on the Dobber switch. For this example, we’ll just calibrate the altitude.

If we want to go back to automatic A-CAL using GPS, Dobber down to the Manual and press M-SEL on the ICP.

First, let’s look at using the radar altimeter. We first need to determine the steerpoint altitude to calibrate as indicated in the top right corner of the DED. In this case, Steerpoint 1. The Elevation line indicates the stored mission planning table altitude for the selected Steerpoint, and below that is the difference, or Delta, between this stored altitude and the current radar altimeter indication. To calibrate using this method:

1. Select NAV master mode
2. Select A-CAL from ICP
3. Select MAN calibration
4. Verify RALT as method
5. Verify Steerpoint to calibrate
6. Verify ACAL on HUD
7. When directly over the Steerpoint to altitude calibrate, press TMS forward
8. Press Enter in the ICP to save and return the DED to the CNI

To use the Fire Control Radar as the calibration sensor, we’ll Dobber right to select it and bring up the FCR on the left MPD.

1. Select NAV master mode
2. When 10 nm or less from the Steerpoint to calibrate, select CRM and then GM FCR mode, set FCR as SOI, ensure the crosshairs are over the Steerpoint, and TMS forward to set the FTT and freeze.
3. Select A-CAL from ICP
4. Select MAN calibration
5. Verify Steerpoint to calibrate
6. Verify ACAL on HUD
7. Select and verify FCR as method
8. Press TMS forward to calibrate
9. Press Enter in the ICP to save and return the DED to the CNI

Next, we’ll use the HUD as the calibration method.

1. Select NAV master mode
2. Select A-CAL from ICP
3. Select MAN calibration
4. Verify Steerpoint to calibrate
5. Verify ACAL on HUD
6. Select and verify HUD as method
7. Set HUD as SOI
8. Use the cursor switch to slew the Steerpoint diamond on the HUD over the Steerpoint location
9. Press TMS forward to calibrate
10. Press Enter in the ICP to save and return the DED to the CNI

Last, we’ll use the Targeting Pod.

1. Select NAV master mode
2. Select Steerpoint to calibrate
3. Select TGP, set TGP as SOI, ensure the crosshairs are over the Steerpoint, and TMS forward to set as a Point Track
4. Select A-CAL from ICP
5. Select MAN calibration
6. Verify Steerpoint to calibrate
7. Verify ACAL on HUD
8. Select and verify TGP as method
9. Enable and fire the laser to create range data
10. Press TMS forward to calibrate
11. Press Enter in the ICP to save and return the DED to the CNI

[Wags]

Regarding the A-CAL AUTO ACAL GPS option, we will be further expanding this DED page to include NAV Filter accuracy, GPS accuracy, DTS, and more.

As mentioned in the video, although not a full EGI system, this option allows INS/GPS Kalman filter blending on INS position and altitude data to greatly reduce INS drift.

Kind regards,

Matt