AIM-54 Missile Desync/RWR Testing

[DoorMouse]

TLDR:

1. in 100% of tests the RWR gave a warning
2. There was only a minimal 'desync' when the missile worked properly, and we have found a way to replicate proper behavior which will be in the next set of tests. Basically, restart the server and the First shot seems to work the same for Shooter and Observer- subsequent shots do not.
3. Shooter and Observer get different initial vectors for the missile heading and this causes the Shooter/Observer's independent simulation of the missile to have different flight paths, speeds, and locations when the 'Kill" event happens. This is not a network issue, this is the two clients being given different information 

 

I will be posting follow up videos later. I have intentionally removed the steps required to reproduce this issue as to not proliferate its use. I hope this helps.

 

I've posted this on both the Heatblur Bugs and ED Weapons Bugs forum.

 

Public Release Missile Test.docx.pdf

[Biggus]

Plenty of reactions.  Most of us I think are content to leave it to HB to address this, with presumably the full unredacted report.  I agree it's an excellent investigation.

[GGTharos]

6 hours ago, DCSoping said:

And not a single reaction sofar ? 

 

Why?  It's pretty much what has been said would be a major factor.

It's great that work was done to make it clear.

Edited September 11, 2021 by GGTharos