Jump to content

[REPORTED] Amraam range wrong indication?


raelias

Recommended Posts

So the test is as follows:

 

 

Hornet behind a group of 4 IL76 flying straight and level at angels 20 M75, spaced 15nm apart

 

 

 

First I do some radar lock and AACQ tests, as I understand AACQ should lock the closest target but sometimes it locks the one ate 15nm, sometimes the one at 30, I do understand however that this feature is in EA not working properly

 

 

locking the closest Il76, the plane tells me I have an rmax at those parameters of 15nm, so I start shooting getting closer and closer

 

 

The target never manouvers, and yet only when I get within 10nm i finally get a hit (just barely)

 

 

Am I misunderstanding the concept? The way I see it the missile should be able to get to the target at rMax as long as it doesn't manouver at all (as the test is setup) which should be 15nm, but in reality It can only reach it at 10nm

 

 

Sorry if I'm wrong about the concept, but there you go track attached

Amraam test.trk


Edited by raelias

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

Same happens on the Sparrow, shows rmax of 11.8nm but I could only get a hit on a 6nm shot

Sparrow test.trk

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

Can someone please acknowledge this?

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

First of all, AACQ is WIP and there's also a bug where your radar might not respect the TDC range position and lock something else in the same azimuth. It's been reported.

 

Secondly, the Rne (no escape zone) logic in the Hornet is definitely incorrect. It's mentioned in several threads. In this one, I did some tests between the F-15C (correct logic) and the F-18C, (incorrect logic): https://forums.eagle.ru/showthread.php?t=250074

 

 

There's also this reported thread: https://forums.eagle.ru/showthread.php?t=253488&highlight=Rne

 

 

Rne should be the range that the target cannot kinematically escape the missile no matter what. It doesn't mean that the missile will hit, but it does mean that purely kinematic evasion (such as dragging the missile or pulling G's at the last second etc) is not possible. That is definitely not true with the Rne displayed in the Hornet. Hopefully, with the upcoming radar changes, they can adjust this. The Rne calculation in the F-16C is better, so I'm hopeful.


Edited by Harker

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

Link to comment
Share on other sites

  • ED Team

Hi

 

Rmax is for a non manoeuvring target, your targets are moving away from you.

 

you should be using Rne for a kill

 

hope that helps

CaptureRMAX.thumb.PNG.26b6a8d0c10eddccd6691d6d7e8d9ca1.PNG

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Link to comment
Share on other sites

Hi

 

Rmax is for a non manoeuvring target, your targets are moving away from you.

 

you should be using Rne for a kill

 

hope that helps

Hey BN, what about the Rne logic though? Is it going to be addressed in an upcoming patch? Because you can get Rne cue from 28NM away now and that is not threatening even in the slightest to an enemy fighter. You can defeat an AIM-120C launched from 28NM away by just maneuvering a little.

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

Link to comment
Share on other sites

Hi

 

Rmax is for a non manoeuvring target, your targets are moving away from you.

 

Flying away is not maneuvering.

 

RMax should be usable regardless the target attitude, only requirements are that it maintains its vector and its velocity.

 

That should be dynamically calculated that as long the target doesn't change vector nor change speed to worse (at least accelerate when flying away, or decelerate when flying toward) the missile will reach it based all the information of wind, height etc there is at the current launching platform (and expecting to have same at the target location).

 

As all different factors change the Rmax value, it only requires that target doesn't maneuver at all after the moment the calculation for Rmax is done.

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

Link to comment
Share on other sites

Hi

 

Rmax is for a non manoeuvring target, your targets are moving away from you.

 

you should be using Rne for a kill

 

hope that helps

 

 

That's incorrect, non manouvering means it's keeping is current speed/altitude/heading, it should calculate Rmax based on those conditions, as such in this case it shows an rmax of 15nm, if the targets were head on it would be sometimes over 30nm depending on the altitude and speed

 

 

Fact of the matter is that the Rmax and Rne are incorrect and must be addressed

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

Hey guys, looking into it now, does seem to be something off, thanks.

 

 

What do you mean? You can clearly see the missile falling WAY short on a non-manouvering target on both the AMRAAM and Sparrow, the calculation is clearly off by a lot

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

  • ED Team
What do you mean? You can clearly see the missile falling WAY short on a non-manouvering target on both the AMRAAM and Sparrow, the calculation is clearly off by a lot

 

I mean... looking into it now, does seem to be something off, thanks.

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

Link to comment
Share on other sites

I mean... looking into it now, does seem to be something off, thanks.

 

 

Oh i misread, thanks!

Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD

 

Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf

Link to comment
Share on other sites

  • Recently Browsing   0 members

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