ColdClaws Posted 2 hours ago Posted 2 hours ago This problem was first noticed by another player who posted the attached video with the file name starting with "7b21a". I, ColdClaws, and another player named Zipper 1-1 have replicated this. In the attached track files and tacview the R-27R fails to start tracking at all in many engagements despite a solid radar lock. In what may be a separate bug, the R-27R appears to track but fails to explode in a near miss despite being within NEZ (no escape zone). This seems to only happen when the target makes a sudden turn right before the missile would impact. There are hits in these tracks but in a significant amount of the engagements the missiles miss when they should have hit or proxy fused. In the tacview, the R-27Rs don't match the position that they were in the track file while the Aim-7M's position was identical within the tacview and track files. Also, no chaff or notching was used during these tests, only cranking, which is why I have included a screenshot from the tacview to show that I was never in a notching position. The two track files are from the same mission. One is from my perspective and the other is from the other pilot's, Zipper 1-1, perspective. The trackfile named "1v1 miz3" was from the player Zipper 1-1, who was primarily in the Su-27 firing R-27Rs at me. The track file named server-20250923 was from me, ColdClaws, primarily defending in the F-15C. The track files are about ten minutes long but only these two planes are in the mission with no scripts or mods, just testing the R-27R. 7b21a7c828ec2b11962463fb47e79d4a.mp4 1v1 miz3-20250923-201636.trk server-20250923-201621.trk Tacview-20250923-201626-DCS-Host-1v1 miz3.zip.acmi
Recommended Posts