Peaches

With TacView files attached. Change .trk to .acmi after download. OB 2-5-3 AGM success.trk OB 2-5-4 AGM 65 fail.trk

Since OB 2.5.4.26368, the flight path of the AGM-65D has been changed, which causes the weapon to no longer be suitable for low-level, stand-off attacks, which is a key mission for the DCS A-10. Attached are two track files with the same set-up and execution of a pop-up attack on an SA-6 radar near sea level. The first track file is from OB 2.5.3.24984, where the missile is launched at 800 feet MSL and 6.5 NM away from the target. The missile climbs to an apex of 3,200 feet MSL by 2.4 NM away from the target and then dives in and kills the vehicle; its flight path is straight towards the target the whole flight. This behavior has been consistent for the AGM-65D for years, perhaps since the inception of DCS: A-10C. The second track file is the same execution but on OB 2.5.4.26368. In this case, the missile, launched at 800 feet MSL and 6.5 NM away from the target immediately starts veering left, performs a slight climb to 1,100 feet MSL (apex at 5.7 NM away from target) and then gradually descends, going below 150 feet MSL while still 2.7 NM from the target and inevitably trashing itself in the trees. Please take the time to look into this change and correct the flight path back to its former profile, so that the Hawg can regain its key mission of pop-up attacks in high-threat environments. Thanks! EDIT: with TacView files in post #3. Sometimes the track files don't play back correctly when recorded on different versions of DCSW. EDIT 2: it looks like the flight profile was changed in OB 2.5.4.25729 on 20 Dec 2018, as the version notes included: "AGM-65. Search and lock ranges was increased based on launch altitude." In giving the missile potentially a little bit longer range at altitude, the change took away the low-level, pop-up ability, which is a poor trade. It also does not explain the left veer tendency introduced. OB 2-5-3-24984 AGM65 success.trk OB 2-5-4-26368 AGM65 fail.trk

Good to hear about the -F. In the screen shot scenario above, I am not having issues either. The problem is pop-up attacks near the deck, where the -D dives down and hits terrain instead of climbing as it used to.

I can confirm this unusual behavior of the AGM-65Ds since the last patch (16 Jan 2019). Flight path of the missile has been altered such that low level launches are hitting targets maybe half the time. This is drastically different than the missile behavior that I am aware of since the launch of the A-10C and severely limits a key weapon for the Hog.

Has anyone figured out how to get a legible RWR export to work? Just using a viewpoint results in thin, spidery lines/symbols.

Little known tip: you get a pilot body if you hit shift-E three times.

Integrated IFF in RWS.

Moltar, I was looking to your mod pack to pull out the RAE mod which had been updated for the new 2.5 architecture. Could you point me to the file path for just this portion in your pack? Thanks! Sent from my SM-G960U using Tapatalk

I get the feeling that team specific chat is now readable by both sides. Any one else?

Same problem with 2 monitors; see attached lua JRM-2-Mntr Update.lua

Thanks! This will help with my instrument turns.

How do I remove the clock from the lower left hand corner of the HUD? It appears to be default on.

Eastern portion of Caucasus is grid 38T.

Try cycling power to the jammer. I recall seeing something similar.

Thanks for checking.

My experience is that buddy lasing works out to a slant range of 10nm. Aspect of laser and weapon also are important at long range, e.g. both laser and bomber approaching target from the same side. Is your experience different?

From memory, I think this may come from ED's building the radar behavior from the ground up for the Hornet instead of using some of the shortcuts of FC3's radar model.

Great to hear, Wags. Thanks for all the work!

Rainmaker, cycling the right generator used to clear the condition, but it does not seem to do so anymore. Also, curious that Nineline is not classifying the post as "already reported."

Cold = better chopper performance!

I can confirm similar behavior: TACAN issues on MP servers, no issues on SP.

UPDATE: with track file attached (from the Instant Action AIM 9 and AA Guns mission) As of Open Beta, yesterday: For in-flight starts, default cockpit set-up places the radar page on the right DDI. If you shift this page over to the left DDI, you get a flashing X on the radar page, even if radar page is first deselected on the right DDI. Problem does not seem to manifest for cold starts. Flashing X on radar1.trk

Radial, if you are interested in pattern work, ATC, etc, I would recommend creating your own mission versus modified a randomly generated one. From the main splash screen, select Mission Editor, create new mission, and then save the miz file wherever you want. That way you will have full control over all of the variables. Hang in there, keep at it and asking questions. This module is excellent and rewards hard work at the beginning.

In current OB, I noticed that I could not fire the wingtip AIM9s after I had used the emergency jettison button on the other stores. Not sure if this behavior is intended or not.

Bring a repair crate with you to jump start the farp repair process. Sent from my XT1060 using Tapatalk