HeavyGun1450 Posted March 30, 2022 Posted March 30, 2022 (edited) I have experienced this many times now and know several others on the same server I play on have as well, but it appears (sometimes) that the SA-5 will not always give you a launch warning on the RWR. I have experienced this in the attached trackfile. Initially I thought this was happening to all aircraft, but after extensive testing in the mission editor only the Tomcat is doing this. Basically what generally happens is your cruising along at 30k-35k and enter the edge of the SA-5s engagement range, the SA-5 will soft lock you for a few seconds, drop lock for a few seconds and repeat over and over again until all of a sudden you get killed by a missile from it with absolutely no launch warning what so ever. So it seems something is wrong with launch detection with the F14's RWR and SA-5 system. @IronMike SA-5Bug#2.trk SA-5Bug.trk Edited March 30, 2022 by HeavyGun1450
HeavyGun1450 Posted July 3, 2022 Author Posted July 3, 2022 Still a issue as of today. Had it happen again. @IronMikecan you please look at those track files.
near_blind Posted July 4, 2022 Posted July 4, 2022 I was able to confirm from your tracks and have made a report with Heatblur. 2
HeavyGun1450 Posted July 5, 2022 Author Posted July 5, 2022 22 hours ago, near_blind said: I was able to confirm from your tracks and have made a report with Heatblur. Thank you for looking at my tracks and reporting this!
Koty Posted July 10, 2022 Posted July 10, 2022 Not sure how intentional this was by HB, however, S-200 does not change emissions when launching so this is in fact more or less how it should behave. 1
near_blind Posted July 11, 2022 Posted July 11, 2022 9 hours ago, Koty said: Not sure how intentional this was by HB, however, S-200 does not change emissions when launching so this is in fact more or less how it should behave. Apocryphally, if that facet of the Barlock were simulated accurately in DCS, it would go straight to a launch indication when detected by the RWR. 1
Bananabrai Posted July 11, 2022 Posted July 11, 2022 Depends on how it is put into the RWRs database. As always spike or always nails 1 Alias in Discord: Mailman
near_blind Posted July 11, 2022 Posted July 11, 2022 Having talked to two different people who were lit up by barlocks in two different types of aircraft during a recent geo-political imbroglio, it's my impression that at least the United States has settled on barlock = all launch warning, all the time 2 1
Koty Posted July 12, 2022 Posted July 12, 2022 Also I think you got the wrong code name, 5N62 is the Square Pair, Bar Lock is the P-35.
near_blind Posted July 12, 2022 Posted July 12, 2022 Yeah, that's my bad. Sentiment remains though. 1
Super Grover Posted July 15, 2022 Posted July 15, 2022 Thank you for your reports. I verified the tracks, and the bug is not related to the SA-5 but to two tracking radars positioned next to each other. The tracks helped me find a bug in the RWR threat association algorithm, and it should be fixed in the next patch. Again, thank you very much. 1 Krzysztof Sobczak Heatblur Simulations https://www.facebook.com/heatblur/
HeavyGun1450 Posted July 15, 2022 Author Posted July 15, 2022 1 hour ago, Super Grover said: Thank you for your reports. I verified the tracks, and the bug is not related to the SA-5 but to two tracking radars positioned next to each other. The tracks helped me find a bug in the RWR threat association algorithm, and it should be fixed in the next patch. Again, thank you very much. Thank you sir for the info. Im glad this bug will be fixed, Its killed and scared the crap out of me and others more times then I can count!
Recommended Posts