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.
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.
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.
Although we released a large and well-received flight model and flight control system update earlier, we have not been sitting on our hands. We will soon be further improving these aspects of the Viper.
• You will be able to attain up to -3.4G. Bring on the creative jinks!
• Removed FLCS flight transition mode between gear down and gear up. Nose will be rock steady. Same holds true if you get slow and the flaps come down. This results in a much more stable nose pointing in a fight.
• DFLCS roll rates have been improved/increased.
• The yaw oscillation when on the deck at high speed is a memory.
• With sufficient energy, the Viper will now hold 9.3G.
• Gear down / AAR door open roll gains have been adjusted to be more accurate.
• Takeoff and landing mode FLCS gains have been improved.
• DFLCS gun compensation has been improved in roll and yaw when slow.
• Manual Pitch Override (MPO) switch will override the negative G limiter.
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.
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
Following our projects meeting today and review of the DCS: F-16C Road Map, we have decided to return several items to the planned features of Early Access release.
Whilst Date Transfer Cartridge (DTC) and Mission Planner is on the Road Map, this is a much larger item that is not just an F-16C item. As such, it will need to come after the module exits Early Access.
As mentioned before, once the Viper exits Early Access, we’ll release a roadmap of planned additional features.
On a different matter, we’ve been having “lively” internal discussions regarding the F-16C radar regarding detection versus bug range and the effect of radar look down angle. This has included a review of numerous documents and discussions with SMEs. We are making good progress to resolve these issues for a July update.
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
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.
Jako koukal jsem na to dvakrát a vůbec nevím, co v tom videu říkal. Něco ve videu těžce odvádělo moji pozornost od hlavního obsahu. Hlavně asi to počítadlo FPS. Jde to na začátku blbě vidět, ale má tam přes 80 fps při rozlišení 4k. Údajně to táhne na I9-9900K, 32GB RAM a RTX 2080Ti YouTube Video
Jako dal jsem video do špatné sekce, tak tady je novinka ohledně F-16: YouTube Video
Jde o to, že při rozlišení 3840 x 2160 tam má hned v první scéně přes 80 fps. Prý je to nový engine s multi-threading a zapomněl zapnout DLSS. No a kartu má právě onu 2080ti
Chlapi viete poradiť? Po dlhšom čase zase lietam Zmiju - a nejak sa mi nedari spojazdniť dtalink ani IFF. Teda upresním: datalink zapnem, , tiež IFF, ale na displejoch sa mi nezobrazujú graficky odlíšení vlastní/nepriatelia. Pozeral som do Chuckovho návodu, ale veľmi mi to nepomohlo. Niečo mi uniká. Viete poradiť?
Former F-16 Fighter Pilot Tries DCS 2.9 F-16 Viper Flight Model
Mover (F-16, F/A-18, and T-38A pilot) reacts to the new DCS 2.9 F-16 Viper updated Flight Model. Flown using the Thurstmaster TQS Throttle and Winwing F-16 EX FSSB Stick.
IL-2 Sturmovik™, Cliffs of Dover™, Pacific Fighters™ are trademarks or registered trademarks of 1C EUROPE, 1C-Multimedia, 1C ONLINE GAMES.
Other marks used herein are those of their respective owners.
