-
Posts
11788 -
Joined
-
Last visited
-
Days Won
59
Content Type
Profiles
Forums
Events
Everything posted by Wags
-
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
-
As we said at the start, the initial IFF was just a stop-gap until the more realistic system was implemented. The accurate system is now in the process of being implemented. Thanks
-
No, it is not "bugged". There is both manual IFF (what we have now), and multiple types of automatic IFF (like STT and ACM modes) that are enabled from the AZ/EL page. Once the AZ/EL page is added, we'll add the automatic IFF modes then. Thanks
-
Our map team continues to go above and beyond by adding new content to the Persian Gulf map. With the new additions, the Persian Gulf map will be the largest map in DCS World (as measured as distance between airfields) and have the most airfields. Coming to the Persian Gulf Map: - Liwa airfield - Ras Al Khaimah airfield - Bam - Persepolis These additions will be included in an upcoming map update.
-
Autostart works fine here as well. As noted, please provide a track file to help us duplicate your issue. Thanks
-
As we've said many times, the Litening will come after HARM is done. At a later point, we'll also add the ATFLIR. Thanks
-
Re IFF on an unknown STT target: as we've stated earlier, this has already been resolved internally. Sadly, it was not completed in time for this weeks OB. Thanks
-
Available data and SME availability.