R27-ER (on SU27) continues to track after breaking lock

[r2dseu]

Hi folks,

I've noticed that R27-ER continues to track even after I've broken lock both by notching (and verifying no lock on RWR) and that the bandit (SU27) has turned away.

I don't have a track file but I do have the Tacview file that clearly demonstrates (around the 23:29 mark when the engagement starts):
1. The first SU27 that fires off the R27ER clearly disengages beyond it's gimbal limit (actually turns cold)
2. The second SU27 is destroyed (confirmed on BDA during the mission)
3. I'm not seeing any other opforce unit that could be providing guidance via datalink or otherwise
4. You can clearly see around 24:57 that the R27ER cranks to engage

I initially thought that I got hit with the ET but Tacview states otherwise. Could Tacview be incorrect here (if so, it doesn't makes sense since I did receive a RWR lock in the first place which forced me to crank).

I know this was a known bug few years ago but surprised to see it coming back.

Tacview-20240118-234053-DCS-F15C TGW M09.zip.acmi

[r2dseu]

I also thought that the missile could have been launched on HOJ mode (I did have my EW turned on) but I did see the initial RWR lock (which prompted me to notch) that indicates that it didn't launch on HOJ mode to begin with. Does R27-ER switch to HOJ mode if the launching platform stops providing guidance?

[AeriaGloria]

19 hours ago, r2dseu said:

I also thought that the missile could have been launched on HOJ mode (I did have my EW turned on) but I did see the initial RWR lock (which prompted me to notch) that indicates that it didn't launch on HOJ mode to begin with. Does R27-ER switch to HOJ mode if the launching platform stops providing guidance?

Yes I believe it can, if lock fails 

[SparrowLT]

R27R will definitily HOJ if loses lock.. i learned long ago that when fired by one first turn ECM off

[Coxy_99]

nullAll fox1 missiles will HOJ as in this perfect example here.