dundun92 Posted July 30, 2020 Posted July 30, 2020 So after looking in the lua with data for the AMRAAM, i noticed in the seeker section of the code this: delay = 1.5, I looked at some tacviews from dedicated missile testing, and noticed the difference from when I got in seeker range (8nm/15km), and when I got the missile warning was just over 1.5 sec (in the tests I was waiting for missile active and knew it was coming, so I reacted very quickly). So this seems to explain some of the reports of AMRAAMs at very high altitudes and speeds giving a warning about 4nm or less from the target, while at lower altitudes (and consequently slower speeds) they gave warnings much closer to 8nm (closer to 6-7nm). Just thought Id share this finding. Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when? HP Z400 Workstation Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg
GGTharos Posted July 31, 2020 Posted July 31, 2020 It that a delay for seeker activation after launch or for the RWR to respond? The missile engages its radar about 7nm away from the target in-game, where it should start search about 13nm (the range is dynamic of course, but much longer than what we have), and the WRs themselves seem to have some sort of delay in reporting the missile. At high speed and altitude, with a huge closure that missile won't leave a lot of room for maneuvering. [sIGPIC][/sIGPIC] Reminder: SAM = Speed Bump :D I used to play flight sims like you, but then I took a slammer to the knee - Yoda
dundun92 Posted July 31, 2020 Author Posted July 31, 2020 It that a delay for seeker activation after launch or for the RWR to respond? The missile engages its radar about 7nm away from the target in-game, where it should start search about 13nm (the range is dynamic of course, but much longer than what we have), and the WRs themselves seem to have some sort of delay in reporting the missile. At high speed and altitude, with a huge closure that missile won't leave a lot of room for maneuvering. For sure it affects the RWR delay. I may try cranking it up to some high value and seeing if it stops it from guiding. Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when? HP Z400 Workstation Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg
BlackPixxel Posted July 31, 2020 Posted July 31, 2020 Just make a mission where you get engaged by an Aim-120 and flare once you get the launch warning. Then you will see on tacview that the Aim-120 maneuvers way before you deploy the flare. There is certainly a RWR-delay.
dundun92 Posted July 31, 2020 Author Posted July 31, 2020 So I did a test and this definitely isnt just RWR delay thats affected. The seeker acquisition itself is delayed, and the RWR warning appears to be instantaneous (or at least not linked to this lua value). Heres the tacview. I edited the value to 10 sec. Note the exact 10sec delay from launch to guidance (when it made the turn towards the flanker):Tacview-20200731-155544-DCS.zip.zip Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when? HP Z400 Workstation Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg
BlackPixxel Posted August 1, 2020 Posted August 1, 2020 Maybe this value is the delay for the safety maneuver, where the missile will just fly straight without guiding to not hit the carrier.
dundun92 Posted August 1, 2020 Author Posted August 1, 2020 Not sure why this was moved to the bug section, I'm pretty sure this is intended behavior? Eagle Enthusiast, Fresco Fan. Patiently waiting for the F-15E. Clicky F-15C when? HP Z400 Workstation Intel Xeon W3680 (i7-980X) OC'd to 4.0 GHz, EVGA GTX 1060 6GB SSC Gaming, 24 GB DDR3 RAM, 500GB Crucial MX500 SSD. Thrustmaster T16000M FCS HOTAS, DIY opentrack head-tracking. I upload DCS videos here https://www.youtube.com/channel/UC0-7L3Z5nJ-QUX5M7Dh1pGg
Recommended Posts