Wags

Fixed indicates it should be fixed in a pubic version of DCS World (at least the OB) Fixed Internaly indicates it is fixed in the internal development build, but in public build yet. Thanks

While other aircraft have this, the legacy Hornet does not.

https://forums.eagle.ru/showpost.php?p=3859226&postcount=149

Yes, this is planned for later as part of the new carrier communications for CASE I, II, III ops. Thanks

It is not just a matter of adjusting the number. The older flares were larger with different properties to the more modern, smaller flares that only take one slot. As such, we first need to create an all new flare type object and performance data. Once that is done, we can adjust the expendable numbers. This also needs to be carefully tested so it does not break gameplay by insuring the new flares have the proper level of effectivness. So, while at first glance it may seem a simple and quick adjustment, in fact it is not. Thanks

https://forums.eagle.ru/showpost.php?p=3735513&postcount=178

Hey everyone, After talking with the team today, I’m afraid that we’ll have to push the JDAM back a bit for several reasons: Still some issues to resolve in the flight dynamics and auto-pilot when the bomb is released near or at maximum range. We need more time to test. We need to ensure that this new code will not break any 3rd party aircraft. We will though still have an Open Beta tomorrow that will include LTWS and other elements. While we are all disappointed that we can release the JDAM tomorrow, there is just too high a chance of it causing significant DCS-wide problems. If all looks good, we plan to release the JDAM in an Open Bea on 10 April 2019. In a related matter, we will be moving Hornet updates to a monthly event, rather than generally every two weeks. We simply need more time for proper testing to avoid bugs, break other products, and avoid the need for hot fixes. While waiting is always hard to do, this will ultimately provide a more stable and solid product. Thanks

DCS: F/A-18C Hornet: JDAM Multi-Target Attack Pass https://www.youtube.com/watch?v=YJjKFzMqHRo In the Open Beta this week, the option to drop Joint Direct Attack Munitions (JDAM) will be added for manual mode (GBU-38, GBU-31, 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!

As stated in the most recent video, yes.

PRECISE and GRID will be added later.

No, it does not. Simple setting up of PP targets and selecting each in turn with weapon release. Nothing Gucci.

No, that will not happen. Zero data.

Yes, we changed our mind.

Yes, and GBU-32 later in early access.

PLANNED FOR 27 MARCH 2019 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! - Wags

Yes, I plan a rather long update video prior to 27 March to discuss D/L changes, JDAM, and LTWS.

Yes, all you have to do is make sure IFF is "ON". Later we plan to add specific frequency selections. But, this will be a much more complex task as it will also require a rather large update to the AI logic to account for sqawks. Thanks

LTWS Update 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

Fixed for the OB next week. As well as FF acting as another supporting IFF identification element. So: Friendy ID = just need Mode 4 Hostile = 1- Mode 4 and SURV, or 2- Mode 4 and FF, or 3- Mode 4 and NCTR. Thanks

https://forums.eagle.ru/showpost.php?p=3847832&postcount=144

WIP LTWS. Full version will be for next week. Thanks

While or general plan is to alternate Open Beta and Release Version updates, there will be times when this needs to be modified due to technical issues. This week was one of them due to desynced binaries and resources in our file servers. This was resolved today and an Open Beta update should be available very soon, if not already. Next week we plan to release a new Open Beta (27 March) and then a Release Version update on 3 April). Thanks

Hornet Mission of the Week Normandy FA-18C Fortress Cherbourg by Bunyap Normandy 22 Jun 2004, Afternoon Fictional An operation is underway to reduce the enemy defenses on the approaches to Cherbourg. Strongholds are being targeted using both air and land assets to prepare the way for a final ground assault. Your flight of two F/A-18C, callsign Springfield 1, will be on call to destroy targets as directed by forces on the ground. Your flight will depart from the carrier and fly southwest to the target area. You will hold at Initial Point (IP) Adder, waypoint 2, and check in with a JTAC, callsign Axeman, on radio channel 5. Your target is expected to be enemy bunkers near the approaches to Cherbourg. The JTAC will direct your flight onto the targets when you arrive on the scene. Your flight is armed with both laser and IR guided AGM-65 Mavericks. The JTAC will mark targets visually with ‘willie pete’ smoke rounds and with a laser designator. Laser code 1688 will be in use. The target location will also be given as a bearing and distance from IP Adder, waypoint 2. See the mission planner for detailed navigation planning and the location of friendly air assets. Enemy units on the map can be considered current intel but may not be the threats you face during the mission. Other package elements will be airborne and operate on a common mission radio frequency. A flight of F/A-18Cs, callsign Springfield 4, be on station north of Cherbourg to provide suppression of SAM threats (SEAD) if needed. Their primary targets are mobile Roland SAM systems so you may be tasked to take care of shorter range Gepard AAA systems yourself if they become active. Combat Air Patrol (CAP) flights will be airborne to provide cover. Ford 7, two F-15C, will be on station to the west and Enfield 4, two F/A-18C will be on station to the east. Two F-14B, callsign Uzi 1, are also on station near the carrier. You may disengage and proceed in their direction for additional cover if needed. Hawk and Patriot SAM systems are active inland and should not be approached. Enemy aircraft can be expected to operate under their SAM coverage. See the intel slide to the left for details. Carrier Admin: TACAN: 74X ICLS: 11 Success criteria: - Several different threat scenarios may play out and it may not always be possible to destroy the primary targets. Returning safely to base is the only success requirement. Normandy FA-18C Fortress Cherbourg.miz

Based on our talks with Hornet pilots, the amount of shake in our Hornt is correct. Thanks

Hey everyone, 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