Matt Wags Wagner
DCS: F-16C Viper Introduction
updated
In this DCS: AH-64D video I’d like to offer an example of using the FCR with radar-guided Hellfire from only the backseat. I understand that most players will primarily be using the AH-64D from just the backseat. This video builds upon the earlier FCR videos like FCR controls. I’ll continue the series of more detailed instructional videos on the FCR, but this video is designed for those of you that simply wish to run-and-gun from the backseat while raining down Hellfire.
NOTE 1. Yes, we plan to allow George to engage with the FCR, but only after we complete FCR development.
NOTE 2. We will later add LINK mode that will slave the TADS to the FCR NTS.
NOTE 3. We will add the FCR to the reloading pop-up.
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.
NOTE 5. You can also slew the HOCAS cursor over the desired target and depress to designate as the NTS. What was the NTS becomes the ANTS. Trying to designate an individual contact on the FCR page with the HOCAS cursor while flying at the same time is not recommended.
This video uses the DCS: Normandy 2 map that can be purchased from: digitalcombatsimulator.com/en/shop/terrains/normandy_2.0_terrain
NOTE. 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.
Correction: Priority Scheme A: Stationary ground targets and airborne targets are prioritized above all others.
AH-64D FCR Fire Zones: youtu.be/HJod9HL80Jc?si=Q7tLW4PSRHs9ECNt
In this DCS: AH-64D video, I’ll be going over how to configure the Fire Control Radar’s, or FCR, target prioritization and how to engage targets with our onboard weapons using FCR target data.
If you have not already, I strongly suggest you review the earlier videos on creating zones and understanding FCR pages and controls. I’ve included cards and links in the video notes.
Let’s first talk about target prioritization. In the previous video on FCR pages and controls, we discussed how to control where and when the FCR scans the battlefield. However, as mentioned in the FCR introduction video, the key aspect of the FCR is that it will automatically classify and prioritize all the targets it detects within its scan volume. So, before we initiate a scan, let’s go over the ways that we can set the target priorities for the next scan.
There are two ways to do this. The first is by setting the Priority Scheme on the FCR Utility page to A, B, or C. As mentioned in the previous video, the selected scheme is noted on the HAD
.
• Priority Scheme A: Stationary ground targets and airborne targets are prioritized above all others.
• Priority Scheme B: Stationary ground targets are prioritized above all others.
• Priority Scheme C: Moving ground targets and airborne targets are prioritized above all others.
What this means is that if there are many ground targets on the battlefield, with some moving and some stationary, stationary targets will be prioritized when selecting A or B schemes and moving targets will be prioritized when selecting the C scheme.
The other way to adjust FCR priorities is by activating Fire Zones on the TSD Battle Area Management, or BAM, page. When these zones are activated, they will also appear on the FCR page when a scan is initiated.
• Any targets that are detected within an activated Priority Fire Zone will out-prioritize targets outside the activated Priority Fire Zone.
• Any targets that are detected within an activated No Fire Zone will not be prioritized and excluded from the shoot-list, even if they are within an overlapping PFZ that is also activated.
What this means is that all the targets within an activated PFZ will be ranked using the selected Priority Scheme, A, B, or C. Once all targets within the activated PFZ have been ranked, then any remaining targets that are detected outside of the PFZ will be ranked using the selected Priority Scheme and added to the 16 target “shoot list” below those inside the PFZ.
We’ll look at a practical example of activated PFZ prioritization in a bit.
The bottom line is that there is no way to force the FCR to target a specific enemy vehicle on the battlefield, the system is not designed for that like in the F-16 or F/A-18 like a fixed target trackR; the crew can only configure how the FCR prioritizes the targets using the Priority Scheme or Fire Zones, or by narrowing the FCR scan size to a narrow sector of the battlefield using the FCR controls discussed in video #2.
Engaging a target with the FCR as the selected sight is very straightforward. Whatever target is designated by the Next-To-Shoot (NTS) diamond is the target that will next be engaged. This NTS target Range Source is displayed as the slant range in kilometers from the ownship to the NTS target.
• If missiles are actioned, that target will be handed off to the next AGM-114L radio frequency, or RF, missile.
• If rockets are actioned, the pilot will receive rocket steering to align to that target.
• If the gun is actioned, the gun will be given a computed firing solution to that target.
When an RF missile is fired, the NTS designation diamond will automatically advance to the next target in the 16 target “shoot list”. In other words, the Alternate Next-To-Shoot target will then become the Next-To-Shoot target and the next target in priority will then become the Alternate Next-To-Shoot target, or ANTS, triangle.
Selecting a target on the FCR page with the HOCAS MPD cursor will place that target at the top of the 16 target “shoot list”. However, if NTS (button L1) is pressed, this will advance the NTS designation through the 16 targets in a cyclic and repeating manner.
If the MPD cursor is on the FCR page when an FCR scan is initiated, the MPD cursor will automatically be moved to the NTS button label, allowing the targets to be cycled by pressing Cursor-Enter as soon as the first scan is completed.
NOTE. 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.
Map used: DCS: Normandy 2 Map
digitalcombatsimulator.com/en/shop/terrains/normandy_2.0_terrain
This is the second of several planned FCR videos.
You can find the text of the video here: https://forum.dcs.world/topic/280176-dcs-ah-64d-mini-updates/?do=findComment&comment=5342766
AH-64D FCR Introduction video: youtu.be/TLRC7paCeVA?si=8Jr38Urvqkh2jhYF
00:00 Introduction
00:52 FCR Controls
03:19 FCR Power
04:40 FCR as Sight
05:05 FCR Pages
07:46 FCR on TDU
09:03 FCR Scanning and Classification Symbols
NOTE. 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.
This is the first of several planned FCR video and is intended as a simple overview.
In this DCS: AH-64D video, I’m going to introduce you to the Fire Control Radar, or FCR, of the Delta. The AN/APG-78 FCR was designed to enhance the target acquisition and engagement process of the AH-64D when faced with large numbers of enemy armor units moving across the battlefield.
More than just a sensor for detecting and engaging targets, the FCR is a target classification and prioritization system that automates and accelerates the process of acquiring targets and determining which of those targets should be engaged to have the maximum effect on the battlefield with the limited number of munitions on board the aircraft. The FCR turns the Delta in a true force multiplier.
It was developed in the 1980s for the Delta as the Airborne Adverse Weather Weapon System, or AAWWS, which was part of the Multi-Stage Improvement Program, or MSIP, to enhance the AH-64A. The AN/APG-78 is a millimeter-wave FCR target acquisition system that also includes a Radar Frequency Interferometer, or RFI. The FCR is housed in a dome located above the main rotor mast. The APG-78 is capable of simultaneously tracking up to 128 targets and engaging up to 16 at once, and an attack can be initiated within 30 seconds. The datalink allows FCR data to be shared with other Deltas and allows them to coordinate attacks using fire zones.
It’s important to understand that performing a radar scan with the FCR can be thought of as taking a “photograph” of the battlefield. When multiple FCR scans are performed in succession, this is called a “scanburst”, which is like taking several photographs of the battlefield in rapid succession. It is during these photographs that the FCR is determining where the targets are, what targets are moving or stationary, and classifying each target within several target types, such as Tracked vehicles like tanks, Wheeled vehicles like trucks, Air Defense vehicles like a ZSU-23-4, or even fixed-wing aircraft and helicopters.
There are two types of scanbursts: a single scanburst and a continuous scanburst. A single scanburst takes several photographs of the battlefield and displays the state of the battlefield on the cockpit displays as a fixed, momentary snapshot in time. A continuous scanburst takes photograph after photograph of the battlefield and continues to update the state of the battlefield on the cockpit displays. Each time a new scanburst is initiated, all FCR data is deleted like throwing away the existing “photographs” and a new series of photographs are taken. This is very different than the air-to-ground radar modes that you may be familiar with like in the F-16 and F/A-18.
When a scanburst is performed, the FCR page will only display the 16 targets that have been determined to be the highest priority. It will never display more than 16 target symbols because the AH-64D can only carry a maximum of 16 Hellfires. These 16 targets on the FCR page can be thought of as a “shoot list”, with a diamond placed around the highest priority, “Next-To-Shoot”, or NTS, target, and an inverted triangle placed around the second highest priority, “Alternate Next-To-Shoot”, target.
The TSD can display more than 16 targets when set to the attack phase, but all low-priority target symbols will be displayed at half the size as the 16 high-priority target symbols.
The C-SCOPE and ZOOM functions on the FCR page are not currently implemented, nor is the LINK function on the Sight-Select switch. These will come later in early access, along with other radar modes.
That’s it for this introduction to the FCR. In the next video, we’ll explore deeper into setting up FCR pages and controls. Thanks for watching.
In this DCS: AH-64D video, we’ll discuss the creation, sending, and receiving of Priority Fire Zones, or PFZs, and No Fire Zones, or NFZs. These allow you to define areas on the TSD to assign targets to Primary members and delineate areas not to engage targets. These zones can be sent over the datalink between Primary members to coordinate fires.
From the COM page, then Preset 1 Chaos, and finally Network, we can see that we have C-2, or Chaos 1-2, on our Preset 1 as both a Primary and Team member. To exchange Zones, data linked aircraft will need to have a Primary assignment. If you have not already done so, please see the earlier videos on setting up and using the datalink.
I prefer to set my brightness knobs to maximum and the Video knobs to about the nine o’clock position. I’ll display the main TSD page on my left MPD, and from B3 on the right MPD, I’ll select BAM, or Battle Area Management. I’ll set both to Attack phase so that we can see all the BAM data. We’ll first learn how to create PFZs and NFZs.
From L1, we can elect to create PFZs or NFZs by toggling this push tile. It defaults to PFZ.
From L2, we can select how we create zones: automatic, manual, and target refence point, or TRP. When AUTO is selected, we first need to select the number of zones that will be created in the polygon we create. In this example, I’ll select 4 from L5. The number of zones will default to the number of aircraft in the flight. To draw the polygon, we can do it either as a box, or BX, or a line, or LN, from L6. Simply move the cursor on the BAM page to where you want to create the box or line and depress the cursor switch. Then, move the cursor to define the box or line segment. Depress the cursor switch again to complete the polygon. Once created, you can see that the polygon was subdivided into four, equally sized zones, in this case, PFZ 1 to 4. Let’s try this as a line now, but we’ll first select Delete from L4 to remove the one we just created. When using line, the polygon is limited to four sides, of which none can cross one another, like an hourglass.
When using the Manual, or MAN, option to create zones, we first define how many zones we wish to manually create from L5. In this example, I’ll create two manual zones. Rather than create a single zone that is then equally divided in automatic option, in manual option, I can manually create unique zones based on the number I defined, two in this case.
The third option is TRP. This will create four, equally divided zones with the size of each zone within the TRP based on the kilometer setting at L5. I can then use the cursor to position the TRP and depress the cursor switch to set it. Once set, each quadrant is automatically assigned a PF.
Pressing L1, we’ll switch from a PFZ to an NFZ, or setting a location, or locations, not to engage targets. As with PFZ, we can elect to draw a polygon using a box or line from L6. Note that it defaults to the next available NFZ number, in this case, NF1. Once drawn, press Accept to save it. We now have No Fire Zone 1, or NF1. To create another, we’ll just select L2 and select the NFZ number to set, in this case, NF2.
With PFZ selected as the Type, select T4 ASN to assign myself and Primary members PFZs. We can see that we have selections for each of the four PFZs we created, PF1, 2, 3 and 4. To assign a PFZ to myself, I’ll select the PFZ for my ownship, PF1 by default in this case, and select OWN from B6. We can see that PF1 is assigned to OWN now. Note that PFZ assignments are done in sequence, and after a member is assigned to a PFZ it will automatically advance to the next PFZ, allowing you to rapidly assign flight members.
Next in the automatic sequence is PF2, and we’ll assign this to our Primary member C-2. So, with PF2 already selected, select C-2 as the assignment. When we do that, we can see that PF2 is assigned to C-2.
Now, press SEND at R6 to send the PFZ assignment over the datalink to C-2.
To send an NFZ to a Primary member, switch the Type back to NF, select the NFZ, select the Primary member, and then select SEND.
If you wish to send both PFZ and NFZ at the same time, select the Primary member, select XMIT BOTH from B5, and then SEND.
If you are sent a PFZ or NFZ assignment, you’ll receive a white REC, or receive notification on your TSD. By selecting REC and accepting the Zone files, the assignment is then displayed on your TSD.
Note that the entire PFZ or NFZ files are sent between aircraft, which overwrites and updates the existing zones on the TSD when received. Individual zones cannot be transmitted separately. This ensures the zone locations and assignments are synchronized across all aircraft within the flight.
First, within the Options, Audio Tab, all Voice Chat options have been consolidated. Along the right, you can adjust microphone input level and decibel levels, and as before along the right, you can set Voice Chat input and output audio devices. Pressing the Start Microphone Test, you can also test your microphone levels.
One of the biggest features is the Dynamic Radio Options button. Upon pressing it, we can select an aircraft in the top left of the page and then view the associated radios below it. For instance, if I select the AH-64, we see its five associated radios. If we select one, its properties are listed on the right side of the window. Clicking in the Sound Filter Options button at the bottom of the window, we can view the sound filter options for the selected radio with the ability to test it.
In addition to these defaults, you can also edit existing radios and even create new ones. In the bottom left corner, we have the option to Create New Radio. You could first select an existing radio and save it or create a new one from scratch using the windows along the right side of the window. Or you could important an existing radio to the selected aircraft. This is a very powerful tool that allows the creation of radio effects across a broad range of eras.
Use of modified and created radios are server enforced.
Coming back out to the Audio tab, be sure to check the Voice Chat and TURN-Servers for Voice Chat boxes to use Voice Chat.
Next, selecting the Controls Tab, we can set up our input controllers to use Voice Chat. We can do so through individual aircraft, or the Voice Chat drop downs. Using the example of the AH-64 Pilot, we’ll select Cyclic to transmit over the selected radio or the intercom over Voice Chat. On the Actions list, we have PTT/RTS Switch – RADIO (VOIP) to transmit over the selected radio using Voice Chat and PTT/RTS Switch – ICS (VOIP) to transmit over the intercom. VOIP stands for Voice Over Internet Protocol, and map these to transmit based on your aircraft radio settings.
Scrolling to near the bottom of the Controls list, selecting Voice Chat provides a wealth of Voice Chat radio options that you can bind. This allows you to set radio binds for Flaming Cliffs 3 aircraft. The two most important are at the very bottom. Show Voice Chat Window allows us to toggle on an off the Voice Chat window whilst in a mission and the Voice Chat Push-to-Talk Mic. Mode: On/Off Voice Transfer will allow us a Push To Talk, or PTT, option to transmit over a selected Common, Coalition, or Private Room.
Now that we’ve covered the basics of setting Voice Chat up, let’s look at it in operation.
First, based on the control input we set, enable the Show Voice Chat Window. Here with the AH-64, we have five Integrated Radio Units, the same ones we saw earlier, and the intercom. For all the radios, we can see the currently selected channel and frequency. If we change these in the aircraft, we can see them reflected in the Voice Chat window. We also can enable encryption and set the secure voice channel. This allows you to transmit between coalition members on the same encryption that will not allow the opposing coalition to listen in on. This interface is optional.
To Voice Chat transmit, simply press, and hold the selected radio transmit switch we defined earlier and speak into the microphone. When transmitting, the yellow box will turn green or red if there is no recipient, like in this case.
Along the top of the window are Radio Push-To-Talk, or R PTT, and Intercom Push-To-Talk, or or PTT. If you are in an aircraft with multiple player positions, you can also use the intercom transmit switch to speak with other aircraft members. If you are in a single seat aircraft though, I PTT is grayed-out.
Clicking on the antenna icon allows us to select chat rooms using Voice Chat. These include a Common room for all players in a mission, Coalition for just your side, and you can create private rooms. To create a private room, type in the name of the Private room in the bottom dialog box, and then press the plus sign to add members. Upon selecting one of these, you will see the participants listed. You can delete or remove yourself from a room by selecting the red trash can. Along the top, you can click the centered box to toggle between a hot mic, or Mic On, Mic Off, and Push-To-Talk based on the room chat transmission binding we set earlier.
That’s an overview of how to use the Voice Chat in DCS 2.9, but it is not the end. We will continue to refine Voice Chat with more options like interfacing with popular user-create mods.
In this rather short DCS: AH-64D video, we’ll look at sending and receiving Fuel, Ammo, Rockets, and Missile, or FARM, reports over the datalink to Primary members. If you have not already watched them, I recommend look at the datalink set up and datalink messaging videos.
Once again, I have Chaos 1-2 joining me to demonstrate this capability.
Let’s first check our datalink Preset by calling up the COM page, then the desired Preset, and then Network. We can see C-2 listed as both a Team member and a Primary member. To exchange FARM reports, we’ll need to make sure he’s set as a Primary.
The next step is to verify that we have the Datalink transmit symbol set to the radio we intend to use to transmit the FARM report. You can see here that the VHF radio has been manually tuned to the same frequency that our wingman is monitoring, signified by “MAN” next to the frequency. However, we can also see that L1 is not displayed next to the VHF radio, meaning the datalink is not capable of transmitting or receiving datalink messages. The datalink will only work if a Preset is tuned.
Back on the COM page, we will ensure that our desired Preset is selected. When a preset is selected, a list of available radios will be displayed along the top of the MPD for us to choose from. I’ll select VHF as the radio I wish to tune to this Preset, and now we have several more options along the bottom of the COM page, allowing us to decide how we will tune this Preset to the radio.
We could choose to place the Preset in the Standby slot of the VHF radio by toggling the TUNE option from Primary to Standby, but for now, I’ll just leave it set to PRI.
All that is left now is to press the button under SC, or Single Channel, to tune the VHF to this frequency. We can now see that the Preset is tuned to the VHF radio, along the Preset callsign of “Hammer” and L1 in the VHF primary slot.
Next, let’s send Chaos 1-2 our FARM report first. Select Reports from the TSD and then select FARM. We can then select our Primary members to send it to, in this case, C-2. Now we just select Send over the VHF to Preset 1.
We can also of course request FARM reports from Primary members. To do that, select Reports, FARM, and set Message to Request. We then select the Primary members and then select SEND.
Once we receive the data, we can view it on the COORD page. From the COORD page, select FARM along the bottom. We can now view received FARM reports, with each listing left to right their callsign, time of reception, fuel level, gun rounds remaining, rockets remaining, radar-Hellfires remaining, and laser-Hellfires remaining.
This is the Basic level. Selecting the Type along the bottom, we can view the Primary members expendables like chaff and flares. From left to right: callsign, time of reception, remaining flares, remaining chaff, and other.
If we select Type again, we view more detailed missile data. From left to right: callsign, time of report reception, total number of missiles, remaining radar-Hellfire, remaining SAL1 laser-Hellfire, remaining SAL2 Hellfire, and other.
If we select Type again and select PP, we can view the 3-dimensional location of our wingman when he sent the FARM report. From left to right: callsign, time of report reception, coordinates, and altitude above sea level.
Selecting Type again brings us back to the Basic level.
It can detect laser threats from 360 degrees around aircraft, just like the Radar Warning Receiver. When a laser strikes the laser warning sensors, the laser is categorized as either a rangefinder, a designator, or as beam-riding guidance.
The laser warning system is integrated with the RWR as the combined “RLWR”, or “Radar/Laser Warning System”, and laser threats are displayed as “snowflake” symbols along with the radar symbols on either the TSD page or on the ASE page. When a laser threat is displayed, audio alerts will also warn the crew of the laser threat type and direction, just like the RWR.
• Rangefinders show as a snowflake with a box around it
• Designators show as a snowflake with a box around it and a dashed line to the ownship
• Beam-riders display the same as Designators but with a flashing box
Since the RLWR is limited to just 7 symbols of the highest priority threats, the laser threats will be prioritized along with the radar threats so that the most critical threats are displayed to the crew. This means that if a tank is lasing the aircraft with just a rangefinder while several radar threats are locked on to the ownship or launching missiles at it, the rangefinder may not be displayed if the number of higher priority threats is 7 or more.
A few more points before we see this in action:
• Rangefinders are considered Acquisition-level threats
• Designators are considered Track-level threats
• Beam-riders are considered Launch-level threats
This is how they are prioritized along with the radar threat counterparts.
We also understand that many of you are looking forward to the Fire Control Radar, or FCR, for the AH-64D. This is being done in parallel by our radar team, and they are making great progress. In fact, I’m sure most of you have noticed the previews. While it is not planned for the 2.9 update, it will not be long after it. We will first release it with Ground Target Mode, or GTM, and this will allow you to detect, track, and engage units. It will also tie into datalink capabilities of sending and receiving Priority Fire Zones and No Fire Zones between Primary members.
NOTE 2. From the RPT sub-page of the TSD, you can elect to set the REPLY to automatically (AUTO) send data that is requested of you from other network members, or you can set to OFF and manually reply with the requested data.
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.
The first type of data to discuss is sending and receiving messages through the COM page. Select COM and then SEND from the Message (MSG) options along the bottom. We now have three options, send a text message, send current mission data, or send either Mission 1 or Mission 2 data.
To send a text message, select TEXT from the top row and then you can choose to send a Mission Planning System, or MPS, preconfigured message, or a FREE text message. To send an MPS message, select the push tile next to the message you wish to send, and then select SEND. It will then send this message to all Team members within the Gunslinger, Preset 1, network over the selected radio on the EUFD, in this case the VHF. To send a free text message, select FREE and you’ll then be able to compose a message of four lines using the keyboard unit. As you might imagine, the TEXT 1 to 4 allows you to compose each line, with a maximum of 44 characters in each line. Once satisfied with your witty message, select SEND to push over the selected radio and team member network as set on the EUFD, box.
If you wish to send over a different radio, use the rocker on the far left to move the box symbol to the radio that you wish to transmit over. Note that you will be listening on all the radios based on the selected frequencies.
If though you send a message and a recipient aircraft’s modem does not acknowledge its reception, you’ll see an XMIT NAK and the transmitting radio message on the EUFD. This means that the transmission was not acknowledged, which may be caused by terrain blocking the line-of-sight to the recipient, or if that recipient isn’t monitoring that frequency for datalink messages.
In addition to sending messages, you can also receive them. When you receive an MPS or FREE message, you’ll see a notification on the EUFD and an REC, or Receive, option will appear next to SEND within the MSG bracket on the COM page. Upon selecting REC on the COM page, the list of received messages is displayed, and you can select them to review them.
Pressing COM, we will select SEND again, but this time select Current Mission. From here, we can select our entire Waypoint and Hazard file, our entire Targets and Threats file, or our entire Control Measures file, Laser Codes, Routes, or All to our Team members on the Gunslinger network over the selected radio, in this case VHF to L1, Preset 1 Gunslinger. For example, if I have numerous Targets created, I can select TGT-THRT from our SEND Current Mission page and press SEND to provide all Target points at once to each Team member within the Gunslinger network.
The first report we’ll discuss is Present Position, or PP. This is the current location of our helicopter and those of our Primary members. As mentioned earlier, this is a static position that is not continually updated. For it to update, you’d need to send a new one that would replace the prior one. To send our PP, we select RPT, or Reports, select PP, and then select SEND to L1 over the VHF.
If wish to request a PP from our Primary members, we select Report, select PP, and at the bottom where is says MSG for Message, toggle that from SEND to Request, or RQST. As before, then press SEND and all Primary members will send you their current PP.
Before leaving Reports, one last item to note is that we can select our aircraft to automatically reply to the receipt of data by setting REPLY to AUTO, or if we want to reply to it only manually, we can set it to OFF.
Last, we can also send individual Waypoints, Hazards, Control Measures, or Target-Threat points on our TSD to Primary members. To do so, enter the TSD POINT page, select XMIT, cursor select the point you wish to send, in this case a Control Measure, select which Primary members you wish to send it to, and then press SEND. You can also manually enter the index of the point using the keyboard using the POINT option at L1 instead of selecting it with the cursor.
If we receive a point, we’ll see a white REC on the left side of the TSD. If we select to receive that point from within the REC list, upon which pressing displays point on our TSD.
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.
NOTE 3. The next AH-64D datalink video will instruct how to transmit and receive datalink text messages, tactical reports, and points.
NOTE 4. Setting the DL check box in the ME sets the Preset to the datalink, not the aircraft.
In this DCS: AH-64D video, we’ll discuss how to datalink with other AH-64Ds in a mission. This is done over the AH-64D radios and will allow you to send TSD points, tactical reports, or text messages. This is a very powerful tool to coordinate actions.
Let’s first start in the Mission Editor where we can pre-configure our datalink networks. From the Helicopter Group window, the top portion remains unchanged. The bottom portion has new information from the Additional Aircraft Properties and Datalinks tabs.
Along the bottom portion of the Aircraft Additional Properties tab are two new entries for DATALINK. The first is the Datalink Originator ID that distinguishes data sent between networked members. Each AH-64D in mission should have a unique Originator ID. Below that is the Ownship Callsign, and like the Originator ID, this should be unique. We’ll see these later when setting up the network.
Before we discuss the Datalink tab, let’s first look at the Radio Settings tab. This lists each radio in the AH-64D and the preset channel assignments for each. As you can see, each radio can have up to 10 presets.
On the Datalinks tab we have two sub-tabs: Settings and Network.
On the Settings sub-tab, we have 10 Presets, and each can have a unique Unit ID and Callsign. We’ll see these later in the cockpit. The primary frequency assigned to each Preset is defined in the drop down for each. Along the right side are check boxes to determine if the Preset takes part in the datalink network.
The Network sub-tab allows us to view, add, or remove AH-64Ds that will participate in a Preset’s datalink network. As you can see, I currently only have myself, Chaos 11, and my wingman, Chaos 12 assigned to Preset 1, which is for “Gunslinger” battalion. I can assign Presets 1 to 10 from the top row. If I wish to add other AH-64Ds to Preset 1, I can select Preset 1 and add them as a Group or as individual Units.
Note that this datalink is different from the ones used in aircraft like the F-16 and F/A-18, and they cannot exchange data.
From the left MPD, I’ll select COM and we can see the Presets 1 to 10 listed along the right and left sides of the page with our ownship information in the center that includes the callsign CS11, for Chaos 11 and the datalink originator ID of 1 as we created in the Mission Editor. If I select ORIG ID, you can see that it displays the same information at the top left and top right. If wanted to edit this, I could select either one of these options and enter new designations for my own aircraft with the keyboard unit.
Back on the main COM page, if I select the first Preset, it then displays additional information regarding the Preset in the center, in this case the radio frequencies used by “Gunslinger” battalion. If wanted to edit this though, I could select PRESET EDIT and select UNIT ID and CALLSIGN and enter new designations with the keyboard unit. I could also select V/UHF, FM, or HF along the top row to edit the frequency data that the Preset will use when tuned to the corresponding radios.
Selecting NET from the bottom row, I can display the aircraft assigned to this Preset’s datalink network. As you can see, this matches what we set up in the Mission Editor, Chaos, and Bootleg flights. To add Saber flight, I simply select Member Directory, and select SR11 and press ADD and the same with SR12. We can now see that all six aircraft are assigned to Preset 1, Gunslinger’s datalink network.
At the top you’ll notice other options. If you select a network member and select Delete, it will remove that aircraft from the selected Preset. Selecting a network member and setting them as a Team member will allow you to send messages from that member through the COM page. If you set them as a Primary member, or PRI, you can send reports over the TSD and FCR page. Note that they are not mutually exclusive.
As mentioned, the Originator ID must be unique for each AH-64D. If you need to, you can edit you own by selecting Originator ID from the bottom of the main COM page as already demonstrated, or by selecting C/S, Callsign, or SUB at the top of the NET and entering a new designation for the network member that you have boxed in the network list.
Let’s start in the Mission Editor to see how we now set up the F/A-18’s datalink. When selecting an F/A-18C 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. Your Voice Callsign will be auto-populated here and everything else cannot be edited at this time except the Transmit Power.
The Network sub-tab is the meat of setting up the network. The top portion lists up to four 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 using the Situational Awareness, or SA, page. We’ll examine this a bit later. Along the left side of the team member number that is auto assigned. 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 eight aircraft. Like the Members list, each row displays an aircraft with its Member number, Pilot Name, Callsign, STN, and delete option. 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/A-18s.
We’ll get in the air now and look at this in action.
Looking at the SA page, you can see that I have my three Team members off my right wing, four F/A-18 donors off my left wing, and four Viper donors ahead of me. I also see four other F-16s that are not assigned to my team or donor list. Remember that team members will have an alphanumeric letter and donors will have a dot on the left side of the icon. We can place the TDC over a contract and see it’s information in the bottom, right corner.
Using the SA page, I can remove and add participants to my Team and Donor lists. For example, we’ll place the TDC over one of the F/A-18 donors and we can see that it is a donor. By selecting the DONOR label, I can remove it as a donor. I can now place the TDC over the second F-16 flight and select DONOR to assign that aircraft as a donor participant. You can do this with all networked aircraft, and it allows you to dynamically configure your network during a mission.
I hope you enjoyed this explanation of expanded datalink functionality for the F/A-18 and recognize it as a major advancement for DCS in general.
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!
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.
I hope you enjoyed this explanation of expanded datalink functionality for the Viper and recognize it as a major advancement for DCS in general.
digitalcombatsimulator.com/en/shop/modules/viper
Purchase DCS: F/A-18C
digitalcombatsimulator.com/en/shop/modules/hornet
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.
In this DCS: AH-64D video, we’ll delve into the ability of the AH-64D to search for, acquire, and track a laser designation that is not from our own aircraft. This could be another aircraft, a UAV, or a Joint Terminal Attack Controller, or JTAC. Laser Spot Tracking, or LST, is a useful feature when you have an offboard designation source at your disposal.
As you might imagine, we first need to determine what laser code the LST will search for. This is done by selecting the WPN page and then CODE sub-page. From there, select the SET LST and pick the channel to search for A to L. Valid LST frequencies range from 1111 to 1788.
LST operations are conducted from the CP/G seat with the right handgrip. Specifically, the Laser Tracker Mode Switch. It has three positions:
When set forward to A for Automatic, commands the TADS to inhibit the LRFD from firing and conducts a 4-bar LST scan along the azimuth of the TADS line of sight. If the set LST code is detected in the scan, the TADS line of sight will slave to it. If the LST track is lost, the TADS will revert to the 4-bar raster scan.
If set to the center, off, position, LST is disabled and the LRFD can fire.
The aft, manual, position enables LST and disables the LRFD while allowing you to manually steer the LST search area. Once a matching LST code is detected, the TADS line of sight will slave to it.
Let’s try this in operation now based on a JTAC designation.
First, I’ll select LST from Code and select channel R, 1788, as my LST channel to search for. Back on the Weapons page, you can see that I have my LST window set as R.
I’ll set my TADS as the sight and place its line of sight in the general area of the target. I’ll then press forward on the Laser Tracker switch to enter automatic mode.
If you select the Slave button, the TADS will be slaved to the acquisition source and cease an LST search or track.
You can use the LST while tracking a target using the IAT and MTT functions, but the LST functions overrides those of the IAT. The TADS will continue to maintain an image auto-track on all primary and secondary MTT tracks while performing LST functions, but if those tracks remain outside the TADS field-of-view for too long, they may be dropped. However, if the LST loses the laser spot it was tracking while in manual mode or the LST is switched to Off, the TADS will slave back to the IAT primary track if it was able to maintain an auto-track on it.
Map used: Upcoming DCS: Sinai.
In this DCS: AH-64D video, we’ll talk about the radar-guided version of the Hellfire missile, the AGM-114L, otherwise called the Lima. Unlike the AGM-114K which is laser-guided and requires a laser designation until impact, the Lima is a much deadlier weapon that is fire-and-forget thanks to the millimeter wave radar seeker in the nose of the missile. This allows rapid engagements and launch-and-leave capability. Just like the Kilo, we can engage the Lima in either LOAL or LOBL modes.
As with the Kilo, it has the same warhead and range. You can also load a maximum of 16 Limas in beast mode. Externally, the Lima can easily be told apart from the Kilo thanks to its white nose cone.
When the Fire Control Radar, or FCR, is later added, the Lima will truly be a wish-you-dead weapon.
We are currently holding at a Battle Position with a hostile tank company and air defense unit off our nose. To configure the aircraft for Lima shots, let’s first do the following:
• I prefer to use the TEDAC, so I’ll set TADS as the sighting system and remove the HDU.
• Arm the weapon systems.
• Action missiles.
• Make sure the missile Type is set to Radio Frequency, or RF.
• From MODE, we can either keep in NORM, or Normal mode, in which the next missile will cycle automatically or MAN, or manual selection.
• The missile power ALL selection allows all radar Hellfires to be powered on, AUTO cycles the missile power between individual missile stations as needed to avoid overheating, and NONE powers them all down.
If LOBL Inhibit is selected, boxed, it prevents the missile from transmitting while on the rail, and would force a LOBL shot to be a LOAL shot. The 2nd Target Inhibit has to do with the FCR that we’ll talk about later.
Missile icons with an inverted chevron symbol on the nose indicate a radar-guided Hellfire, which distinguishes them from the laser-guided Hellfires which are marked by a pair of horizontal lines. Missile icons that are green with an “R” indicate radar Hellfires that have been powered on and are Ready for a target. When they are WAS’ed, they will become solid green. When an icon is white and flashing, it is cued to fire next and ready.
As with the Kilo Hellfires, we can launch either as Lock On Before Launch (LOBL) or Lock On After Launch (LOAL). It’s important to understand that if the target is 2,500 meters or closer, or if the target is moving, LOBL will automatically be used. If the missile cannot attain a lock though, it may revert to LOAL. If the target is over 2,500 meters away and stationary, LOAL will automatically be used. As noted earlier though, we can inhibit LOBL and force LOAL.
LOBL with Limas is much the same as Kilos. In this example we’ll be using the TADS as the sight. Slew the TADS over the desired target and press and hold the 2nd detent of the laser switch, which generates a target location to hand over to the missile. When the TARGET DATA? on the TDU is removed, you no longer need to continue lasing. This indicates that the location of the target has been sent to and stored on the Lima. If you are in constraints, indicated by the large, solid constraint box, launch the missile. Once launched, you can move on to a different target or find cover.
It is worth noting, that once you give a target to the Lima with the TADS, you cannot designate a different target if you decide not to launch. However, you can de-action the missiles and then re-WAS, which erases the target from the missile’s memory, and then designate a new target.
If, however, the target is outside of 2,500 meters and stationery, you will be forced to LOAL and the related smaller constraints. Once launched, the Lima will fly to that location of the designation and search for the target on its own. Much like an AIM-120 air-to-air missile. Once launched, you no longer need to track the target.
In this DCS: A-10C II Tank Killer video, we’ll discuss the very basics of using the new ARC-210 radio. There is a lot of detail in this radio, particularly the menu system, but you’ll read about this in the manual. For this video, we just want to go over the basics to get you started.
The ARC-210 supports both UFH, VHF, and satellite communications, but support for satellite communications will come later along with other aircraft satellite radio communications. The control head is located on the left console, and it replaces one of the two VHF radio control heads. This leaves on VHF, one UHF, and one ARC-210 control head.
Let’s look at the most common functions that you’ll use on the control head.
In the bottom right corner of the control head is the Frequency Mode dial.
The Preset, or PRST, position that allows you to select a preset with its assigned frequency. On the display, the selected Preset channel is shown in the top right corner and the assigned frequency to that Preset is centered in the bottom of the display. Above the frequency is the AM or FM modulation indication.
The Manual, or MAN, position that allows you to manually enter a frequency using the five Frequency Selector Knobs. Also, to the left of the display are three line select buttons. If you press the top button, it will select the previously selected frequency.
The last two positions allow you to tune the radio to either the 243 MHz or 121.5 MHz guard channels.
To the left is the Preset Channel dial. If the Frequency Mode dial is set to Preset, rotating this dial allows you to cycle through the Preset channels.
In the bottom left corner is the Operational Mode dial. This can be set between OFF, Transmit and Receive, Transmit and Receive while doing the same on the two Guard channels, and changing your channel presets. To change the frequencies of your presets, the Frequency Mode Dial must be in the Preset position and the Operational Mode Dial must be in the Change Preset position. You can then use the Frequency Selector Dials to change the frequency of the active Preset channel.
Along the left side at the bottom are your display brightness controls.
On the right side is the squelch switch and the offset button. Pressing the offset button offsets the current frequency to a new frequency, generally in 5 or 8.33 kHz steps.
Last is the Menu button that is a rabbit hole of pages that you can explore but not necessary for normal operations. We’ll detail these in the manual.
Up on the HUD in the top left corner is the ARC-210 indication. V1 is the installed radio. This will either display the frequency when in Manual mode or the channel when in Preset mode. If you wish to change the frequency, using the Up-Front Controller, or UFC, type in the desired frequency and you’ll see it on the HUD scratchpad at the bottom of the HUD. Once entered, press the COM 1 button. To change the Preset, it’s just as easy. Select Preset mode, type in the Preset channel number on the UFC, and then press the COM 1 button.
You can also view all your Preset channels with their assigned frequencies on the new COMM page. Upon selecting COMM, then select ARC210 Presets. You now have all the Preset channels listed and by pressing the NEXT button you can view the second page.
To change a Preset frequency assignment, use the up and down arrow buttons to select the desired Preset channel row and you can then set a frequency, name, and AM or FM. For example: change the frequency by typing in a new frequency on the UFC and then pressing the FREQ button. In the same manner, type in a new name on the UFC and then press the NAME button. To switch the Present channel between AM and FM, just press the MOD, for modulation, button.
I hope this video was helpful for understanding the basic operations of this new radio for the A-10C.
NOTE: Multi-Threading is enabled in this video, but DLSS is not (forgot to enable it).
Purchase DCS: F-16C Viper from:
digitalcombatsimulator.com/en/shop/modules/viper
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.
Purchase DCS: F/A-18C Hornet from:
digitalcombatsimulator.com/en/shop/modules/hornet
In this DCS: F/A-18C Hornet video, we’ll look at some of the changes coming to the Electronic Warfare, or EW, page. This consists of new ALR-67 symbols and enhancement. It’s important to understand that enhancements are regarding an existing emitter contact on the EW display, they cannot be displayed independent of an emitter symbol. Let’s get started.
First, we have a new symbol for Early Warning Radars, or EWRs. These are the large, low-frequency radars that operate independently of a SAM site. These now appear as stylized radar dish.
Another new symbol is for radar-guided anti-aircraft artillery units like ZSU-23-4 or Gepard. This appears as a bent line with two protruding lines on the top.
Now let’s look at some of the new symbol enhancements. First is an open-X symbol that will surround an emitter symbol that is also jamming.
If the FLIR is slaved to an emitter on the EW page, a circle will surround the correlated symbol.
When a HARM is handed off to emitter also on the EW page, a staple will be drawn below the EW symbol indicating the two are correlated.
If an EW symbol is correlated with a friendly radar contact, a hemisphere will appear above the symbol. If, however, the radar contact is ambiguous, it will appear as a staple above the symbol.
digitalcombatsimulator.com/en/shop/modules/ah-64d
Note: The "unused switch" and the MTT promote switch are the same.
00:00 Introduction
00:53 Controls
02:03 Image Auto-Tracker (IAT)
06:43 Multi-Target Tracker (MTT)
In this DCS: AH-64D video, we’ll look at the next, big new feature coming to the AH-64D: the Image Auto-Track, IAT; and its Multi-Target Tracker sub-mode, or MTT. Earlier, tracking a moving target through the TADS would be done with the Linear Motion Compensator, or LMC. However, using LMC effectively can take a lot of practice, and it can be quite difficult to use if you do not have a controller with a good mini stick. IAT will make target tracking super-easy and can be used with either the FLIR or Day TV cameras.
digitalcombatsimulator.com/en/shop/modules/viper
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
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.
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.
digitalcombatsimulator.com/en/shop/terrains/nttr_terrain
Purchase DCS: F-16C Viper from:
digitalcombatsimulator.com/en/shop/modules/viper
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
Please see change log for more items once published.
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. I have also included a textual accounting of the video items.
https://forum.dcs.world/topic/209147-viper-mini-updates/?do=findComment&comment=5031373
digitalcombatsimulator.com/en/shop/modules/viper
Map: DCS: Persian Gulf Map
In this DCS: F-16C Viper video, we’ll talk about toss bombing using both CCRP and Dive Toss bombing modes. I’ve placed some links to earlier CCRP and Dive Toss videos. This will allow you to extend the range of unpowered bombs using a toss profile and potentially keep you out of harm’s reach.
Let’s first start with a CCRP delivery by selecting A-G master mode and selecting CCRP as the bombing mode by pressing once on nose wheel steering/the missile step switch on the stick.
From the SMS page, select to release the two CBU-87 as a pair and then select the Control page. On the Control page, the default release angle is 45 degrees. For this example, let’s instead set it to 30 degrees and then select enter at the top. Next, select the Control page again to bring us back to the main SMS page. In the bottom, center of the page, we can see that the release angle is now set to 30.
We are driving to steerpoint 1 which will be our target, an SA-2 SAM site. As we fly to the Steer 1, which is also our Sensor Point of Interest, or SPI, we’ll fly to align the Azimuth Steering Line, or ASL, with the SPI, box-and-dot, on the HUD.
Along the left side of the HUD is the loft release angle scale when in CCRP and DTOS modes. 10 nm is indicated at the top and the caret to the left indicates the current range to the SPI. The top of the staple indicates maximum bomb toss range based on the selected release angle.
At 10 seconds before pulling up, the solution cue will move down the ASL to the Flight Path Marker to the Flight Path Marker. When two-seconds from toss pull up, the max toss anticipation cue will appear on the HUD as a solid circle, the caret on the range scale will be at the top of the bracket, and both the solution cue will be just above and below the Flight Path Marker. Once all converge, the max toss anticipation cue will flash for two seconds, indicating that it’s time to initiate a 4-G pull up. It’s important to try to maintain 4 Gs during the pull up and keep the flight path marker on the ASL for best accuracy.
During the pull up with the weapon release button is held down, the solution cue resets to the top of the ASL and starts to move down the ASL again to indicate time to weapon release when the solution cue and flight path marker meet. The Horizontal Bar is positioned at the selected release angle. For best results, the flight path marker, ASL, and Horizontal Bar will all intersect at weapon release.
Let’s now try this using the Dive Toss bombing mode. Press the Nosewheel Steering/Missile Step button again on the stick to select Dive Toss and press forward on the Display Management Switch to set the HUD as the Sensor of Interest. In this example, we’ll set the Dive Toss target using the helmet by pressing long forward on the Target Management Switch. By using my head, I’ll place the designation where I want my SPI to be and press forward on the Target Management Switch to set my steering.
https://forum.dcs.world/topic/280176-dcs-ah-64d-mini-updates/?do=findComment&comment=5009941
Purchase DCSL: AH-64D From:
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, we’ll discuss the new George CP/G target identification system. Earlier, the George CP/G was unable to distinguish between friendly, unknown, neutral, and hostile targets. This could easily result in blue-on -blue incidents if not careful. This new system addresses this and offers different levels of target identification that the mission creator can select from.
To determine how the CP/G identities units that it spots, it can be determined by how we set up our Labels and F10 map view options.
Let’s select Options and then the gameplay tab.
From Labels we can select from the following:
Full and Abbreviated allow the CP/G to automatically know the unit’s coalition and unit type.
Symbol Only allows the CP/G automatically knows the unit’s coalition.
And No Label or Dot requires the CP/G to manually identify everything about the unit.
From the F10 View Options, we can also determine how CP/G unit identification is displayed on the F10 Map:
Map Only and My A/C require manual CP/G identification.
With Fog of War and Allies Only, the CP/G will automatically identify the unit’s coalition and unit type.
Using these options, you can set CP/G unit identification from an arcade level in which the CP/G is all-knowing to a very realistic level in which various factors are considered in identification and the CP/G can make mistakes.
Later in this video, we’ll use the most realistic settings of No Labels and Fog of War on the F10 Map.
In the Mission Editor aircraft window in the right-most tab, we have a new AI IFF option. When set to AUTO, the CP/G will use the Label and F10 Map options we just discussed. When set to Simple, it will instantly identify the coalition and unit type; when set to Label, it will use realistic spotting to determine the unit type but then automatically determine coalition; and Realistic will require realistic spotting to determine unit type and coalition.
For realistic unit and coalition identification, two primary factors are considered that include:
Angular size that is based on distance and profile of the unit. For example: a head-on unit will be more difficult to identify than one being viewed from the side.
A unit type being assigned to more than one coalition can affect coalition identification.
During the realistic CP/G identification process, unit identification will go through three steps:
The general unit type of air, ground or naval.
The unit category such as tank, IFV, utility, etc.
And then the specific unit type such as T-72, BMP-2, etc.
When identifying a unit, the CP/G will use the TADS/FLIR and use multiple field-of-views to acquire and then identify the unit. You will be able to see this through the VID/TADS page.
If there is more than one acquired unit in the line-of-sight designated area, the target list is displayed in the bottom, left of the screen. By default, only hostile and unknown units will be listed; friendly units would only be listed if no unknown or hostile units are identified. If an unknown is then determined to be friendly, it is removed from the target list.
Listings are color-coded:
Friendlies are blue
Unknowns are yellow
And Hostilities are red
If instead you wish to view all units, you can press Right Long with the target list in view, or back to just unknown and hostile by pressing Left Long.
To have the CP/G change the zoom level of a target, you can press Up Long to zoom in or Down Long to zoom out.
digitalcombatsimulator.com/en/shop/modules/viper
Forum post:
https://forum.dcs.world/topic/209147-viper-mini-updates/page/4/
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
digitalcombatsimulator.com/en/shop/modules/viper
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
digitalcombatsimulator.com/en/shop/modules/ah-64d
Useful Commands AH-64D Controls:
Axis Commands
- RHG MAN TRK Controller – X axis
- RHG MAN TRK Controller – Y axis
Right Handgrip
- RHG LRFD Trigger – First Detent
- RHG LRFD Trigger – Second Detent
- RHG Sight Slave Button
Left Handgrip
- LHG Linear Motion Compensation (LMC) Button
- LHG Weapons Action (WAS) Switches
- LHG TADS FOV Switches
- LHG Weapon Trigger Switches
In this DCS: AH-64D video, we’ll examine the addition of the Target State Estimator, or TSE, to greatly assist with engaging moving targets with the gun and rockets.
When using the TADS as the sight, TSE allows to determine actual target velocity relative to the TADS line of sight. Using laser-ranging, embedded INS and GPS systems, TADS slew rate, and the air data system, the TSE compares aircraft movement rates from target rates. Once the actual target rate is known, the appropriate amount of lead can be calculated to account for weapon time of flight and required lead. Naturally, this will be essential for accurate fires when using Linear Motion Compensation, or LMC. The most important takeaway is that TSE will provide accurate lead against moving targets when engaged through the TADS.
When using the IHADSS, lead is not calculated.
A very important item to understand is to avoid range jumping. This can happen when you switch between range sources, and it will appear as the TADS line of sight jumping away. This can easily happen if you do not establish an accurate range to target before initiating TSE. Therefore, it is important to use automatic ranging and perform a first detent ranging pulse of the target before to committing to a TSE/LMC track.
To use TSE, you will first want to set the manual range from B6 to A, or automatic, on the keyboard unit. Although a default, manual, or “stale’ range can be used, it is more effective to use AUTO ranging.
Make sure the laser and weapon system are armed and we’ll select the gun for this first demonstration.
Setting the TADS as the Sight, either slew or slave the TADS line of sight to the target area and perform a first detent laser ranging that sends a three-pulse ranging distance to the target area.
With the TADS over the target, engage the second detent of the laser for continuous ranging, enable LMC, and use the thumb force controller to track the moving target. The key is not to rush it and allow TSE to gather enough data to calculate proper lead. I handy tip is to say “T-S-E, catch up to me” with a steady LMC track and only then fire.
With the target in range and a good LMC track with TSE, fire the weapon.
digitalcombatsimulator.com/en/shop/modules/ah-64d
Force Trim/Hold Mode Switch (Cyclic Stick controls):
- Altitude AL/Right
- Attitude AT/Left
- Cancel D/Down
- Set Trim U/Up
In this DCS: AH-64D video, we’ll talk about the Altitude Hold mode of the AH-64D. Using either the radar altimeter or barometric altimeters, the Altitude Hold is a very useful function to automatically hold a hover altitude or keep the aircraft at a constant altitude in forward flight.
To engage radar altitude hold, the ground speed must be less than 40 knots, vertical velocity must be less than 100 feet per minute, and the altitude must be less than 1,428 feet AGL. It should be noted that the Radar Altitude Hold is NOT a terrain following mode since it provides a distance directly below the helicopter and not in front of it.
Barometric altitude hold will be active whenever the aircraft is outside the parameters for radar altitude hold, which is the case if the altitude is greater than 1,428 feet AGL or the ground speed is above 40 knots. To engage barometric altitude hold between 5 to 40 knots ground speed, the vertical velocity must be 200 feet per minute or less. The vertical velocity limit for engagement then scales linearly from +/- 200 feet per minute at 40 knots to +/- 400 feet per minute at 160 knots.
Regardless of which sub-mode it is in (radar or barometric), the Altitude Hold will automatically disengage if the rotor RPM (Nr) drops below 97% or exceeds 104%, either engine torque exceeds 100%, either engine’s temperature (TGT) exceeds 867 degrees C, or whenever the pilot displaces the collective more than half an inch from the original position at the time of the Altitude Hold was engaged.
Altitude Hold relies on the Flight Management Computer, or FMC, and is engaged by pressing right on the Force Trim/Hold switch. Once engaged, the FMC will automatically adjust collective pitch to maintain the altitude at the time the Altitude Hold was engaged. However, like other axis within the SCAS system, it only has a limited authority to do so. For this reason, before engaging altitude hold, ensure that you are first established in a trimmed state.
Combined with Attitude Position Hold, this can allow a 3D hold for a hands-free hover.
Please note that the IR Pointer range was increased in the build this video was created, and this change will be coming soon to an update. Also note that the JTAC coordinates are in a 3+3 format but the AH-64D requires a 4+4 format. Simply add a zero to the E/W and N/S. For example: 123456 to 12304560.
Later when Laser Spot Tracker (LST) is added, the AH-64D will also be able to locate a laser designation spot. However, even now, the JTAC can lase a target and you can launch on the target coordinate using LOAL mode and the seeker tuned to the JTAC’s laser PRF.
digitalcombatsimulator.com/en/shop/modules/hornet
In this DCS: F/A-18C Hornet video, we’ll discuss the ADM-141A Tactical Air Launched Decoy, otherwise referred to as the TALD. The TALD includes Luneberg lenses that can be configured for different Radar Cross Sections, or RCS. In the case of the Hornet, the RCS will match.
TALDs can be carried on stations 2, 3, 7, and 8 on BRU-42 racks with up to three TALDs on each rack. TALDs are listed in the Mission Editor in AG Missiles category.
Upon release, winglets unfold from the decoy and allow the TALD to glide. Naturally, range will depend on altitude and airspeed as it is an unpowered system.
TALDs can be used to create false targets for both surface-to-air and air-to-air hostile radars. This is a great tool for suppressing enemy air defenses and giving enemy fighters false targets to sort through.
In this example, we have an SA-11 SAM site off our nose, and we’ll release four TALDs for it to engage while we then engage the transmitting radars with AGM-88 HARMs.
We’ll select AG master mode and on the left DDI we can see 141 at the top of the Stores page for the ADM-141A TALD. Once selected, we can see that we have four loaded, two on each wing. TALDs are released in Manual mode and indicted by the reticle on the HUD. To change the selected station, press the STEP button.
To release a TALD, press the weapon release button on the control stick. We’ll release all four to keep the SA-11 busy.
We’ll bring up the HARMs and engage the SA-11 TELARs in pre-Briefed mode. As the SA-11 engagement radars tracks the TALDs, the HARMs will make short work of the target.
digitalcombatsimulator.com/en/shop/modules/viper
In this DCS: F-16C Viper video, we’ll talk about the use of the GBU-24A/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. It also uses the BLU-109/B penetrator warhead that is effective against hardened targets.
The bomb can be carried on stations 3, 4, 6, and 7.
Once dropped, the GBU-24A/B 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.
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, we’ll explore both the Position (often referred to as Hover) and Velocity Attitude Hold Modes. For Position mode, you must first establish a stable hover between 0 and 5 knots; it is not a magic button that places you in hover. For Velocity mode, establish a stable airspeed between 6 and 40 knots.
In both modes, first center the trim using the Force Trim Release (FTR) switch to center the control reference point. This allows the Flight Management Computer (FMC) the greatest flight control systems movement to maintain the hold mode.
To release an Attitude Hold mode, press left again on the Trim switch on the Cyclic.
Since the Early Access release of the -64, our focus has been on tuning the existing systems and fixing bugs. Today though, we’ll talk about a new feature coming to the -64, using Hellfire missiles in Ripple mode.
From the Weapons, Missile page, select RIPL from the mode button. When in this mode, the channel will automatically alternate between the Priority channel and the Alternate channel. When might you use this? The most common use would be when working with a flight member online in which he or she is designating on the Alternate channel, and you are designating on the Priority channel. In this way, you can alternate your shots as one for you and then one for them.
Naturally, if you used RIPL and just used self-designation, you would need to manually change the code each time to match the channel. As such, this would most often be used with a flight member.
It’s worth noting that if an Alternate channel hasn’t been set, in which case ALT at B2 says “NONE”, the RIPL mode option will remain “barriered”.
digitalcombatsimulator.com/en/shop/modules/viper
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.
digitalcombatsimulator.com/en/shop/modules/viper
Hey everyone, Wags here from Eagle Dynamics. 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.
Let’s get started.
digitalcombatsimulator.com/en/shop/modules/hornet
In the previous Automatic Carrier Landing System (ACLS) video, we looked at using this in conjunction with DCS: Supercarrier. In this video, we’ll discuss how to use the Hornet ACLS with the free, CVN-74 John C. Stennis carrier comes with DCS World.
The steps are:
1- Contact the carrier on the correct radio frequency using COMM 1 or COMM 2 and select the ATC option. From the ATC selections, select Inbound.
2- Enter the correct Link 4 frequency from D/L.
3- From the HSI page, enable ACL.
4- Fly a Case III as before, and at 5.5 nm (should be gear down, flaps down, hook down, and on-speed) select AP (autopilot) from the UFC (Upfront Controller) and select the CPL option on the UFC.
5- Once coupled, you can press the paddle switch to uncouple and manually fly the approach on Mode 1A.
Rather than couple, you may also elect not to and fly manually in Mode 2.
digitalcombatsimulator.com/en/shop/modules/viper
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.
digitalcombatsimulator.com/en/shop/modules/supercarrier
Download DCS: F/A-18C Hornet from:
digitalcombatsimulator.com/en/shop/modules/hornet
Earlier Case III video:
youtu.be/n4d92zwyb04
In this DCS: F/A-18C instruction video, we’ll review operation of the Automatic Carrier Landing System (ACLS) and associated Link-4 datalink system that allows two-way communication between the carrier and aircraft.
ACLS provides guidance to the Marshal Stack, the carrier, and three different levels of landing assist. Mode 1 provides hands-off recovery, Mode 1A allows manual landing with ACLS HUD and Link-4 indications, and Mode 2 allows manual control with just “tadpole” guidance.
ACLS is only available for Case III recovery operations.
COMING SOON
Hey everyone, Wags here from Eagle dynamics.
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.
digitalcombatsimulator.com/en/shop/modules/viper
Hey everyone, Wags here from Eagle Dynamics. In this DCS: F-16C Viper video, we’ll look at the Primary Datalink Track feature, or PDLT. PDLT allows you to designate a datalink-only or a correlated track on the HSD and have an octagon symbol around it on the HSD, FCR, HUD, and HMCS.
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.
digitalcombatsimulator.com/en/shop/modules/ah-64d
One common question that I often see asked is why my aircraft crashes into the ground when in a hover or very slow speed. This can be due to one of two reasons, either Vortex Ring state, VRS, or settling with power. I often read folks blaming VRS, but it is often not, and rather settling power.
I’ll try to explain both and how to avoid them. For a detailed explanation of why it happens, I’ll leave that to Casmo and his magic white board.
Before we get started though, a quick PSA regarding a very common question I get: how do I remove the TADS video from the HDU when I want the TADS as my sight? The easiest and fastest way is to just remove the IHADSS by pressing the “I” key. If though you want to retain the monocle, just set your level to zero on the TEDAC.
Okay, back VRS and settle with power. Let’s first review the most important controls. First, from the Pilot, Axis controls, make sure that the collective and lower levers are bound and have full range.
First, we’ll talk about VRS. This happens when three conditions exist. You have low forward airspeed (lower than 16 to 24 kts), your vertical velocity in exceeding 300 feet per minute as indicated on the scale along the right side of the HDU, and insufficient collective power.
If you avoid any one of these three conditions, you should be fine.
The much more common issue that most of you are running into is settling with power. This happens when you are at very low airspeed, or a hover and you are demanding more collective power than the aircraft can generate to produce enough lift. When you are outside of ground effect, over 48 feet, the rotors must generate a lot more lift to maintain, much less, increase altitude. If the aircraft is heavy, there is a high outside air temperature, you are operating at a high MSL, can all lead to power requirements that the aircraft cannot meet.
If you continue to pull back on the collective and demand more power than the engines can give you, you’ll just make matters worse and lose rotor RPMs. The engines of the AH-64D, like the engines in any other DCS helicopter, can only produce so much power before they encounter some sort of limitation, whether that be engine RPM or engine temperature. The engines will limit themselves to prevent damage or failure, so once they reach a limit, they will no longer produce any additional thrust to keep the rotor spinning at the current RPM. However, if you keep increasing the collective, which increases blade pitch angle and drag, the rotor RPMs will begin to slow.
Just like any other airfoil, when you reduce your airspeed over the wing, it produces less lift. Therefore, when your rotor slows down, you produce less lift. Therefore, continuing to pull up on the collective when your rotors are slowing down actually makes the situation worse, and results in falling faster. This can be equated to a fixed wing pilot continuing to pull back on the stick to prevent a stall due to low airspeed, but as a lot of you know from playing our other fixed-wing modules, this exacerbates the stall.
You can see when the engines start limiting themselves due to turbine temperatures by observing the Engine page in flight. As you continue to pull on the collective, as the engines approach 867 degrees Celsius, they will top out and the rotor RPMs will begin to drop. As mentioned, when operating at higher altitudes and/or higher temperatures, like NTTR in the summer, the engines may encounter this limit before the torque reaches 100%. This may lead to rotor RPMs decreasing and a loss of lift.
As mentioned, this can be experienced in the other DCS helicopters as well, such as the Ka-50, Mi-24 or UH-1.
To get out of a VRS or a settling with power situation, the easiest solution is to drop the nose and get forward airspeed. But, before getting in such a situation, keep a very close eye on your VVI when entering a hover or very slow speed flight and don’t let it fall to less than 300 feet per minute.
In this video I'll touch on:
- Setting up the laser
- LOAL HI and LO attacks
- Force Trim Release (FTR)
- George Command Switch
Have fun!
https://forum.dcs.world/topic/283298-dcs-ah-64d-faq/#comment-4858067
NOW AVAILABLE!
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, we’ll explore our AI crew for the 64 that we call George. George is a common reference to auto-pilot systems in real aircraft.
When we developed this system, we did so with helicopters in mind that pose a unique set of challenges compared to fixed wing AI crew command systems. For instance, you must be able to rapidly input maneuver instructions, it must not block any of our forward view, it should not require head-movements, and it must be flexible to adapt to different flight conditions.
While there are certainly some very capable AI command systems for fixed-wing aircraft, they would not translate well to helicopters.
At early access release, George will be available for both the pilot and co-pilot/gunner, or CP/G. You will be able to fly and entire mission from just the pilot or CP/G seat.
During the early access period, we will continue to improve and refine it, particularly the automatic sighting and engagement abilities of the CP/G.
https://forum.dcs.world/topic/283298-dcs-ah-64d-faq/#comment-4858067
NOW AVAILABLE!
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, we’ll learn how to cold start our AH-64D.
Please note that this was recorded from a pre-release version in mid-March 2022. Later in development, aspects of the procedure may change.
My Cold Start Cheat Sheet:
Pre-Flight
1. Doors
2. Lights
3. Engine Levers Off
4. Rotor Brake Off
5. Parking Brake On
6. CMWS Off
7. COMM Levels
8. Battery
9. Tailwheel Locked
10. Lights Test
11. Fire Detection Test
APU
12. APU
13. ENG/SYS Page
14. Check EUFD
15. Check DMS Page
16. Set COMM Page
17. ASE Off and Setup
18. Set TSD Page
19. Set FUEL Page
20. Set FLT Page
21. Set WPN Page
22. IHADSS Boresight
Engines Start
23. Set NVS as Desired
24. Uncage SAI
25. ENG/SYS Page and ENG Page
26. ENG 1 Start Wait for TGT Less than 80 C
27. Power Lever to IDLE at Ng Increase
28. Repeat for ENG 2
29. Power Levers to FLY When OIL PSI is Less than 70 and NGB Temps Above 20 C
30. Check RPMs at 101%
31. APU Off
Before Taxi
32. Parking Brake Off
33. Tailwheel as Desired
Have questions? Please see our FAQ at:
https://forum.dcs.world/topic/283298-dcs-ah-64d-faq/#comment-4858067
Pre-Order and Save 30%
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, learn how to setup our controls to fly the -64.
Growling Sidewinder Viper Flight Model Changes Preview:
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 sysmbol with a strike through it.
Also, on the HAD, we added the cursor bullseye location.
https://forums.eagle.ru/topic/283298-dcs-ah-64d-faq/#comment-4858067
NOW AVAILABLE!
digitalcombatsimulator.com/en/shop/modules/ah-64d
In this DCS: AH-64D video, we’ll explore the defensive systems that will be available at launch. These will include the Aircraft Survivability Equipment, or pronounced “ACE”, that consists of the wire strike protection system, the AN/APR-39A(V)4 radar signal detection set, and the Common Missile Warning System, pronounced “C Moss”.
Combined, they work to detect, warn, and provide countermeasure options against both radar-guided and infrared-guided threats.
Later in early access we will add the AN/AVR-2A laser signal detecting set, the AN/ALQ-136 electronic radar jammer, and the AN/APR-48A Radio Frequency Interferometer.


