BlackPixxel Posted January 5, 2023 Posted January 5, 2023 (edited) The radar extrapolation mode in BVR STT has a bug. Under some conditions there will simply be no extrapolation. Lock will then instantly break. When that happens, exceeding gimbal limits will instantly break the lock, and the target changing aspects and crossing the notch for a fraction of a second will instantly break the lock. I don't fully understand when this happens, in one of my test missions it almost always happened when the target was locked with radar scanzone slewed in azimuth and the target locked far off boresight. In another mission it seemed as if it will not happen in lookdown. But I am not sure. I hope these two tracks will help to find the circumstances that cause this bug to appear, In the first track the bug causes the lock to instantly break when the target crosses the notch angle by simply flying a circle: bug_test-20230105-210727_memory_bug.trk In the second track the bug causes the lock to instantly break when gimbal limits are exceeded for a splitsecond: radar extrapolation bug.trk This is a very annoying bug as it does appear from time to time in multiplayer and causes loss of lock under situations where it should not happen. Edited January 5, 2023 by BlackPixxel 1
BlackPixxel Posted June 8, 2023 Author Posted June 8, 2023 Extrapolation is still broken after current update. Very annoying, considering that no extrapolation means instant loss for targets changing aspect, and with the recent changes to R-27 that means that the missile will be always trashed as we lose STT lock. 2
Flappie Posted June 21, 2023 Posted June 21, 2023 Thanks for the heads up and the tracks. Issue reported. 1 2 ---
Flappie Posted July 5, 2023 Posted July 5, 2023 Devs told me it's not a bug: a preliminary target tracking of at least 5 seconds is required to enable trajectory extrapolation. If you have public documentation compatible with rule 1.16 and stating otherwise, please send it to Chizh in a private message. 1 ---
TheFreshPrince Posted July 11, 2023 Posted July 11, 2023 Am 5.7.2023 um 19:44 schrieb Flappie: Devs told me it's not a bug: a preliminary target tracking of at least 5 seconds is required to enable trajectory extrapolation. If you have public documentation compatible with rule 1.16 and stating otherwise, please send it to Chizh in a private message. But it breaks lock even if you lock the bandit for more than 5 seconds before firing or do you mean the missile has to track for 5 seconds first? And shouldn't it start flashing first instead of instantly breaking?
Pavlin_33 Posted August 19, 2023 Posted August 19, 2023 Hi @Flappie, what's the status on this one? I just had a Mirage F-1 break my lock instantly in a lookup from some 10km away. This was in multiplayer. i5-4690K CPU 3.50Ghz @ 4.10GHz; 32GB DDR3 1600MHz; GeForce GTX 1660 Super; LG IPS225@1920x1080; Samsung SSD 860 EVO 1TB; Windows 10 Pro
Flappie Posted August 19, 2023 Posted August 19, 2023 Nothing has hanged since my last message. Devs say it is correct as is. I'll have the tag changed accordingly. ---
Pavlin_33 Posted August 20, 2023 Posted August 20, 2023 9 hours ago, Flappie said: Nothing has hanged since my last message. Devs say it is correct as is. I'll have the tag changed accordingly. Thank you. i5-4690K CPU 3.50Ghz @ 4.10GHz; 32GB DDR3 1600MHz; GeForce GTX 1660 Super; LG IPS225@1920x1080; Samsung SSD 860 EVO 1TB; Windows 10 Pro
BlackPixxel Posted August 20, 2023 Author Posted August 20, 2023 This "fix" for extrapolation mode introduced new issues regarding ECM. If the enemy blinks ECM within 4 seconds after locking the lock instantly breaks. This should not happen when the Su-27 is in an ECCM mode.
Flappie Posted August 21, 2023 Posted August 21, 2023 11 hours ago, BlackPixxel said: This "fix" for extrapolation mode introduced new issues regarding ECM. If the enemy blinks ECM within 4 seconds after locking the lock instantly breaks. This should not happen when the Su-27 is in an ECCM mode. Please create a new thread and attach a track. ---
Recommended Posts