Jump to content

Recommended Posts

Posted

I'm actually using openbeta 2.5.5.33184, not latest.

 

HARM does bug when fired against a moving SAM (here in the track, a SA15 Thor) :

HARM missile locks the point the SA15 was when firing, but not the radar source that is moving and still emitting. So the moving sam is undestructible using HARM.

harm-mov-sam-bug.trk

Posted

HARM doesn't lock on to radiation source

 

The HARM won't lock on the radiation source, but rather its coordinates.

 

I've made a simple mission to demonstrate it, with a moving SA-15. White smoke is marking its initial position and then, every time I fire off a HARM, a different smoke marker appears at the position it was when I fired.

 

If you look at the screenshot, all four HARMs hit at the spot where it was when I fired them, even though the SA-15 itself was close by and still emitting.

 

The HARM is an anti-radiation missile that locks on a source of radiation. Only in PB mode will it guide itself to specific coordinates and that is only if the radiation source in question stops emitting.

 

There is historical precedence of an F-4G hitting an airborne B-52G's tail, because it accidentally locked on its tail gun radar.

 

Open Beta 2.5.5.33552. F/A-18C Lot 20. Persian Gulf map.

Screen_190723_232231.thumb.png.e2e77b4e7102b90ead1bada5fed40601.png

HARM against moving target bug.trk

The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

CVW-17_Profile_Background_VFA-34.png

F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3
-
i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro

  • ED Team
Posted

The AGM-88C is not meant to track and fire on moving targets, newer versions of the HARM improved this, but that isn't what we have.

 

The info on the friendly fire incident isn't very clear, so hard to say it tracked a moving aircraft or not, and hardly something we would want to model our HARM on, based on an unintentional strike.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Posted (edited)

I have another scenario (with a short track), and I wonder if it is also not a bug, like moving sam, or different case where HARM should have homed on sam's radar :

 

A fixed SA15 is fired at with HARM-c, then the SA15 moves for 50-80 meters and stops, so during the last 40 seconds of HARM's flight the SAM is fixed and emitting (but not attacking HARM because this option is disabled).

In this case the HARM still hit the initial position of SA15 (before displacing 50-80m). Is it normal ? or HARM should have homed on SA-15's radar during the last 40 seconds of flight ?

 

Edit : reading this quote : "In all modes the HARM employs flex logic, and will automatically acquire the next highest value (priority) target should the intended target go off the air. This ensures that the weapon is not wasted once it is committed." from this page : https://www.ausairpower.net/API-AGM-88-HARM.html , under HARM C section, I imagine that in the scenario of the track the first Harm should have "re-acquired" the SA15 when stopped moving during the last 40s.

harm-displaced-sam-bug-2.trk

Edited by toutenglisse
  • ED Team
Posted

Dear all, after talking with our weapon guys, it seems there was something off in the HARM, most likely related to a fix a while back that stopped it from changing targets in mid-flight, so a slight adjustment has been made, should be in the next Open Beta, check it out and let me know if its better, or too far the other way. My tests show it to be better with slower-moving targets.

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...