reported earlier R-27R Sometimes Not Tracking After New API Update

[ColdClaws]

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.

 

1v1 miz3-20250923-201636.trk server-20250923-201621.trk Tacview-20250923-201626-DCS-Host-1v1 miz3.zip.acmi

[Creampie]

Suprised this hasn't been acknowledged yet.

 

Surely it wouldn't be deemed as "working as intended" seem like a lot of desync? Maybe something else?

 

Edited September 28 by Creampie

[Thirsty]

On 9/28/2025 at 4:13 PM, Creampie said:

Suprised this hasn't been acknowledged yet.

 

Surely it wouldn't be deemed as "working as intended" seem like a lot of desync? Maybe something else?

I wonder if there's going to be any. 
There is radio silance about the R-27Rs gudince bug

Edited Tuesday at 10:50 PM by Thirsty

[QuiGon]

On 9/28/2025 at 4:13 PM, Creampie said:

Suprised this hasn't been acknowledged yet.

Surely it wouldn't be deemed as "working as intended" seem like a lot of desync? Maybe something else?

The new/reworked R-27 that came with the FF MiG-29 release update does indeed have severe desync issues, meaning only the client that fired the missile will see its actual flight path. That applies to Tacview recordings too, meaning only the recording fromthe client who fired the missile shows its actual flight path.

This desync issue should be fixed in the next DCS update.

Edited yesterday at 07:46 AM by QuiGon

[Ramius007]

I saw around dozen of r-27r fired by AI in my SP mission scoring 0 hits, rather unusual before last update. Flight of 4 FC Fulcrums against pair of Eagles C get decimated. Fulcrum was used to be best performing Soviet CW AI plane after Mig-31

[BIGNEWY]

please wait for the next update for improvement

thank you