Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Questa discussione è stata chiusa 
Regole e linee guida per le discussioni
Segnala questo messaggio
In the meantime, we are shooting for (not a promise) D/L SA page and HARM TOO mode for 27 February.
In parallel, LTWS, Aircraft/Mission Card, and wake turbulence are all progressing well.
I will be away for the next week, so there will be no new updates until next week.
- Wags
[img]https://steamcdn-a.akamaihd.net/steamcommunity/public/images/clans/4471395/15f0b474ffad5ee4297176e29b3af947109ffc88.jpg[/img]
The Datalink and Situational Awareness (SA) Display of the F/A-18C Hornet - Introduction
This week we plan to release the initial version of the MIDS/Link-16 datalink / Situational Awareness (SA) page for the Hornet. This is a basic, introduction video to get you started understanding the system. Later, once the datalink is feature complete, I’ll create a full academic video, interactive training mission, and an updated manual.
A few notes to keep in mind:
1- This is the initial version with more features to follow like automatic IFF modes, IFF code XP and AI setup, Link-4/HARM/FLIR display options, declutter options, flight ground target markers, basic ROE indications, MIDS voice, and a few more.
2- The logic that determines when a target is own-ship classified unknown, hostile or friendly is determined by an ROE matrix of factors. In this initial release it will be determined by Mode 4, but later we will probably factor in NCTR and SURV.
3- An NCTR print requires an L&S or STT lock, therefore I was unsuccessful in the print attempt. My error.
4- Friendly PPLI data is always fuel state, not range.
5- Later with the TXSDSG, it will be based on flight TGT ground designations, not necessarily WPDSG (it can, but not always).
6- I did not show it, but the static SAM threat rings will be included in the version this week.
7- Sorry for the low energy, I’m recovering from a cold and I’m dead inside.
- Wags
AGM-88C HARM in Target of Opportunity (TOO) Mode
This week in the Open Beta we will release the next mode of the HARM, namely TOO mode. This video is to introduce the use of the HARM in this mode. A few notes:
1- Later, we will add the TOO TD box to the HUD.
2- In addition to the line above the emitter that indicates the radar is locking you, an F indicates it is a friendly emitter and a “U” shape indicates a naval emitter.
3- When enabled, LIMIT only shows the 5 highest priority emitters. Otherwise, up to 15 emitters can be displayed.
4- Like SP mode, there is no range indication.
5- Once TOO mode is done, we will implement Pre-Briefed and Pull-Back modes.
6- Once HARM is done, then we will focus on the targeting pod.
7- Yes, I’m still sick and hopped up on cold medicine.
List of HARM TOO classes:
ALL. All classes of radars
FRD. Friendly radars
HOS. Hostile radars
FN. Friendly naval radars
HN. Hostile naval radars
F1. Old friendly radars
F2. New friendly radars
H1. Old hostile radars
H2. New hostile radars
FAA. Friendly AAA
HAA. Hostile AAA
FS. Friendly search radars
HS. Hostile search radars
UKN. Unknown radars
PRI. Radars locked to player aircraft
A little update of what to expect coming up:
After the datalink, SA page, and TOO mode for HARM this week, we then plan Latent Track While Scan (LTWS), JDAM, Aircraft/Mission Card, and some bugs fixes for the 13 March Open Beta. This is an estimate and not a promise.
As has been mentioned before, the engineer assigned to the HARM is also assigned to the targeting pod. So, once HARM is done (PB and pullback modes), he will work on the TGP. Also, in the very near future, we plan to revisit the Hornet flight model, the JDAM flight model (INS-GPS autopilot), and other weapon Launch Acceptable Region (LAR) profiles.
- Wags
Probably in the next Hornet OB update, we will be adding two-factor identification. As most you probably know, a negative Mode 4 IFF response does not always mean hostile, just that it is not friendly. With the upcoming change, a negative Mode 4 IFF AND input from NCTR or a SURV track will be required to set an unknown to friendly or hostile.
Also, to reiterate from an earlier note: we are currently simulating just manual Mode 4 IFF, which requires a depress of the Sensor Select Control switch. Later, when we implement the AZ/EL page, we will add the automatic IFF Mode 4 interrogation modes. One of thes includes auto-IFF when a contact is an STT or L&S. The earlier auto-IFF with a target lock was a stop-gap until the more realistic system could be implemented (now ongoing).
Thanks
One of the big items we are working on for the Open Beta next week is the introduction of Latent Track While Scan (LTWS). This is a sub-mode of Range While Search (RWS) mode that can be selected from the DATA sub-level (LTWS and MSI).
Even in RWS mode, contacts are in fact track files, but much of the data is hidden unless LTWS mode is selected. When selected, you can:
Soft lock a contact with a Target Under Cursor (TUC)
Designate a target to become the Launch and Steering (L&S) track file with airspeed, altitude, and MSI indications. This has a star HAFU symbol.
A second contact designation becomes the Designated Target 2 (DT2) and has the same information as the L&S but has a diamond HAFU symbol.
You can TUC a third contact as well.
It will be important to remember that LTWS has rather poor update for the weapons, so it cannot support a weapons launch. To launch, you will need to designate the target again to an STT track. Also because of this, you will want to use a narrower radar azimuth setting and lower bar setting (like 80-degree azimuth and 2 bars). If not, the target updates will be too slow, and tracks may be lost.
On the HUD, the box/diamond indicates the L&S line of sight and the “X” indicates line of sight to DT2.
LTWS will start to form the foundation of Track While Scan (TWS) which will be coming afterwards.
Thanks
[img]https://steamcdn-a.akamaihd.net/steamcommunity/public/images/clans/4471395/66c7beacd2700f4147b6e2ff4c6fbfd04315062c.png[/img]
1- Update to IFF and D/L identification system
2- LTWS
3- JDAM
Next week we plan (not promise) a new Hornet Open Beta update that includes changes to the IFF/datalink identification system and introduction to Latent Track While Scan (LTWS) and the Joint Direct Attack Munition (JDAM). JDAM in particularly is still very much work in progress with large elements to still add. This video is provided to provide you an initial understanding of these systems.
Please also note that the A/A radar is an iterative process from which LTWS will be built upon to create the Track While Scan (TWS) mode and the Azimuth / Elevation (AZ/EL) modes.
Once the AZ/EL page is created, then the various automatic IFF modes will be implemented.
Before you ask… the targeting pod will come after the HARM is complete.
Thanks, and have fun!
In the Open Beta this week, the option to drop Joint Direct Attack Munitions (JDAM) will be added for manual mode (GBU-38, GBU-21, and GBU-31(V)3/B. This allows basic employment through both Pre-Planned (PP) and Target of Opportunity (TOO) modes. Even in this early version, you can easily attack multiple targets in a single pass by assigning individual JDAMs to different PP mission targets.
Some notes:
We are currently using coordinate entry in the HDTH (hundredth of a degree) option. Later, we will add the THSD option (termed PRECISE when used in the HSI for waypoint entry/modification). As with the real aircraft, JDAM target entry using UTM is not an option (though it will be later to enter/modify waypoints via the HSI).
Later, AUTO delivery and much more detailed attack information will be added like the Launch Acceptable Region (LAR), dynamic launch zones, terminal attack option, launch points, release zones, JPF, BIT/MUMI pages, and multiple attack zones will be available.
GBU-32 (Mk-83 with JDAM kit) and BRU-55/A will be added later. The BRU-55/A will allow dual carriage of GBU-38, GBU-32, and AGM-154 JSOW.
Although not 100% complete, the Open Beta this week includes a greatly updated JDAM flight model and autopilot.
Thanks, and have fun!
In parallel though, other tasks are steaming ahead like new features for the SA page including STEP, EXP, TXDSG, and other elements to complete this system. We are also making great progress on the Harpoon and it went into internal testing today. As noted, before, initial implementation of the air-to-ground radar rendering technology is now being used to create the Real Beam (RB) mode for the radar. Once RB mode is done, we can then use that as the foundation for other modes like SEA, EXP, GMTI, etc. On the GPS-weapon front, work continues on dynamic launch zones for JDAM and JSOW, Track While Scan (TWS) radar mode is underway, and other items and bug fixes.
Thanks,
Wags
[img]https://steamcdn-a.akamaihd.net/steamcommunity/public/images/clans/4471395/d3276f41c69bce98e7257e980e8dcf269a8bcdc3.jpg[/img]
[img]https://steamcdn-a.akamaihd.net/steamcommunity/public/images/clans/4471395/7c91ef8a1a093fdc686ac4131daaa9d69201c221.jpg[/img]
Earlier Case III video:
https://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.
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.
Following some time off, I’d like to update you on current Hornet tasks and priority tasks following those.
Current tasks include:
Following the substantial update to the Viper flight model and FLCS, the team is now focused on the Hornet flight model and FCS. In parallel, important changes are being made to the landing gear and how it behaves at touchdown / touch and goes. This is the primary Hornet task.
Correcting AGM-84D, AGM-84E, and SLAM-ER behavior.
GPS-weapon using TOO engagement behavior.
Incorrect Velocity Vector confinement error.
Following the above, priority items include:
In parallel with the Viper, tuning air-to-air performance including look-down and search to bug target delay.
UFC BU page.
Please note that this is not a 100% inclusive list, but rather the more important highlights.
Kind regards,
Wags
Merry Christmas and all the best for 2023! As the team prepares for some well-earned time off, here is where we are with the Hornet:
Highest priority is on bug fixing. This includes, but it not limited to issues with the Harpoon, SLAM, and SLAM-ER behaviors, ASE dot behavior, etc.
We are performing a ground up review of and refactoring of the Hornet flight model and flight control system. This also includes a large update to the landing gear model.
New and improved pilot model. Once this is complete, we’ll do the same for the Viper.
Refactoring the radar for more accurate performance. Once this is complete, we’ll do the same for the Viper.
We’ve updated the ALR-67 to include new functions and symbols.
Following the next Open Beta, tasks include:
IAM loft cues.
New bomb fuzes like DSU-33 and JPF.
MUMI page and DTC. This will follow the Viper DTE page and DTC.
A review of MSI functions based on available data for the version we are modeling.
Please note that the above are just the highlights is certainly not 100% inclusive of all planned work.
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.
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.