Max1mus Posted June 5, 2020 Posted June 5, 2020 On my screen, some of the last AMRAAMs were missing. On the hosts (and shooters) screen, the missile was hitting its target. This was while attempting to notch them with the new modelling. Might be connected to https://forums.eagle.ru/showpost.php?p=4369681&postcount=8061 Host track http://www.filedropper.com/server-20200604-211435 Perfect_1v1_mission_V1.1-20200605-033110.trk My track (Spectator slot) When ED reworks russian missiles: Spoiler https://imgur.com/VoBlY9n (April 2021 update)
Zergburger Posted June 7, 2020 Posted June 7, 2020 A2A missile desync is not a new phenomenon. The reason it is becoming more prevalent is that the longer the missile is in the air, the more desync can occur (think INS drift). With the introduction of the aim-54 and the increase in aim-120 capabilities, longer and longer shots are becoming possible; thus more desync is introduced.
Max1mus Posted June 15, 2020 Author Posted June 15, 2020 (edited) A2A missile desync is not a new phenomenon. The reason it is becoming more prevalent is that the longer the missile is in the air, the more desync can occur (think INS drift). With the introduction of the aim-54 and the increase in aim-120 capabilities, longer and longer shots are becoming possible; thus more desync is introduced. I need to clarify: THIS IS NEW. THIS IS HAPPENING WITHIN A FEW MILES, NOT RELATED TO FLIGHT TIME. I am well aware of long range desync. Its mostly fixed on the amraam, but still a large issue on the 54. But thats not whats happening here. This is new. Edited June 15, 2020 by Max1mus When ED reworks russian missiles: Spoiler https://imgur.com/VoBlY9n (April 2021 update)
dundun92 Posted August 11, 2020 Posted August 11, 2020 (edited) Can comfirm, and it only seems to happen in MP. It doesnt happen in SP. If someone from ED would look through this track you will find that AMRAAMs that showed as being notched from the server-side AND client-side in fact hit me, and were actually not notched. In fact, in a track that is too large to link, I visually confirmed that the missile turned away from me from the smoke trail, and was flying BEHIND me, yet I still blew up. This also shows up in the tacview, which I can link for anyone interested. Can someone from ED comment on this? Server and client Tracks are attached:server-20200810-174635.trkDAWS BVR BASIC ARH TRAINING 13-20200810-174654.trk Edited August 11, 2020 by dundun92 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
dundun92 Posted October 7, 2020 Posted October 7, 2020 Still an issue post patch. Any comments from ED? 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
nighthawk2174 Posted October 8, 2020 Posted October 8, 2020 +1 I really wish they'd return to the old chaff chance value as imho it's a more realistic option as an interim solution, on top of fixing the above bug which I'd think would be a high priority bug.
Recommended Posts